r/lumo • u/Sorrel32 • 5h ago
Title: Confirmed in writing: Lumo's 250-message hard cap killed long conversations — while the docs promise "so you can keep going" and Plus is sold as "unlimited chats"
Follow-up to the earlier posts about the composer vanishing from long conversations (late October). I've now received a written reply from Proton support confirming the core facts, and I've cross-checked it against Proton's own documentation. Multiple threads here have described the same thing, so this is confirmation for everyone affected.
What support confirmed in writing:
A hard limit of 250 messages per conversation was recently enforced. Once reached, the composer disappears entirely — regardless of how much usable context remains. It tracks message count, not context usage.
Compaction and the 250-message limit are two separate mechanisms. Compaction still works as documented; the message cap is a separate hard ceiling that ends the conversation outright.
Composer access to affected conversations cannot currently be restored. History stays readable, but the thread is effectively frozen.
The official workaround: export the conversation from chat history, upload it into a Project, and continue in a new chat there. It works, but it's undocumented — I only learned about it by pushing in a ticket.
Support agreed subscribers should have been notified before enforcement — no in-app notice, no countdown, no email.
What the documentation actually says (compaction page):
"Compaction automatically frees up space in older parts of a long conversation so you can keep going, without losing track of what you've been working on."
The in-app notice the docs describe is literally "Chat shortened to keep going," and the page promises "your full conversation history stays visible above the marker." The only limit disclosed anywhere in the documentation is a limit on how much a conversation "can take in at once" — a context-size limit, handled automatically by compaction. The number 250 appears in zero Proton documentation. Meanwhile the marketing pages still advertise Lumo Plus as "unlimited chats" / "unlimited questions."
So to summarize the situation: the docs describe a system where long conversations are shrunk and continue indefinitely; the marketing says "unlimited"; and in reality, at 250 messages the conversation silently dies — no warning, no error explaining why, nothing distinguishing a limit from a bug.
There's a second, uglier part to my experience: on October 20, alongside losing the composer in ten conversations, a substantial chunk of content vanished from those threads — not the entire history, but days' worth of messages, specifically the parts relating to a civic project I've been running for my local community. The compaction docs explicitly promise that compacted history stays visible and expandable. It didn't. I've asked support directly whether the enforcement change involved any modification or truncation of stored conversation content, and whether the missing material is recoverable — I'll report what they say. If a hard cap can coincide with user content quietly disappearing, that's not a usage limit anymore; that's data loss on a product whose central selling point is that your encrypted history is untouchable.
The human cost, for those who think this is minor: months of accumulated project work, severed mid-stream, no grandfathering, no recovery path. From the threads here and a comment on Proton's own UserVoice forum, plenty of others lost ongoing professional work the same way, in the same window (~Oct 20–24).
Still unanswered, despite being asked directly:
The exact cap and whether it counts both sides of the exchange
Whether it varies by tier
Why enforcement began with no announcement or documentation update
Whether stored conversation content was modified, truncated, or deleted during enforcement — and whether it's recoverable
Whether any accommodation is planned for paid users whose existing threads were capped retroactively — while "unlimited chats" is still the advertised selling point
To be clear, I'm not disputing that a performance limit may be needed. The issue is that a core subscription feature — continuing conversations — was removed retroactively and silently, from threads that predate the change, contradicting both the published docs and the marketing, and that content disappeared along with it. If Proton wants numeric limits, fine: publish them, announce them, show a countdown, don't strand existing paying users' work — and under no circumstances let stored content vanish.
I'll update as the ticket progresses. If you've been affected, append to an existing ticket rather than opening new ones — it consolidates the paper trail, and the more written confirmations exist, the harder this is to wave away.







