Proton Lumo Desktop: private AI that runs your shell and inbox
Proton Lumo Desktop adds Connectors, Schedules and Skills: file, shell, Proton Mail and MCP access with per-action approvals. Set the rules before you connect.
Proton launched Lumo Desktop today for Windows, macOS and Linux. The privacy-first assistant can now read your files, run shell commands, search your Proton Mail and call your MCP servers on a schedule. Proton announced it on its blog and TechCrunch covered the launch. Lumo Desktop is a privacy pitch, but it is also an agent with real access to your machine. The permissions you set matter more than the encryption.
What actually happened
Per Proton's announcement, the desktop app adds three features:
- Connectors: local filesystem access, shell execution and browser content fetching. Also Proton Mail through Proton Mail Bridge, Google Drive, Jira, Confluence, and "your own local or remote" MCP servers.
- Schedules: tasks that run at a set time or repeat, such as a weekly inbox summary. Each task has its own permissions.
- Skills: saved instructions, templates and reference files that Lumo applies across chats. Existing "Custom Lumos" move to Skills automatically.
For each Connector you choose which actions run automatically, which need approval, and which are blocked. Proton's own example: search the inbox freely, ask before sending, block deletion. Connected tools are on in conversations by default.
On privacy, Proton says Lumo does not train on your conversations or connected data, uses zero-access encryption for chat history, and runs on European infrastructure under Swiss law. It says it will publish the source code for the new tools. Connectors and Schedules are desktop-only. Proton's download page says Lumo is free with a Proton account and paid plans add features and higher limits. We found no price for those plans and no model name in the launch material.
Why it matters for your business
A private chatbot that only talks is low risk. A private chatbot with shell access and a scheduler is an agent. Zero-access encryption protects the chat log from Proton. It does not protect your files from a bad instruction, a poisoned document, or a scheduled task that nobody checks.
If your team tries Lumo Desktop, set it up like any agent:
- Default to "ask," not "auto." Let reads run. Make sends, writes and shell commands need approval. Block deletes.
- Turn off tools per chat. Tools are on by default, so a chat about a blog draft does not need the shell.
- Review every Schedule monthly. A recurring task with send rights is a standing permission.
- Vet MCP servers first. A remote MCP server can see what you send it. Keep a list of the ones you approve.
Key takeaways
- Lumo Desktop adds file, shell, Proton Mail, Google Drive, Jira, Confluence and MCP access
- Each Connector has auto, approve and block settings per action
- Proton names no model and lists no paid-plan price in the launch
- Encryption protects your chat history, not your machine from a bad action
- Set approvals and block deletes before you connect anything
Private AI still needs guardrails. We build internal agents with scoped tools, approval steps and logs you own, on infrastructure you pick. See how we build them or tell us which tools your team wants to connect.
Sources: Proton — Lumo Desktop launch, Proton — Lumo download, TechCrunch.
- #proton-lumo
- #ai-privacy
- #mcp
- #desktop-ai-agents
- #ai-permissions
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
Perplexity Monitor API: web watching at $1 per 1,000 runs
Perplexity's Monitor API tracks topics and pages on a schedule and sends signed webhooks for $1 per 1,000 runs. Here's the cost math and the catches.
Read itGoogle AI Mode temporary threads: what they do and don't hide
Google AI Mode temporary threads skip your history and personalization. Google doesn't state a retention period. What that means for staff AI policy.
Read it