Feature request — first-class support for running Lumo Desktop in an isolated VM
Hi Proton team,
I'd like to request official support for running Lumo Desktop inside an isolated VM (e.g. KVM/libvirt with a host-enforced network filter), which is how I run it today for maximum isolation of the agent.
In essence, the request is: make it easier to run the agent locked down in a VM. Concretely, the changes that would help most are:
- Configurable Bridge host/port in the Mail connector. The "Bridge host" field is currently locked to 127.0.0.1. When Bridge runs on the host and the VM reaches it via a relay, a configurable host/port (e.g. 192.168.122.1:1143) avoids running a local forwarder inside the VM.
- Make SMTP optional when "send" is disabled. The connector currently requires a working SMTP handshake at setup even if sending is blocked. Allowing an IMAP-only connector (or skipping the SMTP check when send is off) removes the need for a local SMTP stub.
- Draft creation in the Drafts folder (separate request) — so replies can be reviewed and sent by the human from their mail client, keeping "send" human-only.
- A browser-less sign-in option (device code / token paste). First-run sign-in currently opens the system browser, which a minimal hardened VM deliberately doesn't have.
Why? an AI agent with mailbox access is exactly the kind of workload users want to run zero-trust — network-enforced guarantees that it cannot send mail or exfiltrate data are stronger than any in-app permission toggle. Making VM isolation a supported, easy path means fewer users resorting to unofficial proxies and workarounds, and it fits Proton's privacy-first positioning: the platform should be the safest place to run an agent precisely because the user can isolate it.
I did get it all working (VM + host-side relay and firewall rules + local stubs), so this is not a blocker but I hope you'll make it an easier option in the future.
T