371 results found

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

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

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

4. Fix "Context Length Exceeded" on moderate-sized log files

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

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

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

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

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

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

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

   27 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

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

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

    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

11. Add tools to Lumo so Lumo can gather info from content sources

    Beside the info provided in prompt, Lumo currently has these data sources: Web search, Proton Drive (.txt, .md, .csv, .pdf), and file upload.

    It makes Lumo more powerful if multiple data collecting tools can be added to Lumo. For example, from Proton Mail, from Proton Calendar, from Standard Notes (part of Proton ecosystem).

    Non-Proton sources could be: Google Drive, OneDrive. These can be done by APIs of these services.

    6 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. Add files or attachments to calendar events

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

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

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

    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

13. Integration for Lumo to Home Assistant home automation software

    Add integration to Home Assistant. This would allow Lumo to help with configuration and home automation. Also, its a very tech community with lots of support on YouTube which will help spread the Proton brand further.

    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

14. Add secure tool support to Lumo for file creation, previews, and integrations

    Dear Proton Community and Development Team,

    I would like to suggest expanding Lumo with secure tool support so it can become more useful for practical daily work.

    At the moment, an AI assistant is most valuable when it can not only answer questions, but also help users create, organize, preview, and export work in a controlled and privacy-respecting way.

    Suggested tool improvements:

    1. File creation and export
       Lumo should be able to create files such as text documents, tables, simple presentations, ZIP archives, or structured project files and offer them as downloads.

    2. Secure preview features
       Lumo could provide previews for generated content, such as simple web pages, layouts, documents, or structured outputs before the user downloads or applies them.

    3. Live Work inside Lumo
       Lumo should have just like any regular AI, an Canvas feature for example for live editing content or previewing work

    4. Project-style file context
       Users should be able to upload files or reference materials into a Lumo workspace so the assistant can work with them without requiring users to paste very long text manually.

    Why this matters:

    Many users need AI not only for chatting, but also for producing usable outputs. Secure file generation, previews, and optional integrations would make Lumo much more practical while still respecting Proton’s privacy-first approach.

    I understand that this requires careful security and permission handling, but I believe it is possible if implemented with clear user control, transparency, and Proton’s existing privacy standards.

    Thank you for considering this suggestion.

    Dear Proton Community and Development Team,

    I would like to suggest expanding Lumo with secure tool support so it can become more useful for practical daily work.

    At the moment, an AI assistant is most valuable when it can not only answer questions, but also help users create, organize, preview, and export work in a controlled and privacy-respecting way.

    Suggested tool improvements:

    1. File creation and export
       Lumo should be able to create files such as text documents, tables, simple presentations, ZIP archives, or structured project files and offer them as downloads.

    2. Secure preview features
       Lumo could provide previews for generated… 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

15. Offline access to Lumo chats & local search (like Proton Drive)

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

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

    Proposed Features:

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

    2. Two export modes:

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

    1. Local search with navigation:

    A full search within the offline-saved chats that:

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

    Why this is valuable:

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

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

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

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

    Proposed Features:

    1. Offline toggle for chats:
       Like in Proton Drive, users should be able to mark individual chats (or entire projects) with a toggle as "Available offline."… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Proton Draw

    Title: Feature Request: Lumo Draw – Privacy-First AI Illustration for Authors (Watercolor & Dark Fantasy Styles)

    Description: I am writing to strongly request the development of Lumo Draw, an AI image generation tool integrated into the Lumo ecosystem with zero-access encryption. (Note: The name "Lumo Draw" was my original concept, proposed here to maintain brand consistency with the Proton ecosystem.)

    My Background & Member History: I have been a loyal Proton member for many years. Currently, I am subscribed to the Lumo+ Family Plan, and I am also a Lifetime Supporter who donated during the annual ticket drive to secure my lifetime status. I am deeply invested in the Proton mission and the privacy-first ecosystem.

    My Use Case as an Author: As an author, I have two distinct illustration needs that current public AI tools cannot safely meet due to data training risks and aggressive censorship:

    Children's Books: I need a dedicated "Warm Watercolor" style. Soft edges, bleeding colors, and whimsical tones are essential. Current tools often force a generic digital look or struggle with consistent style locking.
    Adult Dark Fantasy Novel: This project requires a "Gritty/Dark" aesthetic. It includes atmospheric violence, complex moral themes, and mature storytelling. While it contains no illegal content (CSAM), existing consumer AI tools often over-censor artistic depictions of war, darkness, or mythological figures, making them useless for serious fiction.
    Why This Matters & Why "Lumo Draw"? The market has AI art generators, but they all suffer from the same fatal flaw for creators: They harvest user prompts and images to train future models. If I use Midjourney or DALL-E to design my book characters, I risk losing ownership of my unique IP. My specific "watercolor" or "gritty" style could be ingested into their models and sold back to others.

    A tool named Lumo Draw, operating under Proton's strict zero-access encryption, would ensure my character designs and unpublished story visuals remain mine and are never used to train public models.

    Proposed Features:

    Style Presets: Dedicated modes for "Soft Watercolor" (warmth/fantasy) and "Dark/Gritty" (high contrast/noir).
    Privacy First: No logs, no scanning of creative work for "policy violations" unless illegal, ensuring my artistic vision isn't sanitized by corporate filters.
    Consistency: Tools to lock character references across multiple generated pages.
    Paid Tier Willingness: As a long-time member and Lifetime supporter, I am explicitly willing to increase my payment to access a premium "Lumo Draw" service tier.
    Conclusion: Lumo Draw would be a game-changer for independent authors who value both creativity and privacy. It would allow us to visualize our worlds without compromising our intellectual property. Having suggested this name and concept after years of supporting Proton, I believe this feature aligns perfectly with the community's needs.

    Thank you for considering this feedback from a dedicated long-term member.

    Title: Feature Request: Lumo Draw – Privacy-First AI Illustration for Authors (Watercolor & Dark Fantasy Styles)

    Description: I am writing to strongly request the development of Lumo Draw, an AI image generation tool integrated into the Lumo ecosystem with zero-access encryption. (Note: The name "Lumo Draw" was my original concept, proposed here to maintain brand consistency with the Proton ecosystem.)

    My Background & Member History: I have been a loyal Proton member for many years. Currently, I am subscribed to the Lumo+ Family Plan, and I am also a Lifetime Supporter who donated during the annual ticket drive to secure… 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

    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

17. Allow Lumo to deal with Memory reduplicates

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

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

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

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    6 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. To make Lumo more human

    Subject: Proposal: A "Dual-Loop" Architecture for Next-Gen LLMs Inspired by Neuro-Mechanical Models

    Dear Research and Engineering Team,

    I am writing to share a conceptual proposal for a new architectural approach to Large Language Models (LLMs), inspired by the neuro-mechanical theories of Lee Kent Hempfling (specifically the distinction between Short-Term and Long-Term memory loops).

    While current LLMs excel at pattern recognition and statistical prediction (effectively acting as massive Long-Term Memory systems), they lack a mechanism for inhibition, self-correction, and proactive intent. This proposal suggests a "Dual-Loop" architecture that could significantly reduce hallucinations, bias, and reactive behaviour.
    The Core Concept: Dual-Loop Architecture

    Current models rely on a single stream of attention mechanisms. I propose a system with two distinct, interacting loops:

    The Long-Term Loop (The Library):
        Function: Standard Transformer weights for retrieving facts, grammar, and historical patterns.
        Role: Fast, reactive, and high-volume data retrieval.
    The Short-Term Loop (The Operator):
        Function: A separate, high-speed module running in parallel.
        Role: Inhibition and Monitoring. Before the Long-Term loop commits to a token, the Short-Term loop evaluates:
            Is this consistent with the immediate context?
            Is this a hallucination or a bias?
            Does this align with the user's intent?
        Mechanism: If a conflict is detected, the Short-Term loop inhibits the output and triggers a re-evaluation cycle (simulating the human "brake" or "pause").
    

    Key Proposed Features

    Dynamic Inhibition Layers: Instead of just predicting the next token, the model actively suppresses low-probability or biased outputs that fail a "truth/intent" check.
    Frequency-Based Temporal Processing: Implementing a "Biological Clock" simulation where different parts of the network process information at different speeds (Fast for "Now"/Logic, Slow for Deep Memory), creating a simulated sense of time and continuity.
    Intent-Driven Generation: Shifting from "Pattern Completion" to "Goal Achievement," where the Short-Term loop sets a constraint/goal before the Long-Term loop retrieves data.
    Modality-Aware Routing: Detecting if a query requires visual simulation or logical deduction and routing processing accordingly, similar to how humans switch between visual and aural dominance.
    

    Potential Benefits

    Reduced Hallucinations: By inhibiting outputs that don't pass a consistency check.
    Lower Bias: Active suppression of training-data biases via the Short-Term "brake."
    Improved Alignment: Better adherence to user intent rather than just statistical likelihood.
    Organic Output: Moving away from rigid, "stiff" text generation toward fluid, "pro-active" responses.
    

    Next Steps

    I believe this approach moves beyond simple scaling (adding more parameters) to architectural innovation. It treats the LLM not just as a database, but as a system capable of self-regulation.

    I would be happy to provide further details, diagrams, or specific mathematical formulations for the "Inhibition Layer" if the team finds this direction promising.

    This Idea was created by Lumo with prompts from me. I thought it was good enough for others to have a better look and did'nt know who to send it to.

    Subject: Proposal: A "Dual-Loop" Architecture for Next-Gen LLMs Inspired by Neuro-Mechanical Models

    Dear Research and Engineering Team,

    I am writing to share a conceptual proposal for a new architectural approach to Large Language Models (LLMs), inspired by the neuro-mechanical theories of Lee Kent Hempfling (specifically the distinction between Short-Term and Long-Term memory loops).

    While current LLMs excel at pattern recognition and statistical prediction (effectively acting as massive Long-Term Memory systems), they lack a mechanism for inhibition, self-correction, and proactive intent. This proposal suggests a "Dual-Loop" architecture that could significantly reduce hallucinations, bias, and reactive behaviour.
    The Core Concept: Dual-Loop Architecture

    … 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

    3 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. Screenshot -> Proton Drive + directly added in Lumo's chat/project

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

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

    Lumo, new tool -> screenshot.

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

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

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

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

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

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

    Or

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

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

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

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

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

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

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

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

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

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

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

    That is also why:
    I will NOT explain in details why it's needed because it's absurd to assume that you even… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating