598 results found

1. In-Chat Search with Navigation (Next/Previous) & Highlighting

   While browser shortcuts like Ctrl+F can search the currently visible text, they lack integration and advanced features needed for long conversations. I request a dedicated "Search in this chat" function built directly into the Lumo interface.

   Specific requirements:

   A native search bar within the chat thread (not relying on browser tools).
   Typing a keyword jumps directly to the relevant message(s) within the current thread.
   Highlight all matches visually.
   Navigation controls: "Next" and "Previous" buttons to cycle through multiple matches efficiently.
   Ideally, a counter showing "Match X of Y".
   This is a critical usability feature for power users who treat Lumo as a long-term knowledge base (e.g., tracking pet health logs, creative drafts, or complex analyses). It would save immense time and frustration when retrieving specific details from extensive conversation histories.

   While browser shortcuts like Ctrl+F can search the currently visible text, they lack integration and advanced features needed for long conversations. I request a dedicated "Search in this chat" function built directly into the Lumo interface.

   Specific requirements:

   A native search bar within the chat thread (not relying on browser tools).
   Typing a keyword jumps directly to the relevant message(s) within the current thread.
   Highlight all matches visually.
   Navigation controls: "Next" and "Previous" buttons to cycle through multiple matches efficiently.
   Ideally, a counter showing "Match X of Y".
   This is a critical usability feature for power users who treat Lumo… 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

2. Screenshot -> Proton Drive + directly added in Lumo's chat/project

   WARNING: what i am suggesting does exist if you use "change destination" of the screenshot program you use to save the images in a Proton Drive folder that will upload the pictures and so on. So please understand that what i will suggest is actually MORE then this and it's DIRECTLY linked to Lumo. AKA no, this is NOT a proton Drive suggestion => NO this is NOT a duplicate of existing suggestion exactly because i am suggesting MORE.

   That is also why:
   I will NOT explain in details why it's needed because it's absurd to assume that you even would need what i will suggest if you don't understand it.

   Lumo, new tool -> screenshot.

   In settings -> Timmer, format (like png), whole screen or snip so on and on, all this are the typical screenshot stuff.

   But the idea of it being from proton = it is saved directly in proton drive, not on the PC disk.

   And on the idea that proton drive can be linked to projects (or reverse i guess is more correct?) well that is why i said: NEW TOOL.

   As in we are in LUMO CHAT! we press tools and screenshot and we can take a picture and Lumo get's the screenshot directly.

   And what people don't get is the following: Upload image requested... how many of you saw this when dealing with bureaucracy or other document or evidence or similar? as in Lumo to have screenshots so well integrated that it can show us click butons.

   Can you show me situation a (click to upload) and situation b (click to upload)

   Or

   Click here to take a screenshot of situation a if you press "shortcut key combination" and, then, again, for situation b.

   Note: both files are save on proton drive's subfolder that is linked to this chat.

   Above is an illustrative example. idea is that we don't need to create any folder, we don't need to link anything. we don't need to upload anything. it's exactly how the take a photo via phone, but screenshot. But it also allows Lumo to directly associate screenshots with specific topics aka eliminating everything else, all the other information, in that picture.

   As in the Proton Drive, will have the screenshots = we can do cross platform chat <- again, the take photo via phone's camera is the best example.

   With the main idea is that the screenshots (and i guess phone photo?) are saved in a specific Proton Drive that is associated with the particular chat or project <- chat/project name + timestamp + all in one folder might be more easy to implement since the idea of Lumo can't create folders in Proton Drive.

   Anyways. Idea is that, the the advantages of screenshots done by proton for 100% privacy, no microsoft or apple or google or whatever log, and of course the idea is that if it's saved on proton drive via Lumo chat, Lumo can associate the image with specific information.

   As in image memory. In the memory function to have a "files xyz" - has the following information

   like this, if we just mention that information, it will trigger Lumo to check the image related information to search for that information and tell use which file is the one having that information. Or reverse, i want to check something, it's regarding case A, B, and C, can you also check image memories? And then lumo will check the images as say what information it has regarding A B and C <- Aka insted of checking hundrends of documents, insted of creating documents, insted of doing web search, you simple do a screenshot and well that is all the info you need. And it's instant and more.

   so again, what i suggest is not the same as the other suggestion that have been made, aka it's not a duplicate.

   But it's screenshots that are done and stored via Proton Drive (i mean it already has docs and sheets, why not screenshot on top?) with the purpose of it being for them to be directly added to chat's with Lumo as in: Lumo can add meaning to the pictures, direct and clear. No confusion. Anything irrelevant can be filtered out while also allow to unfiltered if there are relevant information ALL while giving the advantages of screenshot (quick, instantly, no create folder, no name file, nothing, it's simple and fast and most of all, efficient QoL)

   WARNING: what i am suggesting does exist if you use "change destination" of the screenshot program you use to save the images in a Proton Drive folder that will upload the pictures and so on. So please understand that what i will suggest is actually MORE then this and it's DIRECTLY linked to Lumo. AKA no, this is NOT a proton Drive suggestion => NO this is NOT a duplicate of existing suggestion exactly because i am suggesting MORE.

   That is also why:
   I will NOT explain in details why it's needed because it's absurd to assume that you even… 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

3. Support for audio and creative file formats (.wav, .als, etc.)

   When working on music production projects (Ableton Live), I can't upload the files I actually use:

   .wav files are rejected — drag and drop returns "Unsupported file type"
   .als files are greyed out in the file picker
   I chose Lumo Plus because privacy matters for my creative work, but I can't even load the files I work with. Could support for common audio/creative formats be added?

   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. Lumo Watchlist & Scheduled Monitoring – Client-Side Alerts for Topic Tracking

   Hi Proton Team,

   I'm a long-time Proton user who relies heavily on GrapheneOS + Lumo as part of a de-Googled mobile workflow. I love that Lumo 2.0 now has private web search and persistent memory — these features make it an incredibly powerful tool for privacy-conscious professionals.

   That said, there's one gap between what Lumo offers today and what would make it a true competitor to mainstream AI assistants with automation capabilities: the inability to set up proactive, scheduled monitoring of topics or changes.

   Currently, if I want to track whether something new has been published about a specific topic (e.g., "Motorola GrapheneOS partnership"), I have to manually initiate a web search each time. This is inefficient and easy to forget. Other AI platforms offer background task scheduling or keyword monitoring, but often at the cost of privacy (they track your interests server-side).

   Proposed Solution
   Enable user-defined scheduled monitoring tasks within the Lumo client (mobile/web app). The concept would work entirely client-side:

   Create a Watchlist Entry — user specifies:

   Query/topic to monitor (e.g., "GrapheneOS Motorola news")
   Frequency (hourly, daily, weekly, custom cron-like interval)
   Comparison criteria (new results only, significant change detected, etc.)
   Alert method (in-app notification, email via Proton Mail)
   Client-Side Execution — the scheduling happens locally on the user's device. Lumo periodically performs web_search autonomously, compares results with baseline state stored locally, and surfaces differences.

   Privacy Preservation — no server-side logging of watchlists or tracking history. Everything encrypted end-to-end where applicable, with zero-access architecture maintained. Optional opt-in for syncing watchlists across devices via encrypted storage.

   Integration with Existing Features — leverage Lumo 2.0's Persistent Memory to remember previous search baselines. Leverage Private Web Search to avoid external data leaks during queries.

   Use Cases
   Journalists/Researchers: Track breaking developments on stories of interest without revealing query patterns.
   Enterprise IT Security: Monitor threat intelligence feeds or vulnerability disclosures relevant to organization infrastructure.
   Legal/Compliance Teams: Watch regulatory updates on specific topics without internal logs revealing sensitive priorities.
   Consumers: Track product releases, policy changes, or service updates privately (like the Motorola-GrapheneOS-Proton scenario we've been discussing).

   Implementation Considerations (Technical Notes)
   Since Proton already supports zero-access encryption, client-side processing, and encrypted sync across devices, most infrastructure pieces may already exist:

   Scheduling: Could run as background task using native OS scheduler (not Lumo server polling)
   Baseline Storage: Local SQLite/IndexedDB with encrypted snapshot of last-known-good state
   Comparison Logic: Simple diff algorithm comparing search result hashes or keywords
   Notifications: Push notifications via standard platform channels (no server involvement beyond delivery trigger)
   Cross-device Sync: Optional, encrypted via Proton's existing key management system
   Key constraint: Do NOT store watchlist definitions on Proton servers unless explicitly encrypted by client (E2EE), and ensure no metadata leakage occurs.

   Why Now?
   With Lumo 2.0 launching on June 30, 2026, featuring image generation, persistent memory, and private web search, the foundation is essentially ready. Adding scheduled monitoring would naturally extend Lumo's unique value proposition as the only AI assistant that doesn't require compromising privacy for automation.

   This feature would differentiate Lumo dramatically from ChatGPT, Claude, Gemini, and Copilot — all of which either track user activity server-side or lack sophisticated background task capabilities.

   Hi Proton Team,

   I'm a long-time Proton user who relies heavily on GrapheneOS + Lumo as part of a de-Googled mobile workflow. I love that Lumo 2.0 now has private web search and persistent memory — these features make it an incredibly powerful tool for privacy-conscious professionals.

   That said, there's one gap between what Lumo offers today and what would make it a true competitor to mainstream AI assistants with automation capabilities: the inability to set up proactive, scheduled monitoring of topics or changes.

   Currently, if I want to track whether something new has been published about a specific topic… 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

5. iOS app swipe side bar on left

   I’d like to be able to swipe the left sidebar with my finger in the iOS app both in and out.

   Right now you have to tap the sidebar toggle.

   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

6. Add Lumo's Logo and Mascot Info to the Knowledge Base

   Users sometimes reference Lumo's logo or mascot during conversations. However, Lumo lacks awareness of these details and must respond with uncertainty when they're brought up.

   Including official branding descriptions in Lumo's knowledge base would allow for accurate responses rather than hedged guesses or deferrals.

   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. Buttons to quickly jump to responses

   It gets annoying to have to manually scroll up or down through Lumo's responses when re-reading conversation history and it would be nice to have up/down buttons on the sides to jump to the top of a previous response or the top of the next one.

   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. Use mouse scrollwheel to change month/day/week in the calendar

   I miss the ability that Google Calendar has in month view, to use the mouse scroll wheel to quickly move between months. It would be great if this feature, or something similar, was implemented in Proton Calendar.

   Along the same lines, a lot of modern mice have a tiltable scrollwheel, and that tilt can be used for horizontal scrolling, so why not make that move to the next day/week/month?

   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. Improve Lumo’s UI/UX for a smoother, more responsive daily experience

   Dear Proton Community and Development Team,

   I would like to suggest improvements to Lumo’s user interface and overall user experience so that it feels smoother, more consistent, and better suited for daily use.

   Privacy and security are very important, and this is one of the main reasons why many users are interested in Proton products. However, for an AI assistant to become part of everyday work, it also needs to feel fast, polished, intuitive, and enjoyable to use.

   My request is specifically about improving the interaction design and visual consistency of Lumo.

   Suggested improvements:

   1. More responsive UI interactions
      Buttons, menus, input fields, and other interactive elements should provide clearer visual feedback when users hover, click, tap, open panels, or send messages.

   2. Smoother animations
      New messages, loading states, chat transitions, and opening or closing panels could feel more natural with subtle, polished animations.

   3. More consistent spacing, borders, and layout
      Some UI elements feel small or visually inconsistent. A more unified design system with consistent spacing, rounded corners, and clearer hierarchy would make Lumo feel more refined.

   4. More polished visual design
      A cleaner design language, possibly using soft rounded “squircle” shapes and subtle glass-like surfaces, could make the interface feel more modern while still remaining simple and professional. Dark and light modes are enough, but both should feel carefully designed and visually balanced.

   5. More personality in the Lumo brand elements
      The Lumo cat or logo could become slightly more interactive or reactive, for example during loading, idle states, or successful actions. This should remain subtle and professional, but it could make the product feel more alive and memorable.

   6. Better personalization inside Lumo
      It would be useful to allow users to upload files or reference material directly inside Lumo for personalization, similar to project-based workflows in other AI tools. This would reduce the need to paste very long texts manually.

   Why this matters:

   A secure AI assistant is valuable, but security alone is not enough for daily adoption. If the product feels too static, too small, or not responsive enough, users are less likely to use it regularly. A smoother and more consistent interface would make Lumo feel more mature, trustworthy, and pleasant to use.

   This request is not about adding unnecessary visual effects. It is about improving usability, consistency, responsiveness, and the overall feeling of quality.

   Thank you for considering this suggestion.

   Dear Proton Community and Development Team,

   I would like to suggest improvements to Lumo’s user interface and overall user experience so that it feels smoother, more consistent, and better suited for daily use.

   Privacy and security are very important, and this is one of the main reasons why many users are interested in Proton products. However, for an AI assistant to become part of everyday work, it also needs to feel fast, polished, intuitive, and enjoyable to use.

   My request is specifically about improving the interaction design and visual consistency of Lumo.

   Suggested improvements:

   1. More responsive UI interactions
      Buttons, menus,… 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

10. Train Lumo to understand the user interface

    Lumo doesn't understand how to communicate through the User Interface very well. It should be trained. Lumo said that the character limit for a single response was about 4000 to 6000 characters. It should know the actual number and be able to feedback to the user that the limit was hit instead of indicating that it will try to better next time (it won't, the UI has a hard limit). When trying to get Lumo to format a list, it is like working with a teenager, it doesn't do what you want and says it will try to better next time. The problem is that it doesn't understand how the user interface interprets things like linefeed vs carriage return. If they Lumo and the UI both used a common format like Rich Text Format, it would cut the conversation requests way down.

    Lumo doesn't understand how to communicate through the User Interface very well. It should be trained. Lumo said that the character limit for a single response was about 4000 to 6000 characters. It should know the actual number and be able to feedback to the user that the limit was hit instead of indicating that it will try to better next time (it won't, the UI has a hard limit). When trying to get Lumo to format a list, it is like working with a teenager, it doesn't do what you want and says it will try to better next… 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

11. Sort chat history by last activity

    Description:
    Lumo’s chat history currently appears to keep conversations sorted by their original creation date instead of their most recent activity.

    This creates a significant usability problem when reusing older conversations. If I open an old chat and continue using it, the conversation does not move back to the top of the history. It stays buried in the same old position, even though it has just become active again.

    This is especially inconvenient for long-running conversations. For example, I may have a chat created weeks or months ago that I still use regularly for the same topic, project, research thread, troubleshooting case, or personal workflow. Even after sending a new message in that chat, it remains far down in the history list.

    Expected behavior:

    When a conversation receives a new message, either from the user or from Lumo, it should move back to the top of the history. The history should be sorted by last activity, not only by the original creation date.

    Current behavior:

    Old conversations seem to remain sorted according to when they were first created. Reusing a conversation does not make it appear as a recent chat.

    Why this matters:

    This makes the history harder to use as the number of chats increases. A conversation that is still active and relevant can remain hidden far down the list simply because it was created a long time ago.

    The current behavior also goes against what users normally expect from chat applications, messaging apps, email threads, and productivity tools. In most interfaces, a recently active conversation is shown near the top, regardless of when it was originally created.

    Practical impact:

    Users may need to scroll through a long history to find conversations they are actively using.

    Important ongoing conversations become harder to resume.

    Users may create duplicate chats just to keep important topics visible, which makes the history more cluttered.

    The “history” view becomes less useful because it does not reflect what has actually been used recently.

    This is particularly annoying for people who use Lumo for ongoing technical work, long-term research, recurring questions, project notes, or conversations that naturally continue over time.

    Suggested improvement:

    Please sort chat history by a “last activity” or “last updated” timestamp.

    A chat should move to the top when:

    The user sends a new message in that conversation.

    Lumo replies in that conversation.

    The conversation is resumed or updated.

    Optional improvement:

    It would also be useful to display the last activity date or time in the history list, so users can clearly understand why a conversation appears where it does.

    Possible sorting options could include:

    Sort by last activity

    Sort by creation date

    Sort alphabetically

    Pinned or favorite chats first

    But the default behavior should probably be sorting by last activity, because that is the standard and expected behavior for a chat history.

    Description:
    Lumo’s chat history currently appears to keep conversations sorted by their original creation date instead of their most recent activity.

    This creates a significant usability problem when reusing older conversations. If I open an old chat and continue using it, the conversation does not move back to the top of the history. It stays buried in the same old position, even though it has just become active again.

    This is especially inconvenient for long-running conversations. For example, I may have a chat created weeks or months ago that I still use regularly for the same topic, project, research thread,… 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

12. Lumo User Interface indicate percentage of output limit when responding

    Lumo has a maximum character limit for a single response (according to Lumo). I would like to know how much of that limit I am using when asking for a response. Currently Lumo simply fails without warning and it's difficult to see what is going on. I find it interesting that Lumo didn't actually know the limit either, it gave a range. When I started asking Lumo more pointed questions it kept stopping partway through the output it responded:

    You are absolutely right to notice that pattern! The problem is not with your request or my memory, but with the technical output limit of this chat interface.
    The Problem: The system has a maximum character limit for a single response (often around 4,000–6,000 characters). Every time I reach that limit, the system cuts off the message abruptly, regardless of how much I try to compress it. It's a "hard stop" imposed by the software, not a choice I make.

    Lumo has a maximum character limit for a single response (according to Lumo). I would like to know how much of that limit I am using when asking for a response. Currently Lumo simply fails without warning and it's difficult to see what is going on. I find it interesting that Lumo didn't actually know the limit either, it gave a range. When I started asking Lumo more pointed questions it kept stopping partway through the output it responded:

    You are absolutely right to notice that pattern! The problem is not with your request or my memory, but with the… 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

13. Fair Monthly Pricing

    Fair Monthly Pricing

    Title: Offer competitively priced monthly-only options for add-ons (Lumo Plus, Meet Professional) without punitive markups

    Body:

    Users with sporadic needs — such as using Lumo Plus for a few intense workdays or Meet Professional for a rare large meeting — are currently penalized by the pricing structure.

    While annual plans offer a discount, they force a 12-month commitment for services that may only be needed for a few days. Monthly plans exist, but they often carry a significant premium compared to the monthly equivalent of the annual rate. This creates a "flexibility tax" that discourages users from paying only for what they actually use.

    I propose that Proton offer fairly priced monthly-only options for add-ons like Lumo Plus and Meet Professional, without a steep markup compared to the annual rate. This would allow users to:

    Subscribe only when needed (e.g., for one month before a big conference).
    Cancel immediately after without financial penalty.
    Align their spending directly with their actual usage patterns.
    

    Removing the "flexibility tax" would signal that Proton trusts its users to pay fairly for value received, rather than relying on long-term lock-ins to maximize revenue.

    Fair Monthly Pricing

    Title: Offer competitively priced monthly-only options for add-ons (Lumo Plus, Meet Professional) without punitive markups

    Body:

    Users with sporadic needs — such as using Lumo Plus for a few intense workdays or Meet Professional for a rare large meeting — are currently penalized by the pricing structure.

    While annual plans offer a discount, they force a 12-month commitment for services that may only be needed for a few days. Monthly plans exist, but they often carry a significant premium compared to the monthly equivalent of the annual rate. This creates a "flexibility tax" that discourages users from… 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

14. Add files or attachments to calendar events

    I see "Add Proton Drive Files as attachments in Proton Calendar events" is a present request - however, it would be great to be able to add attachments regardless of Proton Drive usage.

    For example, I have a ticket to an event in my pm.me email. It would be great if I could just add the ticket to my calendar event and have all info housed in one app - one source of event truth.

    Another use case: adding text documents to meeting events so the agenda is attached to the event and more readily accessed.

    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. Enable Lumo to attach an entire directory from Proton Drive

    Currently you can only attach files to a Lumo conversation. I would like to be able to select a directory from my Proton Drive and Lumo will automatically use all files within that directory including files within subdirectories.

    In my Gemini account I recently noticed you have the ability to do that and think it would be a great feature for Lumo.

    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

16. Creation of subcategories within a project

    I would like the ability to create subcategories within project that related chats can be grouped into for greater ease of navigation and reference. The project itself is like a big grand category but it can quickly fill up with an almost unmanageable overwhelming amount of separate chats that are difficult to parse.

    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. Make lumo fully open source

    I asked the cat if it's open source. It gave all the wrong answers.

    Either make Lumo fully open source very soon, or set a roadmap to achieve that and share it with everyone. Privacy is great, but Proton, without open sourcing everything you do, you are missing the point of what you represent. Do better.

    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. Delete Calendar Events with "Delete" Key

    Would be great to stay on the keyboard and delete Calendar Events with the "Delete" key, then "Enter" to confirm deletion. Less mouse, more keys.

    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 custom or previous chat knowledge to continue into next chat session

    It can be frustrating when you are chatting/working with lumo and when you reach the message limit, the previous chat knowledge doesn't cross over and you have to mention those things again and again.

    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

20. No restrictions for files made by Proton´s own tools

    I can understand some restrictions like upload sizes (although even for unlimited subscribers they are way too small to be useful), but at least have unlimited features for Proton's own tools like Sheets and Docs. That would further incentivize users to use them as well.

    The 10 MB limit is likely an outdated restriction that doesn't reflect Proton's current technology. Since Proton already has a secure storage system (Drive) and collaboration tools (Docs/Sheets), the technical challenge isn't processing files, but integrating them directly into the chat. In a "Unlimited" tier, Lumo could read and analyze files directly from Drive without physical uploads, effectively bypassing the size limit entirely and making the service truly useful.

    I can understand some restrictions like upload sizes (although even for unlimited subscribers they are way too small to be useful), but at least have unlimited features for Proton's own tools like Sheets and Docs. That would further incentivize users to use them as well.

    The 10 MB limit is likely an outdated restriction that doesn't reflect Proton's current technology. Since Proton already has a secure storage system (Drive) and collaboration tools (Docs/Sheets), the technical challenge isn't processing files, but integrating them directly into the chat. In a "Unlimited" tier, Lumo could read and analyze files directly from Drive without… 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