Automation and bots
Here is Lumo’s summary of a very long back-and-forth.
I set out to build a "chief of staff" workflow — surfacing priorities, managing calendar and documents, drafting communications — using Proton tools (Lumo, Proton Calendar, Proton Mail, Proton Drive) and Lumo as the AI layer. I chose Proton deliberately: I want minimal data exposure and I value the Proton ethos of zero-access encryption. But attempting the workflow surfaced concrete integration gaps that make meaningful automation impractical today. I'm sharing this in the hope it informs a roadmap for permissioned, user-authorized automation — agent-like functionality that preserves the Proton privacy model rather than abandoning it.
What I tried, and what happened
Lumo cannot reach Proton Calendar in any way. No Lumo-to-Calendar integration exists. The workaround is generating an ICS file for manual import.
ICS import friction on iOS. The Import from ICS feature lives only in the web app, not the iOS settings. On a phone, the practical path collapses.
Self-emailed ICS was not recognized as an event. Sending an ICS to my own Proton Mail address produced no "Add to Proton Calendar" button. The event card appears designed around formal invitations (organizer/attendee/RSVP structure); a bare event definition was treated as a generic attachment. Notably, auto-add of invites exists, so the machinery is half there.
Lumo creations download as .txt, requiring manual renaming to .ics — a small but emblematic snag.
Lumo's Drive relationship is one-way. I can read files I explicitly submit and save creations to Drive, but Lumo cannot browse Drive, open a document at my request, or edit in place. Perfectly understandable from a threat-model perspective — but it caps the assistant at "advice provider" rather than "collaborator."
The larger point
Competitors (e.g., Grok Bot on Mac) now offer deep cross-app automation: agents that sign into Mail, Messages, Notes, Reminders, Calendar, Contacts, and location, and act autonomously. Many users — including privacy-conscious ones — are tempted, because the utility is real. The current market forces a binary choice: capability with total exposure, or privacy with manual labor.
Proton is uniquely positioned to define a third path. What I'd love to see explored:
Scoped, revocable permissions: Let me grant Lumo access to specific Proton Calendar calendars or Drive folders, with per-action confirmation and an activity log I can audit. Agency through explicit delegation, not blanket credential sharing.
Act-on-my-behalf within Proton only: An agent that can create/edit/delete Proton Calendar events, attach drafts to Proton Mail, or update a Proton Doc — confined to the encrypted ecosystem, with no third-party surface at all — would deliver much of the chief-of-staff value with exposure capped at Proton itself.
At minimum, low-cost fixes: recognize bare ICS files in Proton Mail with an "Add to calendar" action on all platforms; add ICS import to iOS; preserve .ics naming on downloaded Lumo creations.
Consider an on-device/local execution model where feasible, so that "the agent saw your calendar" means "software on your machine saw your calendar."
Why this matters
I don't want to leave Proton's ecosystem — I left competitors because of its principles. But privacy shouldn't have to mean doing everything by hand. The Proton ethos and meaningful automation are reconcilable; it requires deliberate design of user-controlled authority rather than either refusing agency outright or handing over the keys. Whoever builds this well will keep privacy-motivated users from drifting to surveillance-based alternatives out of sheer frustration.
Thank you for considering it.