598 results found

1. Recurring events for weekdays only! Or custom days of the week!

   Literally just let me use a checkbox for specific days of the week! I can't click "Every weekday" for a recurring meeting.

   My use case is to set meetings that are the same meeting every day from Mon-Thurs, and they recur every week. This seems impossible without creating 4 events... 1 for each day of week.. but I want the notes and meeting invite to be ONE!

   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

   1 comment  ·  Changes to existing features  ·  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. 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

3. 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.

   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

   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

4. Ability to delete attached files instead of only excluding them

   Files marked as "Excluded" aren't truly removed—they're just moved to another section. There's no clear way to actually remove files from a chat.

   Requested: Clear file removal/deletion options that actually removes files from the chat context.

   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

   0 comments  ·  Changes to existing features  ·  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. 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

6. Text size adjustments

   Implement an option in settings to make the text bigger in the mobile apps. Specifically IOS. Global text size adjustment has no affect on the Lumo application. Results are too small. Needs to be more clear like ChatGPT for example.

   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

   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

7. Native Mermaid diagram rendering in Lumo chat interface

   Description:

   Mermaid.ai is the de facto standard for text-to-diagram visualization, natively supported by GitHub, GitLab, Notion, Obsidian, and VS Code. Currently, when Lumo generates Mermaid syntax in a fenced ```mermaid code block, the Lumo web UI displays it as raw text instead of rendering the diagram visually. This significantly reduces the utility of Lumo for technical users who rely on diagrams — flowcharts, sequence diagrams, architecture diagrams, state machines, ER diagrams, and more.

   Proposed implementation:

   Integrate the Mermaid.js library into the Lumo web UI Markdown renderer to automatically detect and render ```mermaid fenced code blocks as interactive SVG diagrams within chat messages.
   Support the full range of Mermaid diagram types (flowchart, sequence, class, state, ER, Gantt, journey, timeline, mindmap, gitGraph, etc.).
   Ensure rendering occurs client-side to maintain Lumo's zero-access encryption and privacy-first architecture.
   Consider a fallback: if rendering fails, display the raw Mermaid source with a copy button.
   Extend support to the iOS and Android apps where feasible.

   Why this matters:

   Lumo already generates Mermaid syntax in responses — the gap is purely in rendering.
   Competing AI assistants (Claude, ChatGPT, Gemini) render Mermaid natively.
   The Mermaid.js library is lightweight, MIT-licensed, and runs entirely in the browser.
   Privacy is preserved: no server-side diagram generation is required.
   Technical professionals (developers, architects, IAM consultants) represent a key Lumo Plus subscriber demographic that depends heavily on visual documentation.
   Related existing requests:

   Syntax-highlighted code blocks (18 votes on UserVoice) — Mermaid rendering would naturally complement this feature.

   Description:

   Mermaid.ai is the de facto standard for text-to-diagram visualization, natively supported by GitHub, GitLab, Notion, Obsidian, and VS Code. Currently, when Lumo generates Mermaid syntax in a fenced ```mermaid code block, the Lumo web UI displays it as raw text instead of rendering the diagram visually. This significantly reduces the utility of Lumo for technical users who rely on diagrams — flowcharts, sequence diagrams, architecture diagrams, state machines, ER diagrams, and more.

   Proposed implementation:

   Integrate the Mermaid.js library into the Lumo web UI Markdown renderer to automatically detect and render ```mermaid fenced code blocks as interactive SVG diagrams within… 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

   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

8. Paid Chat Preservation - Automatic Freeze/Backup Instead of Deletion

   Current Behavior:
   After subscription expiry, all chat history is deleted 7 days later. There is no chat backup functionality currently available.

   Why Manual Backups Fall Short:
   Relying on users to manually export or back up chats defeats the purpose of a seamless subscription model. Manual backups are reactive and easy to forget - automatic preservation should be the default expectation for paid users.

   Proposed Solutions:
   1. Freeze/Hide Logic (Lumo 1.x style): When subscription ends, chats become read-only or hidden rather than deleted
   2. Automatic Drive Integration: Proton Drive auto-backups for chat history at regular intervals
   3. Grace Period Extension: Longer retention window during subscription pauses

   Use Case:
   I want flexibility to pause Lumo temporarily without losing months of conversation history. Deleting chats after 7 days creates a "pay-to-win" dynamic where continuous payment becomes mandatory to retain data.

   Impact on Paid Customers:
   This policy punishes legitimate usage patterns (seasonal use, budget cycles, trial periods). A better approach would preserve data integrity while allowing subscription flexibility.

   Current Behavior:
   After subscription expiry, all chat history is deleted 7 days later. There is no chat backup functionality currently available.

   Why Manual Backups Fall Short:
   Relying on users to manually export or back up chats defeats the purpose of a seamless subscription model. Manual backups are reactive and easy to forget - automatic preservation should be the default expectation for paid users.

   Proposed Solutions:
   1. Freeze/Hide Logic (Lumo 1.x style): When subscription ends, chats become read-only or hidden rather than deleted
   2. Automatic Drive Integration: Proton Drive auto-backups for chat history at regular intervals
   3. Grace Period Extension: Longer… 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

   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

9. use Drive and Docs as Lumo memory for avoiding the bottle neck that brings us "chat too long". thanks

   2 problems. 1. chats cut off due to bottle neck or lack of live memory to back up lumo. 2. Having to cut paste constantly while working to avoid loss of "condensing" the chat. Can proton apps act as backup and active chat memory? Since the subject is often revisited for context. ? Need 2 way data movement between Drive/ Docs and Lumo. Integrate infrastructure.

   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

   0 comments  ·  Changes to existing features  ·  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. Edit/Remove content pasted in to project chats from project files

    Right now if you paste a a large enough block of text in to a project chat it coverts it to a text file and it will be added to the over all project context that Lumo has access to. But, once this content is pasted in to one chat, even if that chat is deleted the pasted content text file from the still stays in the project knowledge and all future chats will then use that as context for the project and it cannot be edited or removed.

    This request is to allow us to edit/remove these pasted text blocks from project knowledge. Or to have them upload to the connected proton drive so we can edit or remove then from there.

    Right now if you paste a a large enough block of text in to a project chat it coverts it to a text file and it will be added to the over all project context that Lumo has access to. But, once this content is pasted in to one chat, even if that chat is deleted the pasted content text file from the still stays in the project knowledge and all future chats will then use that as context for the project and it cannot be edited or removed.

    This request is to allow us to edit/remove these pasted text… 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  ·  Changes to existing features  ·  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. Fix "Context Length Exceeded" on moderate-sized log files

    "Context Length Exceeded" errors when uploading moderately sized log files (even 1-5 MB text files) to Lumo for analysis despite the theoretical 128k token context window.

    Use case: As an IT administrator managing cloud infrastructure, I need to analyze server logs, error traces, and security events. Other AI assistants handle multiple large log files without issue. Lumo currently dumps entire file content into the prompt, consuming all available context upfront.

    Thank you for considering this feedback. Privacy-first AI with practical file handling capabilities would make Lumo indispensable for professionals managing sensitive data.

    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

    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

12. Downloadable document generation

    I noticed Lumo AI lacks on document generation. No option to generate downloadable document such as text, pdf, markdown, excel, powerpoint, open document, etc. I suggest this should be available as it is a norm/standard feature of an AI.

    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

    0 comments  ·  Changes to existing features  ·  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. make it easy as possible to run Lumo from a home server - its a win for all but especially Proton

    Proton allows you to download and run your own version, but I just read the instructions and its not trivial. Its in the interest to Proton to do so. The user takes on costs for power, space, and cooling. An analogy: a german telcom created a virtualized TV set top box. The TV interface was streamed and effectively ran like a video game. The home only required a simple USB stick that ran DRM and some controls. This cost about 30 euro and the user would self install, just plug it into their smart TV. This replaced a 100 Euro set top box and a service call to do the install (150 Euro). Seems simple no? What they didnt consider is the home owner pays the power and space of the STB, this was a net new cost the Telco had to take on. And you have to build out for peak demand even when no one is watching. It was a massive failure. This is why distributed AI "on the edge" of the network makes financial sense. Let the user take on the power and space costs. The benefit to the user is complete sovereignty and privacy. But it will never be popular unless you make trivially easy. Do a deal with some hardware vendor to sell preconfigured rasberry pi boxes with a simple wizard interface to configure it. Provide the home version with security updates etc.

    Proton allows you to download and run your own version, but I just read the instructions and its not trivial. Its in the interest to Proton to do so. The user takes on costs for power, space, and cooling. An analogy: a german telcom created a virtualized TV set top box. The TV interface was streamed and effectively ran like a video game. The home only required a simple USB stick that ran DRM and some controls. This cost about 30 euro and the user would self install, just plug it into their smart TV. This replaced a 100 Euro… 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

    0 comments  ·  Changes to existing features  ·  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. Add an incognito mode to not include memories for unbiased chats

    Lumo is great and the memory feature is great. However sometimes it would be nice to have a chat without it having all that extra memory context to have a simple unbiased, impartially neutral chat for times where all the memory content is making things "too" personalised with the angles it takes.

    It would also come in handy when someone is next to you and asks "Can you ask Lumo about XYZ" and then you search. With an incognito feature, if you're asking it questions about someone else's issues it won't blurt out for everyone reading things like "It's not that different than your [insert personal PRIVATE topic here] issue." because it wouldn't know any of your prior history/memory for that new chat.

    Lumo is great and the memory feature is great. However sometimes it would be nice to have a chat without it having all that extra memory context to have a simple unbiased, impartially neutral chat for times where all the memory content is making things "too" personalised with the angles it takes.

    It would also come in handy when someone is next to you and asks "Can you ask Lumo about XYZ" and then you search. With an incognito feature, if you're asking it questions about someone else's issues it won't blurt out for everyone reading things like "It's not… 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

    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

15. All-day events show as "Free"

    I'd like to mark all-day events as "Free." This is especially important on shared calendars, because if I have, say, a birthday marked on my Proton calendar, it blocks off my entire work calendar (Outlook) because it thinks I'm busy all day.

    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  ·  Changes to existing features  ·  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. Project Threads Lack Clear Memory Architecture

    Title: Project Threads Lack Clear Memory Architecture—Choose Privacy OR Context, Not Neither
    Category: General Ideas / Lumo

    The Current Problem:

    Lumo's v2.0 persistent memory aggregates content from general chat threads—but excludes project threads from memory aggregation. However, project threads remain indexed and searchable by keyword within the account.

    This creates a contradictory state with no tangible benefit:

    No context continuity — When you mention a project topic in a general chat, Lumo doesn't know the project exists or have any history to reference
    No real privacy — Project content is still searchable/indexed, so it's not a true "black box"
    No security gain — A snooper with account access can find project content via search; a locked memory system wouldn't add protection
    

    Current State:

    Projects: NOT aggregated → memory = incomplete
    Projects: Still indexed → search = works
    Result: Worst of both worlds (loss of convenience, no privacy benefit)
    

    Proposed Solutions (Either/Or):

    Option A: True Private Project Mode

    Project threads are fully gated—requires PIN/code entry to access
    Content excluded from both memory and search indexing
    Opt-in only (user explicitly locks a project)
    For sensitive work that needs genuine isolation
    

    Option B: Full Memory Aggregation

    Project threads feed into Lumo's persistent memory like general chats
    Content indexed and searchable (current behavior)
    Cross-thread context works seamlessly
    For users who prioritize functionality over isolation
    

    Option C: Hybrid Approach (Recommended)

    Default: Project threads aggregate to memory AND indexed
    User can enable "PIN Lock" on specific projects
    Locked projects: Excluded from memory, excluded from search
    Requires authentication to view or discuss locked project content
    Dual-memory system: General memory + Project-only memory (accessible after PIN unlock)
    

    Why This Matters:

    Users managing multiple projects (business startup, technical documentation, etc.) need consistency. If project threads are meant to be private, make them private. If they're meant to support context continuity, let them aggregate.

    The current halfway measure provides neither benefit.

    Requested Action: Implement gatekeeping (PIN/code) for project threads with dedicated project memory upon unlock. Give users explicit control over whether their project content feeds into general memory or stays isolated.

    Title: Project Threads Lack Clear Memory Architecture—Choose Privacy OR Context, Not Neither
    Category: General Ideas / Lumo

    The Current Problem:

    Lumo's v2.0 persistent memory aggregates content from general chat threads—but excludes project threads from memory aggregation. However, project threads remain indexed and searchable by keyword within the account.

    This creates a contradictory state with no tangible benefit:

    No context continuity — When you mention a project topic in a general chat, Lumo doesn't know the project exists or have any history to reference
    No real privacy — Project content is still searchable/indexed, so it's not a true "black box"
    No

    … 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

    0 comments  ·  Changes to existing features  ·  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. Shared Calendar Colors

    So when you share a calendar or invite someone else to it, it would be great or hugely beneficial if it would also save and use the specific colors people have already set for certain event types.
    Because currently it only shows all events in that shared calendar with the default color and the new users would have to change the colors for the respective event individually and manually, which kind of defeats the purpose of a shared environment if you ask me. I mean should each individual user still be able to change colors independently? Sure why not, but I think the default should be: Sync all events and their corresponding colors.

    So when you share a calendar or invite someone else to it, it would be great or hugely beneficial if it would also save and use the specific colors people have already set for certain event types.
    Because currently it only shows all events in that shared calendar with the default color and the new users would have to change the colors for the respective event individually and manually, which kind of defeats the purpose of a shared environment if you ask me. I mean should each individual user still be able to change colors independently? Sure why not, but… 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

    0 comments  ·  Changes to existing features  ·  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. Offline access to Lumo chats & local search (like Proton Drive)

    I'd like to propose a new feature for Lumo that enables access to chat histories without an internet connection – similar to the "Make available offline" function in Proton Drive.

    Use Case: Users want to read and search through specific chats or project histories while offline (e.g., on a plane, in areas with poor connectivity, or for privacy reasons). Currently, Lumo is only usable online, which limits access to your own conversation data.

    Proposed Features:

    1. Offline toggle for chats:
       Like in Proton Drive, users should be able to mark individual chats (or entire projects) with a toggle as "Available offline." These would then be stored locally on the device, fully encrypted.

    2. Two export modes:

    • Full-text mode: The complete chat history is made readable offline (including all details and discussion threads).
    • Summary mode: Users can select multiple chats to generate a compact, Lumo-created summary available offline.

    1. Local search with navigation:

    A full search within the offline-saved chats that:

    • Highlights found terms in color.
    • Allows navigating up/down between search results.
    • Works entirely without internet (indexing happens locally).

    Why this is valuable:

    • Increases the practical usability of Lumo in situations without internet.
    • Provides continuity in long-term projects and conversations, even offline.
    • Leverages proven Proton principles (encrypted local storage) and extends them to chat data.
    • Universally useful – not limited to specific use cases but beneficial for anyone who wants to work flexibly.

    Technical Feasibility: The infrastructure for encrypted local storage already exists in Proton Drive. Extending this to chat data would be a logical evolution. Local search is technically achievable since the text resides on the device after download.

    I'd like to propose a new feature for Lumo that enables access to chat histories without an internet connection – similar to the "Make available offline" function in Proton Drive.

    Use Case: Users want to read and search through specific chats or project histories while offline (e.g., on a plane, in areas with poor connectivity, or for privacy reasons). Currently, Lumo is only usable online, which limits access to your own conversation data.

    Proposed Features:

    1. Offline toggle for chats:
       Like in Proton Drive, users should be able to mark individual chats (or entire projects) with a toggle as "Available offline."… 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

    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

19. Allow Lumo to deal with Memory reduplicates

    I notice the memory list often has either exact duplicates or very similar worded info. I presume there is some kind of self-check to see if a memory has already been added. But its not quite up to standard.
    May i suggest can we give Lumo permission to comb through the memory and weed out duplicates or too similar ones. If there are edge cases it could apply a tag for a special filter called User Attention Needed (or something) and we can click on this button that is lit up when it has memories to assess and we only see the list of edge case memories and each one has a green tick button to approve or X to delete and a pencil icon to edit and once done we can tap the green tick button to allow it back into the main memories (and of course remove the special filter tag)

    Also to further enhance this idea, add search bar so we can see if what certain topics might be listed. And we could also filter our own manual memory entries with a command in the search bar: #you or /you

    I notice the memory list often has either exact duplicates or very similar worded info. I presume there is some kind of self-check to see if a memory has already been added. But its not quite up to standard.
    May i suggest can we give Lumo permission to comb through the memory and weed out duplicates or too similar ones. If there are edge cases it could apply a tag for a special filter called User Attention Needed (or something) and we can click on this button that is lit up when it has memories to assess and we only… 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

    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

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