580 results found

1. I love using Lumo. But have difficulty with the small gray scrollbar. Please make that in a contrast colour or much much bigger.

   I love using Lumo. But having difficulty with the small gray scrollbar. Please make that in a contrast colour or much much bigger. I do not want to squint every time I have to scroll up and down. Recently I asked Lumo and he suggested settings. So by trying myself, I realized something and succeeded in making the background white. That helped a bit. But the bar is still very small. Can you please fix this.

   1 vote

   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  ·  Edit…  ·  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. Proposal: Include Lumo Plus for free with Proton Unlimited subscriptions or 50% discount

   Dear Proton Team,

   First of all, thank you for building such a strong privacy-first ecosystem. As a paying Proton Unlimited subscriber, I genuinely value the work you do, and my subscription feels like an investment in a company whose mission I believe in.

   With that in mind, I would like to propose a change to the Unlimited plan that I believe would strengthen loyalty among your paying customers and differentiate the bundle even further:

   Proposal: Include Lumo Plus at no extra cost for Proton Unlimited subscribers or give 50% discount for paid users. And, not for yearly payments, but also for monthly pay.

   The reasoning:

   Rewarding loyalty. Paying Unlimited members are the backbone of Proton's sustainability. Unlike free users, we directly fund the infrastructure, development, and innovation that keep Proton running. Extending Lumo Plus to us would feel like a meaningful acknowledgment of that contribution.
   Stronger bundle value. Unlimited already bundles Mail, VPN, Drive, and Pass. Adding Lumo Plus would make the bundle even more competitive against Big Tech ecosystems (Google One, Microsoft 365, Apple One) that increasingly bundle AI features at no extra charge.
   Alignment with Proton's mission. Lumo is promoted as a privacy-first AI assistant. Making it a core part of the paid privacy ecosystem would reinforce the message that privacy tools belong everywhere — including AI — not just in email and VPN.
   Likely minimal revenue impact. Many Unlimited subscribers currently use Lumo Free. The users who would benefit most from this change are existing loyal customers, not heavy AI power users who would already be paying for Lumo Plus. In practice, this mostly transfers value back to the people funding Proton.

   Kind regards,

   a 5 years Proton Unlimited user

   Dear Proton Team,

   First of all, thank you for building such a strong privacy-first ecosystem. As a paying Proton Unlimited subscriber, I genuinely value the work you do, and my subscription feels like an investment in a company whose mission I believe in.

   With that in mind, I would like to propose a change to the Unlimited plan that I believe would strengthen loyalty among your paying customers and differentiate the bundle even further:

   Proposal: Include Lumo Plus at no extra cost for Proton Unlimited subscribers or give 50% discount for paid users. And, not for yearly payments, but also… more

   1 vote

   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  ·  Edit…  ·  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 Diary: Reflective Daily Journaling with Photos & Conversation History

   I'd like to propose a built-in Diary Mode for Lumo – a private, encrypted daily journal that grows naturally out of normal conversation.

   The Concept: Instead of filling out a journaling form, the user simply talks to Lumo during the day about what they did, thought, or experienced, and can attach photos. When the day ends (or the next day is opened), Lumo compiles the conversation and images into a structured diary entry.

   Key features:

   • Conversation-to-entry with timestamps: The day's chats become the raw material. Each new day gets a "page" in the diary. Each conversation segment is automatically marked with the time it took place (or the user can adjust it), so the entry reflects the natural flow of the day – morning thoughts, midday moments, evening reflections. An expandable view lets users reopen and read the original conversations behind each entry – exactly as they happened.

   • Optional context: The user decides whether to add the day's weather (automatically fetched) or other context to the entry. Nothing is collected automatically – full user control, in line with Proton's privacy philosophy.

   • Privacy by default: Entries are stored with zero-access encryption, readable by no one except the user (consistent with how Lumo handles chat data).

   • Search across the diary: Entries can be found later by date, keywords, or hashtags, with the option to select and combine multiple days (e.g., "all entries about Silver's vet visits in August").

   • Optional export: At the user's discretion, entries could be exported (e.g., as a document to Proton Drive/Docs) or kept purely inside Lumo.

   Why this matters: Many people want to document their lives but find traditional journaling too formal. Talking to a trusted AI companion – already happening today – becomes a living memory: Lumo remembers the day with you, structured and searchable. This complements my earlier Integrated Notebook idea (https://protonmail.uservoice.com/forums/932842-lumo/suggestions/51643303-integrated-notebook-with-offline-online-toggle-n): the Notebook permanently captures individual insights, while the Diary automatically structures each day's conversations into a living record of the user's life.

   Technical feasibility: Lumo already supports chat, image recognition, summarization, and web search. This feature primarily requires structuring chat history into day-based entries with an index for local search – a logical extension of existing capabilities, delivered with the same zero-access encryption as all Proton products.

   I'd like to propose a built-in Diary Mode for Lumo – a private, encrypted daily journal that grows naturally out of normal conversation.

   The Concept: Instead of filling out a journaling form, the user simply talks to Lumo during the day about what they did, thought, or experienced, and can attach photos. When the day ends (or the next day is opened), Lumo compiles the conversation and images into a structured diary entry.

   Key features:

   • Conversation-to-entry with timestamps: The day's chats become the raw material. Each new day gets a "page" in the diary. Each conversation segment is automatically marked… more

   1 vote

   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  ·  Edit…  ·  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. Within Safari browser, allow to rename a chat

   Within Safari browser, allow to rename a chat

   1 vote

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Lumo has gotten a lot faster since the 2.0 upgrade

   I use Lumo Max in thinking mode all the time, and I just noticed the lag has almost disappeared when it's responding. Just wanted to says thanks!

   1 vote

   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  ·  Edit…  ·  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. Please make a TTS ( text to speech) option it would be sooo cool ❤️‍🔥

   I think it will be really cool if you made a text to speech option reading out loud you know TTS

   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

7. Multi-user Reservation page

   Idea on Proton Calendar to be able to get completely rid of Calendly = a multi-user reservation page, offering the ability to create a link to be sent to external user to book a meeting on the shared availbilities of several users of one company using Proton.

   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

8. Allow Renaming Chats

   Chats are titled automatically based on the first prompt, and cannot be renamed. A rename option feels like an essential feature to have. It would make it much easier to organize 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  ·  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. Manual control of per-chat project knowledge

   As an alternative to Lumo chats ingesting project knowledge automatically from the files available to the project, it would be great if there was a "Manual" mode.

   The user could selectively add and remove which files are used, as the automatic features sometimes needs a few tries to get everything right. This is especially helpful to avoid the chat auto-ingesting metadata files from external project configurations.

   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

10. How Do You Approach Law Coursework?

    https://writemycoursework.co.uk/law may sometimes prove to be tough since it requires a lot of legal research, case studies, law, and referencing. I would like to know which aspects of LLB coursework help UK prove to be difficult for other law students. Is it sourcing information, applying legal principles, IRAC, or something else?

    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

11. Native Excel (.xlsx) editing and export support

    I'd love to see Lumo able to work directly with Excel files — not just reading them, but actually editing them and returning the result as a downloadable .xlsx file.

    My typical use case: I upload a spreadsheet and want Lumo to clean up data, recalculate columns, merge sheets, apply formulas, or reformat cells. Right now, the best I can get back is a markdown table or CSV text that I have to manually copy back into Excel — which is tedious and loses formatting, multiple sheets, and formulas.

    It would be a huge productivity boost if Lumo could:

    Read and analyze .xlsx files (including multiple sheets and formulas)
    Apply requested changes (editing, filtering, calculations, restructuring)
    Return the modified file as a proper .xlsx download — preserving original formatting where possible
    Since privacy is Proton's core promise, this would also be a great differentiator: processing sensitive spreadsheets locally in an encrypted environment instead of uploading them to Big Tech AI tools that train on user data.

    I'd love to see Lumo able to work directly with Excel files — not just reading them, but actually editing them and returning the result as a downloadable .xlsx file.

    My typical use case: I upload a spreadsheet and want Lumo to clean up data, recalculate columns, merge sheets, apply formulas, or reformat cells. Right now, the best I can get back is a markdown table or CSV text that I have to manually copy back into Excel — which is tedious and loses formatting, multiple sheets, and formulas.

    It would be a huge productivity boost if Lumo could:

    Read… 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

12. Title: Per-conversation memory control: "New Private Chat" option + memory containers

    Hi Proton Team,

    Memory shipped with Lumo v2.0, and it's a genuinely useful feature — but right now the only control is a global on/off toggle. I'd like to suggest finer-grained control, in two parts.

    Part 1. "New Private Chat"

    A conversation with no memory loaded in, and no memory saved out. Like a browser private window: fully functional, nothing retained afterwards. Your existing memory stays intact for all your other chats — this session simply doesn't participate.

    Visual indicators:

    In the sidebar: a small icon (lock, or similar) next to the conversation title — left side for LTR languages, right side for RTL
    In the active chat: a small badge on the existing header bar — no new persistent bar, so no screen space lost
    Icon paired with text, so it doesn't rely on colour alone (accessibility)

    Part 2. Memory "containers"

    Separate compartments (work, personal, etc.) that don't bleed into each other:

    Each container holds its own memory context
    A conversation only draws from its assigned container
    "Private chat" is effectively a container with no memory at all — nothing in, nothing out
    This serves two groups currently pulling in different directions:

    Users who want memory get organised, compartmentalised context instead of one blended pool
    Users who are wary of quiet accumulation get a deliberate, reviewable way to use memory — or none at all
    It would turn the current all-or-nothing toggle into genuine user control: stateless by default for those who prefer that, compartmentalised memory for those who don't.

    The browser-container concept is familiar, so it needs almost no explanation — and it aligns with Proton's privacy-first values: the user decides what's on the record and what isn't.

    Thanks for reading!

    Hi Proton Team,

    Memory shipped with Lumo v2.0, and it's a genuinely useful feature — but right now the only control is a global on/off toggle. I'd like to suggest finer-grained control, in two parts.

    Part 1. "New Private Chat"

    A conversation with no memory loaded in, and no memory saved out. Like a browser private window: fully functional, nothing retained afterwards. Your existing memory stays intact for all your other chats — this session simply doesn't participate.

    Visual indicators:

    In the sidebar: a small icon (lock, or similar) next to the conversation title — left side for LTR languages,… 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

13. Drag calendar event and reschedule by 15-minute increments instead of 30min

    Drag calendar events and reschedule by 15-minute increments instead of 30min

    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

14. Conversation tree to help navigate current chat

    In a single chat, it's common to ask follow up questions, or clarifications, and sometimes related but slightly different angles, and chats can become long and convoluted. I frequently scroll back in a chat looking for details in a previous answer. Navigation would be much easier if each chat showed a tree in the sidebar that lists each question I asked in the current chat. (This would also be quite useful if I come back to review the chat at a later date.)

    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

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

    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

16. 🧠 Advanced Persistent Project Memory & Engineering Partner Mode

    🧠 Advanced Persistent Project Memory & Engineering Partner Mode

    Summary

    Enable Lumo to maintain long-term project context across sessions and operate as a proactive engineering partner rather than reactive assistant.

    Problem Statement

    Current conversation memory is session-bound. Each new chat requires re-establishing context about:
    - Project architecture decisions and trade-offs
    - Technology stack specifics (local models, frameworks, deployment targets)
    - Previous iterations and lessons learned
    - Ongoing development challenges

    This creates friction for complex, multi-session projects and forces users to constantly re-explain context.

    Proposed Solution

    Feature 1: Project-Specific Memory Stores

    Description: Allow users to create and manage named "project memory" objects that persist across separate conversations.

    Key Capabilities:
    - Store: Architecture diagrams, tech stack details, API contracts, codebase structure
    - Query: Natural language retrieval of project-specific knowledge
    - Update: Incremental additions as project evolves
    - Export/Import: Share project contexts between team members

    Technical Implementation:
    ```yaml
    ProjectMemory:
    - Name: "adrenalina-prime"
    - Created: timestamp
    - Tags: ["engineering", "agent-system", "local-llm"]
    - ContextBlocks:
    - Type: "architecture" | "api-contract" | "tech-stack" | "decision-log"
    - Content: markdown/text
    - Last_Modified: timestamp
    Feature 2: Engineering Partner Mode

    Description: Toggle switch for interaction style optimization.
    Standard Mode Engineering Partner Mode
    Reactive Q&A Proactive gap identification
    Generic responses Stack-aware suggestions (e.g., knows Ollama vs OpenAPI constraints)
    No state awareness Remembers previous session's blockers
    Neutral tone Direct, technical communication (zero sugar-coating)
    Feature 3: Contextual Code Awareness

    Description: When uploading code files, Lumo should build internal map of:

    File dependencies and imports
    Function signatures and interfaces
    Testing coverage and gaps
    Potential security vulnerabilities based on patterns
    

    Integration Points:

    Auto-detect language/framework from file extensions
    Cross-reference with known local model capabilities (e.g., deepseek-coder:6.7b context window limits)
    Suggest tests before implementation, not after
    

    User Stories

    "As a developer working on a multi-week project, I want to resume conversation without explaining what we built last week."
    
    "As an engineer, I want Lumo to notice architectural inconsistencies between my code and stated design goals."
    
    "As a team lead, I want to share project context with junior developers via exported memory bundles."
    

    Success Metrics
    Metric Target
    Reduction in context-setting time >60% decrease
    Multi-session project completion rate +40% increase
    User satisfaction (Engineering users) NPS +25 points
    Memory feature adoption >50% of Lumo Plus users within 6 months
    Risks & Mitigations
    Risk Mitigation
    Privacy concerns with persistent data All memory encrypted end-to-end; opt-in only
    Memory bloat over time Automatic summarization; user-controlled cleanup
    Inaccurate recall Version history with diff view; confidence scoring on retrieved context
    Competitive Differentiation

    Other AI assistants (Claude, ChatGPT, etc.) offer:

    ✅ Long context windows
    ❌ Project-scoped memory persistence
    ❌ Role-based interaction modes
    ❌ Architecture-aware code review
    

    Lumo's opportunity: Become the first privacy-focused AI with persistent project memory + professional mode optimization.

    Priority: High Effort: Medium (requires backend memory infrastructure + UI toggles) Timeline Estimate: 3-4 sprints for MVP

    Related Features:

    Custom Lumos (already exists, but lacks memory integration)
    Persistent Memory (exists, but not project-scoped)
    File Analysis (exists, but lacks cross-session code mapping)
    

    🧠 Advanced Persistent Project Memory & Engineering Partner Mode

    Summary

    Enable Lumo to maintain long-term project context across sessions and operate as a proactive engineering partner rather than reactive assistant.

    Problem Statement

    Current conversation memory is session-bound. Each new chat requires re-establishing context about:
    - Project architecture decisions and trade-offs
    - Technology stack specifics (local models, frameworks, deployment targets)
    - Previous iterations and lessons learned
    - Ongoing development challenges

    This creates friction for complex, multi-session projects and forces users to constantly re-explain context.

    Proposed Solution

    Feature 1: Project-Specific Memory Stores

    Description: Allow users to create and manage named "project memory"… 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

17. Preview Images in Project Knowledge Before Deleting – Show Thumbnails or Click-to-Open

    Currently, when viewing files in the "Project Knowledge" section, images are displayed only as generic icons with filenames (e.g., IMG_9630.png). There is no way to preview the actual image content before deciding to delete it. This creates a significant risk of accidentally deleting the wrong image, especially when managing multiple uploads with similar or non-descriptive filenames.

    I request a preview feature for images in the Project Knowledge panel with the following specifics:

    • Thumbnails: Display small thumbnail previews of the images instead of just generic icons so users can instantly identify the content.
    • Click-to-Open: Allow users to tap or click an image to open a larger preview window before confirming any action.
    • Confirmation Dialog: When clicking the delete (X) button on an image, show a confirmation popup where the image preview is clearly visible, asking "Are you sure you want to delete this specific image?"

    Why this matters: For users who upload many reference images (photos, diagrams, screenshots) to guide Lumo's responses, being able to visually verify content before deletion is critical. It prevents accidental data loss and improves confidence when managing project context. This is a basic usability standard seen in most file management systems (like Photos or Drive) and should apply here too.

    Currently, when viewing files in the "Project Knowledge" section, images are displayed only as generic icons with filenames (e.g., IMG_9630.png). There is no way to preview the actual image content before deciding to delete it. This creates a significant risk of accidentally deleting the wrong image, especially when managing multiple uploads with similar or non-descriptive filenames.

    I request a preview feature for images in the Project Knowledge panel with the following specifics:

    • Thumbnails: Display small thumbnail previews of the images instead of just generic icons so users can instantly identify the content.
    • Click-to-Open: Allow users to tap or click an… 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

18. Lumo needs access to the current date and time

    Having access to the exact current date and time is important for certain tasks. Lumo is able to retrieve the date from its context, but not the time. And it is unable to confirm the date timezone (I assume it is UTC). A tool to fetch the current date and time, and optionally to specify the timezone for which the date and time is requested, would be a helpful feature.

    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. Anthropic Claude and Google Gemini Import

    Visionary user here switching from Anthropic Claude and Google Gemini to Proton Lumo Max I'd like to have an option as a user to import my data and memory as easy as possible. Today a manual import usually exceeds the context of the chat and even with multiple chat's it's not possible to get all data into Lumo. So please Proton give us an option to import our data.

    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

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