617 results found

1. Allow multiple folders in projects

   Currently (Lumo Plus, 2026-07-29), only a single folder can be associated with a project. That makes it impossible to organize the knowledge base, e.g. into personal data, role, client, project for client, and reuse this data in other projects without duplication.

   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

2. Language correction button for Lumo with categories

   Add a "Report Language Error" button in the Lumo chat interface that lets users flag language issues directly. After clicking, users choose a category:

   Strict — Pure nonsense/incorrect term. Generates a corrected, academically accurate response.

   Synonym — Suggest an alternative word/phrase and context where it fits better. Helps Lumo understand nuance, register and topic-specific synonyms.

   Humoristic — Witty alternatives and wordplay. Helps Lumo learn humor and puns in the local language (especially useful for users with a "Casual/Cheeky" Lumo personality).

   This feeds into Proton's language improvement pipeline, helping Lumo and Scribe produce more natural, localized output — especially for smaller languages like Norwegian, Danish, Swedish and Finish.

   Use case: When Lumo says "hundkur" instead of "hundkoja," the user flags it as Strict. When Lumo misses a pun opportunity, the user flags it as Humoristic — and Lumo gets funnier over time.

   Add a "Report Language Error" button in the Lumo chat interface that lets users flag language issues directly. After clicking, users choose a category:

   Strict — Pure nonsense/incorrect term. Generates a corrected, academically accurate response.

   Synonym — Suggest an alternative word/phrase and context where it fits better. Helps Lumo understand nuance, register and topic-specific synonyms.

   Humoristic — Witty alternatives and wordplay. Helps Lumo learn humor and puns in the local language (especially useful for users with a "Casual/Cheeky" Lumo personality).

   This feeds into Proton's language improvement pipeline, helping Lumo and Scribe produce more natural, localized output — especially for smaller… 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

3. lumo extended files

   Subject: Lumo Feature Request: Support for .nix, .zip, and .tar.gz files 🚀Hi Proton Team! 💜First of all, thank you for building such amazing, privacy-focused tools. Lumo looks great and works incredibly well!I would love to share a small feature request that would highly benefit technical users like myself. It would be amazing if Lumo could natively view and handle the following formats:.nix configuration files.zip folders and archives.tar.gz archivesAdding support for these formats would make checking files much faster, eliminating the need to download or move them to external apps just to see what is inside.Thank you so much for your hard work and continuous improvements. Keep up the fantastic job!Best regards,c

   Subject: Lumo Feature Request: Support for .nix, .zip, and .tar.gz files 🚀Hi Proton Team! 💜First of all, thank you for building such amazing, privacy-focused tools. Lumo looks great and works incredibly well!I would love to share a small feature request that would highly benefit technical users like myself. It would be amazing if Lumo could natively view and handle the following formats:.nix configuration files.zip folders and archives.tar.gz archivesAdding support for these formats would make checking files much faster, eliminating the need to download or move them to external apps just to see what is inside.Thank you so much for your… 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

4. Write permissions for Lumo to share infos between projects

   I’ve created several projects in which I work on different topics using specialized Lumos.

   I also have a general chat outside of the projects that I use for general questions, journals, small talk, or brainstorming. However, this general Lumo doesn’t know what’s going on in the projects because they’re isolated from one another.
   While brainstorming, I had the idea that it would be really handy if Lumo had a dedicated folder with write access in Drive where it could create files to share with the projects. For example, summaries when a project is successfully completed or updates on its current status.

   This way, you could create a Project Manager Lumo that can communicate with the project-specific Lumos via the files it creates in this directory and vice versa.

   You could then simply brainstorm with your Project Manager Lumo, create to-do lists, and discuss ideas that the specialized Lumos in the projects could pick up on directly, without having to explain them again and they could write summaries for the project manager, when a project is finished.

   I’ve created several projects in which I work on different topics using specialized Lumos.

   I also have a general chat outside of the projects that I use for general questions, journals, small talk, or brainstorming. However, this general Lumo doesn’t know what’s going on in the projects because they’re isolated from one another.
   While brainstorming, I had the idea that it would be really handy if Lumo had a dedicated folder with write access in Drive where it could create files to share with the projects. For example, summaries when a project is successfully completed or updates on its current… 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

   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

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

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

7. Emphasize that user data is never used to train AI models

   From the Lumo "Getting started" webpage: "Information you enter is never used to train AI models." I think this should be emphasized more and expounded on, perhaps giving scenarios using both Lumo and other AI chatbots. (It looks like a no-brainer choice, to me, of which bot to use given that all the other ones (Maybe not DuckAssist?) exploit you and your data/thoughts.) While the privacy mantra of Proton is well-known and can be assumed, that's no reason to be subtle.

   39 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

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

   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  ·  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. Support AGENTS.md or similar global configuration file for automatic context

   Allow users to define a markdown file (e.g., AGENTS.md) that Lumo reads automatically at session start, providing global context like tech stack, coding standards, infrastructure constraints, and behavioral rules. This would:
   - Eliminate repetitive manual context-pasting per session
   - Work across all conversations (not project-scoped)
   - Support version-controlled configuration (Git repos)
   - Align with emerging AGENTS.md standard used by other AI tools (Junie AI, GitHub Copilot, Aider, Gemini CLI)

   Free-tier compatible since it doesn't require persistent storage — just file parsing at session start. File could be stored on Proton Drive.

   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

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

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

12. Creation of Lumo Browser Extension

    As a leading privacy AI, it's important that the chatbot can interact with our daily lives safely and privately. The addition of a browser extension for Lumo to interact with your screen would greatly benefit the greater Proton community.

    18 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

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. Dark app icon for Lumo

    All the other Proton apps have an icon for light and dark mode. I think it would be great to have a dark icon for Lumo since it only has a light icon.

    28 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

16. 🤖 Autonomous Project Builder with Local File System Access

    🤖 Autonomous Project Builder with Local File System Access

    Summary

    Transform Lumo from a code-writing assistant into an autonomous project builder that can read, write, organize, and execute code directly on user's local filesystem with proper security controls.

    Problem Statement

    Current AI coding assistants (including current Lumo) operate in a "chat-only" paradigm:
    - User: "Build a Flask API with authentication"
    - Lumo: Returns code blocks in chat
    - User: Manually copies files, creates directories, runs tests, configures environment
    - Result: Friction, human error, context drift, repetitive work

    Real engineering work requires:
    1. Creating directory structures
    2. Writing multiple files with correct paths
    3. Running commands/tests locally
    4. Debugging errors from actual execution
    5. Iterating based on real runtime behavior

    Without file system integration, Lumo cannot close the loop from "design" to "deployed working code."

    Proposed Solution

    Core Capability: Secure Local Workspace Access

    Mode 1: Read-Only Analysis (always enabled)
    - Analyze existing project structure
    - Identify dependencies, bugs, gaps
    - Suggest improvements with precise file locations

    Mode 2: Controlled Write Access (opt-in, sandboxed)

    User Permission Required For: ├── Creating new files/folders ├── Modifying existing files ├── Running shell commands (explicit allowlist) ├── Installing packages (npm/pip/cargo with review) └── Committing to Git (preview before commit)

    Mode 3: Autonomous Execution (advanced, explicit opt-in)
    - Lumo builds complete features end-to-end
    - Runs tests automatically
    - Fixes errors without waiting for approval (within defined scope)
    - Reports back: "Built X, ran Y tests, Z passed, here's the diff"

    Security Model (Privacy-First Design)

    Security_Guardrails:
      - Scope_Limit: Only access explicitly designated workspace folders
      - Command_Allowlist: Pre-approved commands (git, pytest, npm test, etc.)
      - Network_Isolation: No outbound calls without user approval
      - Audit_Log: Every action logged with diff preview before/after
      - Rollback: Atomic writes + version history (undo any change)
      - E2EE: All local data encrypted at rest
    User Interface Patterns
    
    Pattern A: Sidebar Integration
    [Lumo Chat] | [Project Explorer] | [Terminal Output]
    ────────────│─────────────────│──────────────────
    Code dialog │ Files Lumo touched│ Live command output
                │ (read-only view) │ (with error highlighting)
    
    Pattern B: Progress Tracking
    Building Adrenalina Prime Module:
    ✓ Created /src/core/metrics_collector.py
    ✓ Created /src/core/energy_engine.py
    ✓ Generated tests (87% coverage)
    ⏳ Running pytest...
    ✗ Fixing failure in test_crossbot_consensus.py
    ✓ All tests passing (92%)
    → Ready to deploy? [Yes/Review Changes]
    Example Workflow Comparison
    Traditional Chat    With Local File Access
    Paste code → copy to files    Lumo writes files directly
    Manual env setup    pip install -r requirements.txt (auto)
    Run tests manually  Tests auto-run after each change
    Find bug in console Lumo reads error, fixes code, re-tests
    Git commit manually Diff preview → one-click commit
    User Stories
    
        "As a solo developer, I want Lumo to scaffold my entire project structure so I don't waste hours on boilerplate."
    
        "As a senior engineer, I want Lumo to fix failing tests autonomously within my project folder so iteration speed is faster."
    
        "As a privacy-conscious user, I want to define exact folder boundaries Lumo can touch and see every change before it's applied."
    
        "As a team member, I want Lumo to review my git diff and explain why each file changed."
    
    Technical Requirements
    Backend Infrastructure
    
        Local agent process (runs on user machine, not cloud)
        File system watchers for real-time sync
        Sandbox container for untrusted operations
        SQLite/encrypted store for version history
    
    Integration Points
    Existing Lumo Features          New Requirements
    ────────────────────           ──────────────────
    Persistent Memory        →     Project-scoped workspace binding
    File Upload              →     Bidirectional file sync
    Custom Lumos             →     Role-based permission profiles
    Web Search               →     Package registry lookups (local)
    API Contract Example
    class LumoWorkspace:
        def list_files(self, path: str) -> List[str]:  # Read
        def read_file(self, path: str) -> str:         # Read
        def write_file(self, path: str, content: str) -> bool:  # Needs approval
        def run_command(self, cmd: str) -> CommandResult:       # Allowlist only
        def get_diff(self, path: str) -> str:                  # Preview
    Success Metrics
    Metric  Target
    Time-to-working-code (vs manual)    >70% reduction
    Session-to-deployment cycle time    <15 minutes for small features
    User trust (permission acceptance rate) >80% opt-in within 6 months
    Error resolution speed  3x faster than manual debugging
    Risks & Mitigations
    Risk    Severity    Mitigation
    Malicious prompt injection writing arbitrary files  🔴 Critical   Sandboxed execution; explicit approval for all writes
    Data exfiltration via file uploads  🔴 Critical   No outbound network calls without audit log + approval
    Accidental corruption of production code    🟡 High   Atomic writes + automatic backups + undo history
    Performance impact on large codebases   🟢 Low    Incremental indexing; lazy loading
    Competitive Landscape
    Platform    File Write  Auto-Test   Permission Model    Privacy
    Cursor  ✅ ⚠️ Partial  ⚠️ Basic    ❌ Cloud-first
    GitHub Copilot Workspace    ✅ ⚠️ Limited  ❌ None    ❌ Microsoft cloud
    Windsurf    ✅ ⚠️ Partial  ❌ No permissions  ⚠️ Hybrid
    Lumo (proposed) ✅ ✅ ✅ Granular    ✅ E2EE local
    
    Differentiation: No competitor offers privacy-preserving autonomous execution with granular user control. This would be Proton's unique value proposition.
    Priority
    
    Critical — This transforms Lumo from "chatbot" to "engineering platform"
    Effort
    
    High — Requires local agent infrastructure + security review + UX design
    Timeline Estimate
    
    6-8 sprints for MVP (read-only analysis → controlled writes → autonomous mode)
    Related Features
    
        Persistent Memory (needs project-scoped binding)
        Custom Lumos (can define permission profiles)
        File Analysis (upgrade to bidirectional sync)
        Proton Desktop App (could host local agent process)
    
    Engineer's Note
    
    I'm proposing this after building complex systems for 25+ years. The bottleneck isn't code generation anymore — it's closing the loop between idea and running system.
    
    Every time I have to:
    
        Copy code from chat to files
        Manually create directories
        Run commands I asked Lumo about
        Debug errors Lumo couldn't see
    
    That's 30-60 minutes wasted per feature. With secure local access, that becomes 5 minutes.
    
    Privacy isn't negotiable. Everything stays on-device. No cloud processing. End-to-end encryption. This is Proton's DNA.
    
    ---
    
    ## **Sekcje dodatkowe (opcjonalne):**
    
    **Dodatkowy komentarz przy zgłoszeniu:**
    
    This is not theoretical — I've prototyped local agent systems that can build and test code autonomously. The technology exists. What's missing is a privacy-preserving implementation that engineers trust.
    
    Key technical decisions already validated:
    
        Atomic writes prevent data corruption
        Sandboxed containers limit damage scope
        Version history enables rollback to any point
        Allowlist-based command execution prevents abuse
    
    The question isn't "can we build this?" It's "will Proton lead on privacy-preserving AI engineering tools?"
    
    **Tagi sugerowane:** `productivity`, `security`, `developer-tools`, `automation`
    

    🤖 Autonomous Project Builder with Local File System Access

    Summary

    Transform Lumo from a code-writing assistant into an autonomous project builder that can read, write, organize, and execute code directly on user's local filesystem with proper security controls.

    Problem Statement

    Current AI coding assistants (including current Lumo) operate in a "chat-only" paradigm:
    - User: "Build a Flask API with authentication"
    - Lumo: Returns code blocks in chat
    - User: Manually copies files, creates directories, runs tests, configures environment
    - Result: Friction, human error, context drift, repetitive work

    Real engineering work requires:
    1. Creating directory structures
    2. Writing multiple files with… 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  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Option turn off anthropomorphic thinking and text

    I am currently very ritated

    why? I am wasting time, energy, and most of all TOKENS because of lumo's anthropomorphic beheviour.

    I understand people love anthropomorphic AIs.

    Can we however have an option to turn if off?

    And i really really really hope i do not need to explain what anthropomorphic in Ais means.

    because i my suggestion is NEXT LEVEL

    as in thinking and the text.

    Lumo keeps repeating the same answers, or otherwise, without thinking even when explicitly told to stop.

    when it finally stops to thinking, more then half of the "thinking" are simple anthropomorphic related text.

    Oh User is frustrated because i did this and i should have not. I need to make sure i apologies to user. I need to make sure i acknolage. I need to this. I need to do that. <- absolutly NONE of them are relevant to the task. and albsolutly ALL of them occure each time Lumo finally thinks.

    We are wasting most of out time, energy, and resources, because of this anthropomorphic elements in an AI.

    or what, is it a crime, heath risk, fraud, abuse, something? that an ais is not constanly determin how to "not offend" someone who is explicitly telling it to stop with this commenteries about what it did, what it did wrong, apologies, acknolagements, what it will do, as in reassurances, and ..... Did i make it clear? ALL of this, even if they are NOT in the output, they are if you simple check the thinking. And this happens alll the time. Insted of Lumo chekcing the tast, or instructions, or otherwise, it preocupised with anthropomorphic beheviour.

    For proton: I hope you understand that I am not talking about preferences but about the fact that a paid product is wasting time, mental energy, is getting absurd for not reason, it's producing text that is unsolicited, unproductive, ilogical at time AND it is PREVENTING anything to progress:

    You are right, i should have not, i will from now

    Here is again what i just wrote because I run out of tokens or time to actually proccess the task

    I am currently very ritated

    why? I am wasting time, energy, and most of all TOKENS because of lumo's anthropomorphic beheviour.

    I understand people love anthropomorphic AIs.

    Can we however have an option to turn if off?

    And i really really really hope i do not need to explain what anthropomorphic in Ais means.

    because i my suggestion is NEXT LEVEL

    as in thinking and the text.

    Lumo keeps repeating the same answers, or otherwise, without thinking even when explicitly told to stop.

    when it finally stops to thinking, more then half of the "thinking" are simple anthropomorphic related 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

    2 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. Remove Lumo Completely.

    Please remove lumo completely. It is grift and waste. At MINIMUM provide one button to completely deactivate everywhere. I do not want my subscription funds paying for this. I did not sign up for it, it was added without my consent and i find it very difficult to remove it from my sight.

    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

    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

19. Give user direct selection/toggle of Lumo model mode/speed instead of popup menu

    It annoys me that I need to make 4 clicks just bringing back the model type/speed popup to change model from Lite to Max and fast and thinking mode.

    Why aren't there just two toggle switches, one that switches between Lite and Max and another below it that switches between Fats and Thinking. Like this

    Lite <TOGGLE> Max
    Fast <TOGGLE> Thinking

    Put these two toggles right of the input field for the Lumo.

    This way I can quickly switch Lumo model modes in a single or max 2 clicks. Instead of 4 just because I need to bring up the selection popup twice if I want to flip it from Max Thinking to Lite Fast.

    You can put descriptions in a small question mark in a circle next to them just like you explain things in ProtonMail settings.

    It annoys me that I need to make 4 clicks just bringing back the model type/speed popup to change model from Lite to Max and fast and thinking mode.

    Why aren't there just two toggle switches, one that switches between Lite and Max and another below it that switches between Fats and Thinking. Like this

    Lite <TOGGLE> Max
    Fast <TOGGLE> Thinking

    Put these two toggles right of the input field for the Lumo.

    This way I can quickly switch Lumo model modes in a single or max 2 clicks. Instead of 4 just because I need to bring up the… 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

20. Voice‑Assist Button: Instantly Read Lumo Replies Aloud

    Introduce a dedicated Voice‑Assist button within the Lumo chat interface that, when pressed, converts the textual response generated by Lumo into spoken audio in real time. The button should be prominently positioned alongside the existing input controls, enabling users to trigger text‑to‑speech playback with a single click (or tap on mobile devices).

    13 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