A laptop displays a glowing security assistant dashboard, set against a scenic alpine office view.
Proton's privacy-focused AI assistant has left the browser tab. Proton has released Lumo Desktop for Windows, Mac, and Linux with new Connectors, Schedules, and Skills capabilities. The release landed on 17 November 2026. The headline is a desktop app. The real story is that the app lets an AI assistant touch your files, your shell and your inbox. That deserves a closer look from anyone who runs Windows PCs, whether at home or in IT.

A laptop displays a glowing security assistant dashboard, set against a scenic alpine office view. What Proton actually shipped​

Neowin's report describes Lumo as an open-source chatbot that Proton launched in July last year. Proton claims zero-access encryption for saved chat histories, so not even Proton can read them. Neowin adds that most of Proton's AI servers sit in Switzerland. The desktop apps arrive months after Lumo 2.0, which brought Lite and Max models, memory across conversations, image generation and a side-by-side editing canvas.

Proton's launch post bundles three features with the desktop apps:

  • Connectors link Lumo to apps, files and tools.
  • Schedules run a task at a set time or repeat it at an interval.
  • Skills are saved, reusable instructions. They replace "Custom Lumos," which Proton says will migrate automatically.

Proton also says it is publishing the source code for the desktop tools so the community can inspect them. It frames this as a first step toward more transparency about how it uses AI. It also says its first NVIDIA B300 cluster, built on Open Compute Project standards, is going live in Switzerland.

One gap is worth flagging. Proton's material doesn't list minimum Windows versions or hardware requirements. I won't guess at them. Check the download page before you roll this out.

Connectors: the part Windows admins should read twice​

Per Proton's documentation, Connectors let Lumo find information and take actions in the tools you connect. The supported types are:

  • Local tools: filesystem access, shell execution and browser content fetching.
  • Proton Mail, through Proton Mail Bridge.
  • Third-party services. Proton's support page names Slack, Atlassian, Dropbox and Google Drive. The launch post names Google Drive, Jira and Confluence.
  • Your own local or remote Model Context Protocol (MCP) servers. Proton's support page says local stdio servers and remote HTTP servers are supported.

Proton's pitch is that you can ask Lumo to find a document on your computer or gather bookings from your email. You don't have to switch tabs or copy and paste between windows.

The permission model​

For every connector you choose which actions run automatically, which need approval and which are blocked. Proton's example is letting Lumo search an inbox, asking before it sends an email, and blocking message deletion. Proton's support page names the three settings:

  • Auto-approve: Lumo runs the action without asking.
  • Ask human: Lumo asks for confirmation first.
  • Deny: Lumo is blocked from running the action.

Proton's support guide says all actions are set to Auto-approve by default when you add a connector. This is the detail to take away. The marketing says you decide. The default says Lumo will proceed unless you've told it otherwise. Connectors are also enabled in every conversation by default. Neither default is unusual in the AI-agent world, but they put the burden of caution on you.

The shell execution connector is the one to treat with respect. IT Security Guru's coverage points out that giving an assistant this kind of reach raises obvious security questions. Proton's answer is granular control. Tbreak makes the same point in its own coverage: connectors can expose inbox contents and local files, while shell execution lets the assistant run commands. That's analysis rather than a defect. Any agent with file and shell access carries this risk profile.

How to set up a connector​

Proton's support steps are:

  1. Open Lumo Desktop and sign in with your Proton account.
  2. In the sidebar, click Customize > Connectors.
  3. Pick a connector and click Connect. For a custom MCP server, click Add MCP server and enter its details.
  4. Optionally adjust per-action permissions.
  5. Complete any authentication steps. When authorization succeeds, the tool shows as connected.

To exclude connectors from a single chat, click Tools > Connectors in the chat window and toggle them off. To change permissions later, go to Customize > Connectors, pick a connector and open the Functions tab. To remove one, select it and click Disconnect.

A cautious starting posture (my recommendation)​

This advice is mine, not Proton's. Start with read-only actions on a narrow folder, and set anything that sends, modifies or deletes to Ask human. Switch the shell connector to approval-only, or leave it off until you have a clear use for it. A permissive default is fine for a toy. It is a poor fit for a work laptop that holds client data.

Schedules: unattended AI​

Schedules apply the same permission model to work that runs without you watching. According to Proton's support page, you can create a task in two ways:

  • With Lumo: click Scheduled > New task, choose Create with Lumo, describe the job, answer follow-up questions, check the details and click Schedule.
  • Manually: choose Set up manually, then fill in the name, instructions, connectors, frequency, permissions and advanced settings such as notifications.

Existing tasks can be edited, paused, resumed, run immediately with Run now, or deleted. Proton advises starting simple and using Run now to check the output before you trust the schedule. It also notes that Lumo works only from the instructions you give it, so vague prompts produce vague results.

Proton's examples include a weekly summary of emails that need a reply and a monthly review of bills and receipts. Its permissions advice is sensible. Read-and-summarize tasks can run freely. Anything that sends or deletes should ask first. The catch is that an approval prompt for an unattended task only helps if you are around to answer it.

Skills: reusable instructions​

Skills save instructions Lumo can reuse across conversations. Proton's examples are a writing Skill so emails sound like you, a résumé and career goals for job applications, and dietary preferences for meal plans. You can add templates and reference files, and Lumo applies relevant Skills automatically, several at a time if needed. You can write one yourself, ask Lumo to help, or upload an existing one.

A Skill is guidance. A Connector is access. Keeping those separate in your head makes it easier to reason about what the assistant can actually do.

Privacy claims: what is promised and what isn't​

Proton's stated position is that Lumo never uses conversations or information from connected apps and files to train models or serve personalized ads. It also says zero-access encryption means only you can read your chat history, and that Lumo is hosted on European infrastructure under Swiss privacy law, outside the scope of the US CLOUD Act. Its support page adds that connectors are protected by zero-access encryption and are never logged.

Read those as vendor claims. I haven't seen an independent audit of the desktop software or of each third-party connector. Encrypted chat history is also a different question from what a connector has to read to complete a task. If you point Lumo at Google Drive, Google's side of that relationship is unchanged. Proton's decision to publish the source code is a real point in its favor, because anyone can now check how the tooling behaves. Publishing code doesn't guarantee anyone has audited it.

Why Windows users should care​

  • A native option: Windows users get a dedicated app instead of a browser tab. Proton's productivity page says Connectors and Schedules are available on Lumo Desktop for macOS, Windows and Linux. Proton hints that they could come to mobile later.
  • Agent features in a privacy brand: Proton has moved from chat to task execution. That puts Lumo in the same conversation as other desktop AI agents, though Proton is the one pitching privacy and open code.
  • Subscription gating: Thurrott reports that Proton subscribers can download Lumo Desktop from the Proton website. Check your plan before planning a deployment.
  • MCP support: Bringing your own MCP servers makes Lumo a client for the same tool ecosystem developers already use elsewhere. That is powerful, and it widens the attack surface.

Bottom line​

Lumo Desktop is a meaningful step for Proton's assistant. It is also a good reminder that the safest AI agent is the one with the narrowest permissions. Before you connect anything, review the Auto-approve defaults, scope file access tightly, and test schedules with Run now. For IT teams, treat the shell and MCP connectors as you would any tool that can execute commands on a managed endpoint. Pilot first, and don't assume approval prompts will appear unless you've set them.

 

References

  1. Proton announces Lumo desktop apps for Windows, macOS, and Linux Neowin 2026-11-17T20:30:02+00:00
  2. Proton launches Lumo Desktop, bringing connectivity and automation to privacy-first AI | Proton proton.me
  3. Proton Lumo Desktop is Now Available - Thurrott.com thurrott.com