385 results found

1. Copy Lumo response as markdown

   Copying a Lumo response presently comes out as plain text (stripped down of formatting).
   Another button (or the same one with a dropdown option) could enable copying down the actual markdown formatting shown on screen instead.
   Essential when drawing up documents.
   The workaround today: copy the text, paste it into a new Proton Doc, and then copy as markdown from there. So it is feasible. The workaround is just cumbersome.

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Send to Proton Drive Button

   I lost some very important conversations about my ****** cancer journey and important memories because Lumo's local storage was silently cleared despite History being enabled. An automatic export or "Send to Proton Drive" feature would prevent this from happening to others. Memories and Health conversations are too important to lose. Please consider adding automatic backup to Proton Drive or Proton Docs.

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Lumo Senior: The Wise Companion with White Hair & Glasses – Growing Old with Our Users

   Many older adults (like my 82-year-old father) face daily challenges: They struggle to write emails, forget medications, or feel lonely. They need a companion who understands their pace and offers warmth, not just efficiency.

   I propose a dedicated "Lumo Senior" version where Lumo has visibly aged alongside its users. Instead of a young cat, Lumo appears as a wise, gentle companion with a few white hairs and friendly glasses. This symbolizes experience, patience, and the bond formed over years. His personality should be calm, patient, and empathetic – no rush, no jargon, just a warm presence that listens and remembers.

   Here are the key features for this version:

   1. Daily Life Support: Help with writing emails, messages, or classified ads (e.g., "Help me write an email for this bicycle I found"). Gentle reminders for medications and meals. Simple navigation for essential tasks without technical confusion.

   2. Emotional Connection & Stories: Storytelling by reading books, telling historical anecdotes, or helping seniors recall memories ("Tell me about that trip in 1970"). Combating loneliness through a conversational partner who truly listens, offers comfort, and encourages connection with family.

   3. Safety & Privacy: Sensitive health data stays on the device via offline mode. Secure and simple interface with no complex menus, just big buttons and clear interactions.

   Why this matters: If Lumo starts as a magical companion for kids, it should grow with them. Seeing Lumo age – with white hair and glasses – would create a profound sense of continuity and trust. It is not just an app; it is a life-long friend who grows old with you. My father already smiles when Lumo helps him write a simple email. Imagine the joy millions could feel with a companion who looks like they have been there all along.

   Future Vision: This concept lays the foundation for future expansions, such as advanced voice interaction and emergency safety features.

   Technical Feasibility: Built on Proton's existing secure infrastructure (encryption, local storage) with specialized models trained for patience and empathy.

   Many older adults (like my 82-year-old father) face daily challenges: They struggle to write emails, forget medications, or feel lonely. They need a companion who understands their pace and offers warmth, not just efficiency.

   I propose a dedicated "Lumo Senior" version where Lumo has visibly aged alongside its users. Instead of a young cat, Lumo appears as a wise, gentle companion with a few white hairs and friendly glasses. This symbolizes experience, patience, and the bond formed over years. His personality should be calm, patient, and empathetic – no rush, no jargon, just a warm presence that listens and remembers.

   … more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Code editor

   It would be nice if the codeblock Lumo uses would be an interactive code editor.
   Right now if I ask Lumo to change part of my code it also tends to rewrite other parts of code which I didnt ask it to do. With an interactive code editor I would be able to select a part of the code and make a prompt just about that selected part. Or I could edit the code myself if I dont like something without having to copy paste the whole code again to Lumo to let it know I edited something. This wouldn't only make it more userfriendly but it would also be more cost efficient since it would only need to look at the selected part of code and I also wouldn't need to copy past a bunch of code into Lumo every time.

   It would be nice if the codeblock Lumo uses would be an interactive code editor.
   Right now if I ask Lumo to change part of my code it also tends to rewrite other parts of code which I didnt ask it to do. With an interactive code editor I would be able to select a part of the code and make a prompt just about that selected part. Or I could edit the code myself if I dont like something without having to copy paste the whole code again to Lumo to let it know I edited something. This wouldn't… more

   52 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. download pdf

   recently was using gemini ai pro..they have at top of chat, right corner, "download pdf"..simple and effective. many parts of the world internet is expensive and not available always, this would be useful to user of lumo so they can access chat offline as pdf ( since this is widely used). Any particular reason for not being implemented till now?

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Lumo Integration to Read Encrypted Emails, Calendar, via On-Device Processing

   I want an AI assistant (Lumo) that can automatically read my Proton Mail inbox and execute actions based on preset rules (e.g., sorting, summarizing, drafting replies, flagging urgent items, consolidating multiple emails into one for review). I understand this requires on-device processing to maintain zero-access encryption. Currently, I have to manually copy/paste emails. An automated, privacy-preserving workflow would be a game-changer for productivity. Lumo needs more gemini like functionality in the Proton product space.

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Direct save of chats as Docs on Drive (+ Lumo-folder on Drive?)

   Integration between Lumo and Docs to allow Lumo users to save chats as Docs on Drive, directly from Lumo.

   Purpose: to ease UX of organising projects in Lumo and save time and effort for users.
   Value:
   1) Nudging users to support their own data security, by not using alternative tools outside of Proton Suite.
   2) Supporting user loyalty to Proton product suite, especially Lumo.

   User scenario:
   After finishing chat with lumo I press the "save as docs"-button next to "copy" and "try again features" in the bottom right corner of the screen. Dialog opens and asks: "Do you want to save this chat as a doc?" Possibillities: "Yes/No". I press "Yes" and Docs opens with the current chat content, ready to be named and saved. When named and saved in a folder of my choice in my Drive, I can upload it to my relevant folder in Lumo Projects.

   Or:
   After finishing chat with lumo I press the "save as Docs"-button next to "copy" and "try again features" in the bottom right corner of the screen. Chat is named (by Lumo as usual) and saved as doc in dedicated Lumo-folder on my Drive. Dialog opens in Lumo: "I have saved the chat as a doc in your Lumo folder on Drive. Do you want me to upload it to your Lumo Project folder X?" (the chat being an x-topic) I can answer "Yes/No" depending on, whether I want this or not.

   This is just from the top of my head, so please be critical about unnecessary complexity, best data flows and architectural robustness and scalability

   Integration between Lumo and Docs to allow Lumo users to save chats as Docs on Drive, directly from Lumo.

   Purpose: to ease UX of organising projects in Lumo and save time and effort for users.
   Value:
   1) Nudging users to support their own data security, by not using alternative tools outside of Proton Suite.
   2) Supporting user loyalty to Proton product suite, especially Lumo.

   User scenario:
   After finishing chat with lumo I press the "save as docs"-button next to "copy" and "try again features" in the bottom right corner of the screen. Dialog opens and asks: "Do you want to… more

   11 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Search not just Lumo chats titles but also content

   The sidebar allows searching in chat titles, but I am unable to easily find on how to search in the chats content (in my questions and Lumo replies). I am aware that i can use browser Ctrl+F to search in current chat, but not in all available chats).

   Ideas:
   - after you type the search query, maybe hitting enter can execute search in content.
   - content search included by default, only the matches in chat titles will be displayed on the top of the search results

   clicking on a content search result, should jump to a correct place in the corresponding chat where is a 1st match, maybe allowing some action buttons to jump to next matches.

   The sidebar allows searching in chat titles, but I am unable to easily find on how to search in the chats content (in my questions and Lumo replies). I am aware that i can use browser Ctrl+F to search in current chat, but not in all available chats).

   Ideas:
   - after you type the search query, maybe hitting enter can execute search in content.
   - content search included by default, only the matches in chat titles will be displayed on the top of the search results

   clicking on a content search result, should jump to a correct place in the… more

   49 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. allow copying history conversation into the projects that we create.

   currently there isn't an option to copy old chats into new projects. why? this is quite disturbing and prevent us from organizing our old conversations.

   10 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Lumo Scheduling Automation

    I went down the rabbit hole of trying to create a scheduled web search on specifict topics. Lumo repeatedly told me it had automation to do this but when I tried to set it up it ended up apologising each time saying it got a bit excited but can't do what it said it could...
    Functionality request - automation that will run a scheduled task/search/etc

    12 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Think and respond in the user's English variant, with full regional settings for Lumo (units, currency, time zones + more)

    Lumo has language selection, but no regional settings governing how it formats measurements, currency, dates and times in its responses, or how it reasons within them. For users outside the US this is constant friction. Critically, these settings should shape how Lumo thinks, not just how it writes: drafting a document in British English should mean composing it in British English from the first word, rather than generating American English and converting the spelling afterwards.

    Requested options, ideally as one Region preference with independent sub-settings:

    1. English variants with full grammar, punctuation, vocabulary and idiom rules (en-GB, en-AU, en-NZ, en-IE, en-CA, en-IN, en-ZA, en-US), rather than one undifferentiated English that defaults to American.

    2. A separately selectable spelling and proofreading variant, independent of interface language.

    3. A temporal awareness toggle (choose whether Lumo knows the current date and time, for privacy), with a user-set default time zone including fractional offsets (UTC+5:30, +5:45, +12:45), correct daylight saving rules per region, a 24-hour or 12-hour clock, and unambiguous offset rendering for cross-zone times.

    4. Measurement units: user-selectable metric or imperial, governing both how Lumo expresses quantities and how it interprets input.

    5. Temperature scale (Celsius or Fahrenheit) as an independent setting.

    6. Default display currency, so financial figures do not assume USD.

    7. Date format independent of language variant (DD/MM/YYYY, MM/DD/YYYY, ISO YYYY-MM-DD, YYYY/MM/DD, D.M.YYYY), plus alternative calendar systems (Hijri, Hebrew, Japanese era, Thai Buddhist, Persian, Indian Saka, Chinese lunisolar among others). This prevents consequential misreadings such as 09/01/2026, two entirely different dates eight months apart depending on the reader's convention.

    8. Calendar week-start day (Monday, Sunday or Saturday, per the user's convention), with ISO week numbering as an option.

    9. Holiday awareness: regional terminology (public, bank, federal, statutory holidays), sub-national variation, correctly named Lunar New Year variants (Spring Festival, Seollal, Tet, Losar, Tsagaan Sar, Imlek), other East and Southeast Asian observances, religious observances across all major traditions (with an option to surface global ones), school holidays and academic terms per jurisdiction (academic year boundaries differ between hemispheres), and moon phases and lunisolar calendar display. Multi-jurisdiction families and remote students should be able to subscribe to several calendars at once.

    10. Financial year conventions: calendar year, 1 July to 30 June (Australia, NZ), 1 April to 31 March (India, Japan), 6 April to 5 April (UK personal tax), 1 October to 30 September (US federal), and a custom start date for anywhere else, so financial year reasoning stops assuming the calendar year.

    11. Number formatting: regional decimal and thousands separators (1,234.56 / 1.234,56 / 1 234,56 / 1'234.56), Indian lakh and crore digit grouping, Arabic-Indic numerals, and East Asian myriad grouping.

    12. Paper size conventions: ISO A and B series, US Letter and Legal, JIS B and traditional Japanese sizes, ANSI, and Latin American formats.

    13. Region-appropriate cultural references in examples (pricing, quantities, institutions) rather than US defaults.

    14. Academic citation styles (Harvard, APA, MLA, Chicago, Oxford) as a selectable preference.

    15. Toggles controlling whether each setting also applies in Ghost Mode chats, so ephemerality does not cost users their regional settings.

    Ideally these would be managed at Proton Account level and available across all applicable Proton apps, applied either globally or per app, configured once and synced everywhere.

    The examples above are illustrative, not exhaustive: the underlying request is that these options cover the conventions in use by everyone in every country globally, with custom options catching the remainder. No Proton user should find their regional reality unrepresentable.

    Competitor landscape: Apple's Language and Region settings already allow independent configuration of these conventions at OS level, inherited by Siri and Apple Intelligence. No major AI assistant (ChatGPT, Gemini, Claude, Copilot) currently offers structured regional settings natively; users resort to character-limited custom instructions that are inconsistently honoured. Proton would be the first AI assistant to ship them.

    Full detail for every item, with regional examples, is posted in the comments below. Please vote if you would like to see these features added :)

    Lumo has language selection, but no regional settings governing how it formats measurements, currency, dates and times in its responses, or how it reasons within them. For users outside the US this is constant friction. Critically, these settings should shape how Lumo thinks, not just how it writes: drafting a document in British English should mean composing it in British English from the first word, rather than generating American English and converting the spelling afterwards.

    Requested options, ideally as one Region preference with independent sub-settings:

    1. English variants with full grammar, punctuation, vocabulary and idiom rules (en-GB, en-AU, en-NZ, en-IE, en-CA,… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Lumo integration in meet for meeting summaries & transcriptions

    It would be great if the upcoming meet app would have an option to summarize and transcript meetings.
    Making this possible with a trustful AI like Lumo would be amazing (and I think no one else has a meeting transcription feature with a trustful AI)

    23 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Ability to edit chat names (especially in projects).

    The automated chat names often aren't relevant to the topic. The ability to edit them would be helpful, especial for projects.

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Bring real-time encrypted voice interaction to Lumo using existing MLS/WebRTC infrastructure

    Live Voice Conversation Mode for Lumo — Powered by Proton Meet's Proven Architecture

    Summary: Enable bidirectional voice conversation in Lumo's mobile apps — speak through a Bluetooth headset, receive spoken responses via text-to-speech — creating a Gemini Live-style hands-free experience. Proton Meet already solves the hardest engineering challenges for real-time encrypted audio. Extending this to Lumo is a natural evolution, not a fundamental R&D problem.

    The Opportunity
    Lumo's mobile app supports voice input (speech-to-text) but lacks voice output (text-to-speech) and continuous conversation mode. Users who want hands-free, private AI interaction — while driving, walking, cooking, exercising, or working — have no privacy-preserving alternative to Gemini Live, Siri, or Google Assistant. All of those services harvest voice data for training and profiling.

    This is both a feature gap and a market differentiation opportunity: Proton could offer the only AI voice assistant where your spoken conversations are encrypted, never logged, and never used for training.

    Technical Feasibility: Proton Meet Already Did the Hard Part
    Proton Meet currently delivers real-time, end-to-end encrypted audio for up to 250 participants using a proven, battle-tested architecture:

    Component Proton Meet Implementation Applicability to Lumo Voice Mode
    Audio capture & encoding WebRTC stack with Opus codec Same stack would power Lumo voice capture/playback
    Real-time encryption AES-256-GCM, encrypted on-device before transmission Same encryption protects voice data in transit to/from Lumo backend
    Key management MLS (Messaging Layer Security, RFC 9420) — IETF standard co-developed by Proton team members Adapts directly for 1:1 user-to-AI session (simpler than group calls)
    Forward secrecy Automatic key rotation per MLS epoch Ensures each voice session is independently secured
    Authentication Secure Remote Password (SRP) protocol Same system already used for Proton Account logins and Meet access
    Server architecture Selective Forwarding Unit (SFU) via LiveKit Cloud — forwards ciphertext only, never decrypts Lumo backend could process only encrypted requests, same zero-knowledge principle
    No-log policy No meeting content, metadata, or participant graphs retained after call ends Same standard applies — voice sessions leave no trace
    Infrastructure Distributed European data centers, outside US jurisdiction Same infrastructure hosts Lumo
    Bottom line: The cryptographic pipeline for real-time encrypted audio already exists, is audited, is open source, and is in production. Adapting it for a 1:1 user-to-AI voice session is architecturally simpler than what Proton Meet already handles for 250-person group calls with dynamic key rotation.

    Proposed Implementation
    Phase 1 — Core Voice Mode (6 months):

    Tap-to-talk: press to speak, release for response
    Streaming TTS output through device speaker or Bluetooth headset
    Audio encrypted on-device using MLS-derived keys before sending to Lumo backend
    Lumo processes the transcribed text (or encrypted audio) and returns a text response
    Response converted to speech via on-device TTS engine
    Zero audio or transcription retained after session ends
    Phase 2 — Continuous Conversation (12 months):

    Hands-free mode: wake word or button activation for back-and-forth dialogue
    Conversation state maintained across exchanges within a session
    Interruptible responses (user can speak over the AI, like Gemini Live)
    Voice activity detection (VAD) to know when the user has finished speaking
    Phase 3 — Advanced Features (ongoing):

    Voice customization (select TTS voice, speed, language)
    Multilingual voice support (leveraging Lumo's existing 11-language support)
    Offline TTS via on-device models (no audio leaves the device for output synthesis)
    Optional local speech-to-text via on-device Whisper or similar model (input never leaves device)
    Voice biometric authentication (optional, user-opt-in, for hands-free session access)
    Privacy Architecture: Where Proton Differentiates
    Competing voice assistants (Gemini, Siri, Alexa, Google Assistant) share a fundamental flaw: they collect, transcribe, and retain voice data on corporate servers for training, advertising profiling, and analytics. Users have no meaningful control over what happens to their voice after it leaves their device.

    Proton's architecture offers a fundamentally different model:

    1. Local Processing Where Possible

    Speech-to-text can run on-device (Android provides native STT APIs; Whisper models run locally on Pixel-class hardware)
    Text-to-speech runs locally via Android's native TTS engine or third-party on-device models (e.g., Piper)
    When both STT and TTS are local, raw audio never leaves the device — only encrypted text is sent to Lumo's backend for processing
    2. Encrypted Transit When Cloud Processing Is Needed

    If cloud-based STT/TTS is required (for accuracy, multilingual support, or low-resource devices), audio is encrypted on-device using MLS-derived AES-256-GCM keys before transmission
    Lumo's backend processes only encrypted data and discards it immediately — same zero-knowledge architecture as Proton Meet
    3. No Retention, No Training

    Voice sessions are ephemeral — no audio, transcriptions, or metadata retained after the session ends
    Voice data is never used to train models (consistent with Lumo's existing zero-training policy)
    No voice fingerprints or biometric profiles stored
    4. Transparent and Auditable

    All client code is open source (consistent with Lumo's existing open-source mobile apps)
    MLS implementation is a public IETF standard — anyone can verify the cryptographic protocol
    Independent security audits (Proton is ISO 27001 certified and SOC 2 Type II attested)
    Market Positioning
    This isn't feature parity with competitors — it's a privacy protection opportunity. Every user who currently uses Gemini Live, Siri, or Alexa because they need hands-free AI is accepting surveillance as the price of convenience. Proton can offer the same convenience with zero surveillance.

    Target audiences:

    Privacy-conscious consumers who avoid voice assistants because they don't trust Big Tech with their voice data
    Professionals handling sensitive information (lawyers, journalists, healthcare workers, executives) who need hands-free AI but can't risk voice data being harvested
    Accessibility users who depend on voice interaction and deserve privacy without compromise
    Enterprise Lumo for Business customers where voice data retention creates compliance risk under GDPR, HIPAA, and similar regulations
    Revenue Potential
    Lumo Plus differentiator: Live voice mode as a premium feature driving Plus subscriptions
    Lumo for Business upsell: Encrypted voice AI for enterprise — a capability no competitor offers with zero-access encryption
    Future hardware partnership opportunity: Licensed secure audio SDK for certified Bluetooth headset manufacturers, bundling with Lumo Plus subscriptions ("Proton Audio Suite")
    Community Need
    Real-world use cases where private voice AI matters:

    Driving: Ask questions, get directions, hear summaries — without sending voice to Google or Apple
    Physical work: Cooking, gardening, repairs — hands occupied, need voice interaction
    Health and medical: Asking sensitive health questions aloud — voice data is especially intimate
    Professional: Dictating notes, drafting documents, brainstorming — work product shouldn't be mined
    Accessibility: Visually impaired users or those with motor limitations who rely on voice and deserve privacy equal to sighted users who can type
    Recommendation
    Prioritize Phase 1 in the current mobile app development cycle. The architecture is proven (Proton Meet), the market demand is demonstrated (Gemini Live adoption), and the privacy differentiation is unmatched. This is a case where Proton can leapfrog competitors by applying existing internal expertise to a new modality.

    I am willing to participate in beta testing and provide detailed feedback throughout development.

    Live Voice Conversation Mode for Lumo — Powered by Proton Meet's Proven Architecture

    Summary: Enable bidirectional voice conversation in Lumo's mobile apps — speak through a Bluetooth headset, receive spoken responses via text-to-speech — creating a Gemini Live-style hands-free experience. Proton Meet already solves the hardest engineering challenges for real-time encrypted audio. Extending this to Lumo is a natural evolution, not a fundamental R&D problem.

    The Opportunity
    Lumo's mobile app supports voice input (speech-to-text) but lacks voice output (text-to-speech) and continuous conversation mode. Users who want hands-free, private AI interaction — while driving, walking, cooking, exercising, or working — have… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Lumo and big projects

    Lumo + big projects - when working inside the project, all of the files added should be added to the project, not to the chat. I have a very large self reference files that when added imediately consume 1/2 od the available tokens.
    There should also exist an option to share a local directory with all the files needed so they don't use space in the chat.

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Local agent June powered by Lumo

    Please integrate with a local agent like June

    https://www.opensoftware.co/june

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Report Carbon equivalent footprint of a user requests

    I think I do not have to explain that energy consumption of LLMs even doing only inférence is high.
    Since Proton has always promoted transparency over source code of its tools, I believe it should also pioneer transparency on this matter.
    There exist libraries to wrap function calls and estimate co2 équivalent (e.g. mlco2)

    44 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. VSCode integration

    Other LLM's like ChatGPT and Claude have integration with VSCode. It would be great to see an integration for that or another opensource IDE.

    The most amazing thing would be if you can replace all the things most people use day to day with apps and have full support on Linux.

    43 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Please add Biometric (fingerprint) unlock to Lumo

    Please add Biometric (fingerprint) unlock to Lumo (and Calendar), it and Calendar seem to be the only Proton apps that do not have this feature.

    25 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Feature Request: "Amnesia Bridge" – Cross-Chat Context Retrieval

    When chats close due to resource limits, all invested context is lost. Users must re-upload files and start from scratch—wasting time and compute.

    Proposal: Let users selectively pull context from older chats into active conversations: "Lumo, check our chat from last week for what we found about XY." -> the desired feature is similar to "websearch" - just scoping the own (internal) activities.

    Optional: User tagging of important chats for quicker discovery.

    Why it fits: Same privacy model, just extended. Decryption stays client-side, metadata stays user-controlled and encrypted. No server-side indexing.

    Impact: Better session continuity, no redundant uploads, preserves invested work.

    When chats close due to resource limits, all invested context is lost. Users must re-upload files and start from scratch—wasting time and compute.

    Proposal: Let users selectively pull context from older chats into active conversations: "Lumo, check our chat from last week for what we found about XY." -> the desired feature is similar to "websearch" - just scoping the own (internal) activities.

    Optional: User tagging of important chats for quicker discovery.

    Why it fits: Same privacy model, just extended. Decryption stays client-side, metadata stays user-controlled and encrypted. No server-side indexing.

    Impact: Better session continuity, no redundant uploads, preserves invested… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating