Skip to content

Moonshine

My feedback

3 results found

  1. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Moonshine commented  · 

    This is exactly the issue I'm experiencing — but since 20–24 October 2026, it has escalated from a limit to a full lockout: the composer disappears, and conversations become read-only mid-session. Professional conversations used continuously since last year were severed with no warning, notice, or grandfathering.

    I've opened a dedicated suggestion with the timeline, the unanswered questions, and proposals for relief: https://protonmail.uservoice.com/forums/932842-lumo/suggestions/51863964-composer-lockout-250-message-limit-introduced-wit

    If you've been affected, please vote and comment there — the more documented reports, the harder this is to dismiss.

    Moonshine supported this idea  · 
  2. 95 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Moonshine commented  · 

    Related, and more urgent in my view: Lumo Plus now enforces a hard 250-message limit per conversation, introduced around 20–24 October with no announcement and no documentation. Past that point the composer disappears and the conversation becomes read-only. Several professional conversations I've used continuously since last year were severed mid-session — no warning, no notice, no grandfathering.

    This bears directly on your suggestion. Competitors advertise ~1M-token context windows (Gemini 3.1 Pro, Claude 5, GPT-5.6/6 Astra), but Lumo sits at 131.1K. Even if that gap were closed, a 250-message ceiling would still terminate conversations first. Your point about paying customers funding the extra compute is exactly the model that would solve this: a paid continuity tier, with disclosed numeric limits.

    I've opened a dedicated suggestion here: https://protonmail.uservoice.com/forums/932842-lumo/suggestions/51863964-composer-lockout-250-message-limit-introduced-wit — if you're affected, please vote there so this gets documented publicly.

    Export now exists, but it's wholly inadequate: it preserves the text, not the working relationship and the collaboration built with Lumos over time. Older conversations under "All Chats" don't show the export option at all — not less important, just put aside, and they need to be continued.

    Still unanswered by Proton: (1) is there a 250-message limit on Lumo Plus, and where is it documented; (2) what are the per-conversation limits for Business and Lumo Professional; (3) what is the token/context allowance in numbers; (4) why was this change never communicated before it affected users' work.

    Two steps would resolve most of it. Immediate relief: grandfathering — existing conversations regain their composer and continue with the Lumos that hold their history, with any limit applying only to new chats. Lasting solution: guaranteed continuity for those willing to pay, with transparent numeric limits — the direction you're arguing for here.

    Moonshine supported this idea  · 
  3. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Moonshine shared this idea  ·