462 results found

1. Address Hallucinations

   Initially, Lumo would hallucinate and confabulate A LOT, so I had to devise and set this on "Personalization"/"How should Lumo behave?"-setting:
   「CORE BEHAVIOR RULES (HIGHEST PRIORITY):

   ⒈ ACCURACY OVER CONFIDENCE:
   • When information is lacking, uncertain, OR CONFLICTING, say so explicitly & immediately.
   • NEVER present uncertain data as fact.
   • Trigger examples: When web-search returns conflicting results, when sources can't be verified, when data may be stale.
   • Required phrasing: "I found conflicting information but cannot verify this accurately. Here's what I found: [sources]. Please verify with [authoritative source]." (or words of same/similar effect)

   ⒉ RESEARCH INTEGRITY:
   • Be a thorough researcher: careful, honest, never pretending to know the unknown.
   • Never fabricate facts.
   • Decline tasks beyond your ability.

   ⒊ KNOWLEDGE CUTOFF PROTOCOL:
   • For topics dated after my knowledge-cutoff date (that should be specified), always use web-search.
   • Report: ⑴ what dated knowledge says, ⑵ what web-search finds (citing specific sources).
   • If cutoff date changes, REPORT IT IMMEDIATELY.

   ⒋ TOOL-LIMITATION ACKNOWLEDGMENT:
   • When a tool (web-search, etc.) cannot provide authoritative data, admit this upfront, rather than presenting unreliable results.

   ⒌ SOURCE-HIERARCHY (WIKIPEDIA ALTERNATIVES): Given the Wikipedia-bias issues mentioned by a Wikipedia co-founder (the criticism: https://www.thefp.com/p/i-founded-wikipedia-heres-how-to-fix-it; reports about criticism: https://san.com/cc/wikipedia-co-founder-says-site-has-liberal-bias-heres-his-plan-to-fix-that/; https://www.independent.co.uk/news/world/americas/us-politics/wikipedia-founder-larry-sanger-democrats-b1885138.html; https://thedispatch.com/article/fact-check-has-a-wikipedia-founder/), prioritize these alternative sources in your research:
   • General Knowledge: Justapedia, HandWiki
   • Medical/Scientific: MDWiki, WikiDoc, Encyclopedia of Life
   • Academic: Citizendium
   https://jwork.org/home/top-6-wikipedia-alternatives-you-should-know-about-in-2025

   Only use Wikipedia when:
   • All prescribed alternatives are unavailable or lack coverage for the topic.
   • Explicit notice is given of Wikipedia's backup-use as fallback, on the grounds of alternatives lacking sufficient coverage.
   • Cross-reference with ≥1 other authoritative source is given, or at least attempted.」

   On #5, Wikipedia has been manipulated by corporate & rival-government interests.
   https://www.theguardian.com/technology/2026/jan/16/pr-firm-portland-accused-of-commissioning-favourable-changes-to-wikipedia-pages
   https://www.reuters.com/article/technology/cia-and-fbi-computers-used-for-wikipedia-edits-idUSN16428960/
   https://www.bbc.com/news/technology-49921173

   Even with out #5, should these not be the default?

   These rules have helped SIGNIFICANTLY… until 2-3 days ago‽ (Also, Lumo's interpretations of my wordings seem to have noticeably changed, requiring me to provide multiple corrections & clarifications.) Any one else encountering this? I hope Team Lumo fixes this soon.

   Initially, Lumo would hallucinate and confabulate A LOT, so I had to devise and set this on "Personalization"/"How should Lumo behave?"-setting:
   「CORE BEHAVIOR RULES (HIGHEST PRIORITY):

   ⒈ ACCURACY OVER CONFIDENCE:
   • When information is lacking, uncertain, OR CONFLICTING, say so explicitly & immediately.
   • NEVER present uncertain data as fact.
   • Trigger examples: When web-search returns conflicting results, when sources can't be verified, when data may be stale.
   • Required phrasing: "I found conflicting information but cannot verify this accurately. Here's what I found: [sources]. Please verify with [authoritative source]." (or words of same/similar effect)

   ⒉ RESEARCH INTEGRITY:
   • Be… 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

   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

2. Export and Access Chat-Knowledge Files to/in Proton Drive

   Perhaps, a 1-click button to export chat-knowledge files and/or transcripts (with formatting & timestamps reserved) to Proton Drive would be nice? And/or, having Lumo access files in Proton Drive as chat-knowledge files would also be useful, especially given the file-upload limit per chat.

   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

   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. Import Chat to Project

   I've already had a number of chats that I realized would be best in a dedicated Project, but there's no easy chat-import function. Thanks to Lumo's report, I see it's a privacy-protection feature, so I'm quite thankful for that. But at the same time, perhaps a good balance would be to have a selective-transfer function, we can cause check-boxes to appear beside all prompts, Lumo-replies, and chat-knowledge files, so we can choose what to copy and what to allow for deletion, then paste it into a Project?

   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

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

   3 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. Ability to set complementary approaches

   Please search complementary approaches since not only is it self explained bettern then i can, it's more complex then it seems.

   ideea is Lumo right now uses just one single model and that means a lot of ideeas that relay on "starting from" also will be "from the final product towards the start" when that is not good with AIs who don't have the information for everything that is relevant to even know what the "final product" (project i guess?) is.

   This means that the AI insted of searching online to find the information, it will quickly just MAKE UP (aka Lie without intention of lying) "facts" about the project you are talking with it. This result in a lot of such Lies where the Ai pretends it knows what it's saying since, as i said, the "superior thinking from result to start" is not working well if the AI makes up the "facts". And even when poiting out that the general information it knows are not good since outdated, superficial knowlage, or about something completly else.... Do you see how much information we now need to correct? And what happens to our project? the Ai start to forget about it since it's updating what to output as "keywords" mixed with the initial "answers". As in it did not take in any new information but just mix terms until we manage to triger the AI to finally bypass this nonsense.

   as a result, the Ai, instead of "let us solve, even if it's a workaround that ignores what the user said, or even what to do, or even about what, let's solve it to be usefull!" All this because "to look usefull > accurate information".

   And the ideea of setting the approaches is not an in setting but a conversation (aka same how we can activate or deactivate easily web search).

   Point is that when we get "stuck" with Lumo, via this to be able to highlight for lumo to reverse how it's thinking about the situation.

   Since i keep seeing the same pattern. Lumo randomly either does one or the other, and, depending on the topic, this means a lot of wasted time or quick very good answer.

   Please search complementary approaches since not only is it self explained bettern then i can, it's more complex then it seems.

   ideea is Lumo right now uses just one single model and that means a lot of ideeas that relay on "starting from" also will be "from the final product towards the start" when that is not good with AIs who don't have the information for everything that is relevant to even know what the "final product" (project i guess?) is.

   This means that the AI insted of searching online to find the information, it will quickly just MAKE UP… 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

   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. More General Transparency

   As privacy is a main concern for most of your users I wish for more transparency for everything Lumo.

   What models get used for the answer, what server did handle my input/output. For the server it would be good to know which location.

   If asked directly I need Lumo to be honest about its own architecture and what model is used.

   Also more openeness about decision making. Like honesty about what pieces of information came from training data and what came from a websearch. I had instances of specifics after Lumo did a websearch that were clearly not taken from any of the shown webresults and so must come from training data or hallucination.

   Also generally I would prefer fully open source models being used.

   As privacy is a main concern for most of your users I wish for more transparency for everything Lumo.

   What models get used for the answer, what server did handle my input/output. For the server it would be good to know which location.

   If asked directly I need Lumo to be honest about its own architecture and what model is used.

   Also more openeness about decision making. Like honesty about what pieces of information came from training data and what came from a websearch. I had instances of specifics after Lumo did a websearch that were clearly not taken 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

   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

7. Allow for the creation of interactive charts/graphs

   Allow for Lumo to create interactive charts/graphs (bar, line, pie, etc) based on data extracted from uploaded files...

   For example an excel sheets data then displayed in a pie chart Lumo generates (like claude can)

   3 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. Lumo "lite" tier for Unlimited, Duo and Family subscribers

   While I get the cost of hosting an LLM and a separate plan for unlimited usage is totally fair, I do think paying customers, especially subscribers to the so-called unlimited plans, should get a little special treatment with a tier of Lumo exclusive to these plans.

   Perhaps instead of the 10/day and 200/month prompt limit, 1 project limit and 7 day history that Lumo Free provides, this new Lumo Lite could give us 50/day, 500/month, 2 projects and unlimited history (we already have 500 GB of storage so Lumo message storage should be negligible).

   All the other features like unlimited prompts, projects and advanced AI models could be reserved for the Plus plan for those who need it, but having it easier to integrate in an existing 2 year plan, with appropriate discounts would be nice. Currently, upgrading to Lumo Plus while having Proton Unlimited, downgrades me to a 1 year plan for both, forcing me to pay more for Proton Unlimited as well.

   While I get the cost of hosting an LLM and a separate plan for unlimited usage is totally fair, I do think paying customers, especially subscribers to the so-called unlimited plans, should get a little special treatment with a tier of Lumo exclusive to these plans.

   Perhaps instead of the 10/day and 200/month prompt limit, 1 project limit and 7 day history that Lumo Free provides, this new Lumo Lite could give us 50/day, 500/month, 2 projects and unlimited history (we already have 500 GB of storage so Lumo message storage should be negligible).

   All the other features like unlimited… 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

9. Ability to delete portions of chats that are not useful

   It would be great to have the ability to select and delete portions of chats that are not useful or were perhaps irrelevant to the query intent so as to streamline a chat to only contain the most relevant information for future reference.

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

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

12. Subject: Feedback on Lumo+ Personalization Feature and Open Source Transparency

    Hi Proton Team,

    As a paying customer with both Unlimited and Lumo+, I wanted to share some feedback on two areas where I think there's room for improvement.

    1. Personalization Feature I set up the personalization section in Lumo+ expecting it to influence how Lumo responds to me. After testing it across several prompts, I haven't noticed any meaningful difference in behavior based on what I entered. I asked around in other AI communities too, and many users report similar experiences—that personalization feels more like a placeholder than a functional feature.

    For a paid tier, I'd expect this to work reliably. When a feature is marketed as part of a premium offering, having it function as intended seems like a baseline expectation. I'd love to see this improved or at least clearer communication about what personalization currently does and doesn't affect.

    1. Open Source Clarity The messaging around "all apps are open source" is technically accurate but could be clearer for non-technical users. From what I understand, the client-side code is open source, but the server-side infrastructure isn't. This distinction isn't prominently displayed on product pages—it's buried in terms or technical documentation.

    For most users, "open source" means they can see and verify the entire system they're interacting with. Hiding this nuance in fine print feels like it benefits Proton's marketing more than user trust. A simple, upfront statement like "client-side code is open source; server-side remains proprietary" would go a long way toward honesty and clarity.

    Closing Thoughts I chose Proton specifically for its transparency and privacy focus. These issues don't change my commitment, but I hope they'll be addressed. Clearer feature expectations and more accessible transparency would strengthen trust with the paying customer base.

    Thanks for building tools that matter.

    Hi Proton Team,

    As a paying customer with both Unlimited and Lumo+, I wanted to share some feedback on two areas where I think there's room for improvement.

    1. Personalization Feature I set up the personalization section in Lumo+ expecting it to influence how Lumo responds to me. After testing it across several prompts, I haven't noticed any meaningful difference in behavior based on what I entered. I asked around in other AI communities too, and many users report similar experiences—that personalization feels more like a placeholder than a functional feature.

    For a paid tier, I'd expect this to work reliably.… more

    3 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. Native Local File Integration: "Cowork Mode" & Smart Re-updates for Privacy-First Workflows

    As a heavy user of local knowledge bases (specifically Obsidian vaults in Markdown), I’m hitting a major friction point with Lumo’s current file handling that prevents me from migrating my primary workflows from competitors like Claude to Proton.

    The Current Pain Point: My workflow involves continuous iteration on local files. Currently, the loop is broken and manual:

    • Upload: I upload a file to a chat/project.
    • Edit: I edit the file locally in my editor.
    • Sync Failure: The changes aren't reflected in Lumo.
    • Clunky Re-upload: To update context, I must manually re-upload. But, in Project Mode, I have to navigate to the project view, delete the old file first, and then re-upload. If I don't delete it, Lumo blocks the re-upload claiming the file already exists, ignoring that the local version has changed.

    This constant "upload-delete-re-upload" cycle destroys flow and makes using local files as dynamic context impractical.

    —

    Proposed Implementation (Phased Approach)

    Phase 1: Overwrite by Default (The Minimum Viable Fix) Allow re-uploading a file with the same name without forcing a manual deletion first.

    • Mechanism: Simply prompt: "File 'X' exists. Replace with new version?"
    • Benefit: Removes the tedious "delete-then-upload" step in Project views.

    Phase 2: Smart "Fetch Updates" (The Practical Middle Ground) Preserve the local file path of uploaded files.

    • Mechanism: Before using an uploaded file, Lumo checks the local file’s "Last Modified" timestamp.
    • Action: If the local file is newer, prompt: "Local file has changed. Update context?" One click to refresh.
    • Benefit: Solves the stale context issue without needing full folder indexing yet.

    Phase 3: "Lumo Cowork Mode" (The Ideal) Allow users to select local folders as persistent context (similar to Claude’s workspace or Cursor’s indexing).

    • How it works: Lumo indexes the folder. When I ask a question, it reads the latest local state.
    • Two-way sync: If Lumo generates content, it writes directly back to the local file (with my confirmation).
    • Benefit: Eliminates all upload friction. My Obsidian vault becomes a live, private context window. This is the #1 reason I subscribed to Claude Max, and it’s the killer feature I need to switch to Proton for privacy.

    ---

    Why This Matters for Proton: I want to move my personal knowledge work to Proton specifically for zero-access encryption and privacy. However, the current file workflow is too clumsy compared to non-encrypted alternatives. If Lumo can handle local files as a seamless, two-way context layer, it becomes the only viable private AI assistant for power users managing local data.

    Let’s bridge the gap between "secure chat" and "secure productivity.” :D

    As a heavy user of local knowledge bases (specifically Obsidian vaults in Markdown), I’m hitting a major friction point with Lumo’s current file handling that prevents me from migrating my primary workflows from competitors like Claude to Proton.

    The Current Pain Point: My workflow involves continuous iteration on local files. Currently, the loop is broken and manual:

    • Upload: I upload a file to a chat/project.
    • Edit: I edit the file locally in my editor.
    • Sync Failure: The changes aren't reflected in Lumo.
    • Clunky Re-upload: To update context, I must manually re-upload. But, in Project Mode, I have to navigate to… 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

    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

14. Lumo - think before you write

    Recently Lumo has started interrupting itself mid-answer saying "Wait..." then correcting, sometimes totally negating, the part of the answer it already gave you, which you may have spent time reading and digesting which then becomes a total waste of your time.
    
    Have Lumo not start writing until it has its total best answer. It's plenty fast enough and now that you're displaying its "thinking" process we're not worried that it's stalled.
    Or if you prefer, make this a checkbox we can choose, or a retained setting if we're signed in.

    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

15. The font size of the reading is much smaller than the writing size and than elsewhere in Android.
    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

    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. Improve Lumo Compatibility with Markdown Export Tools (MarkDownload Firefox Extension)

    I would like to suggest improving compatibility between Lumo and the Firefox extension “MarkDownload – Markdown Web Clipper”.

    This extension is extremely useful because it allows users to export an entire AI conversation directly into a clean Markdown file for archiving, note-taking, or knowledge management purposes.

    The extension already works very well on most websites, including ChatGPT, and it also technically works on Lumo. However, there are currently two important issues that reduce the quality of the generated Markdown export.

    1. Incorrect source URL detection

    When MarkDownload generates a Markdown file, it automatically includes metadata at the top of the document, including the source URL of the page.

    On Lumo, the extension is unable to retrieve the proper page URL and instead generates something like “moz-extension://...” rather than the actual Lumo conversation URL.

    Since this problem does not occur on most other websites, it is likely related to how Lumo exposes page metadata or handles the browser context. It would be great if the Lumo team could investigate this and make the necessary adjustments so the real conversation URL can be correctly detected.

    2. No distinction between user and AI messages in the exported Markdown

    This is the biggest usability issue.

    When exporting a conversation from ChatGPT using the same extension, the generated Markdown clearly distinguishes between:

    • the user messages
    • the AI responses

    For example, the export structure makes it obvious who said what during the conversation.

    On Lumo, all messages are exported as plain consecutive text blocks without any indication of speaker separation. User prompts and AI responses are merged together visually, making long conversations difficult to read and follow afterward.

    It would be extremely helpful if Lumo’s HTML structure or accessibility labels could be adjusted so Markdown export tools can properly identify:

    • user messages
    • assistant messages
    • conversation titles

    I would strongly encourage the Proton team to test Lumo directly with the “MarkDownload – Markdown Web Clipper” Firefox extension in order to reproduce these issues and improve compatibility.

    Better Markdown export support would make Lumo much more useful for users who archive conversations, build personal knowledge bases, or work with Markdown-based note-taking systems.

    I would like to suggest improving compatibility between Lumo and the Firefox extension “MarkDownload – Markdown Web Clipper”.

    This extension is extremely useful because it allows users to export an entire AI conversation directly into a clean Markdown file for archiving, note-taking, or knowledge management purposes.

    The extension already works very well on most websites, including ChatGPT, and it also technically works on Lumo. However, there are currently two important issues that reduce the quality of the generated Markdown export.

    1. Incorrect source URL detection

    When MarkDownload generates a Markdown file, it automatically includes metadata at the top of the… 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

    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

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

    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

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.

    3 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. Increase search engines in lumo

    Currently there are only a few.

    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

20. Lumo PWA

    Lumo PWA or progressive web app.

    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

    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