Hello,

I'd like to propose a feature that would significantly increase Lumo's value for professional users: the ability for Lumo to read files directly from the user's own Proton Drive as conversation context.

The current gap: Lumo works great with individual files pasted or uploaded into a chat, but there is no way to give it access to a complete folder — for example, a software project directory. Working on real code means needing context across many files at once (source code, configs, changelogs). Right now, this means repeatedly uploading files by hand, which breaks the workflow.

Concrete user story (my own): I develop a network-management add-on for Kodi. Debugging sessions with Lumo involve dragging five-plus Python files into the conversation, manually keeping them in sync with my local versions, and re-sending them after long chats get compacted. If I could point Lumo at a synced folder in my Proton Drive — say, "read resources/lib in this shared folder as your working context" — the entire friction disappears. Everything stays end-to-end encrypted under my own keys, and Lumo always sees the current version.

Why this fits Proton uniquely: This could become a genuinely differentiating feature. Privacy-focused cloud storage plus a private AI assistant that can securely work on your own files — with decryption happening client-side and content never exposed to third parties — is a combination mainstream competitors cannot credibly offer. For developers, writers, and researchers, "your encrypted Drive is your AI workspace" is a compelling pitch.

Suggested scope (phased):

Read-only access to user-selected Drive folders as chat context (with automatic refresh on file changes).
Later: a session-persistent "workspace" concept that survives conversation compaction.

Thank you for considering this — and thank you for building privacy-respecting tools that professionals can actually rely on.

Kind regards, Doemela.