Report #55917
[gotcha] Long conversations silently degrade AI quality with no UI warning or error
Display context window utilization as a token count or progress indicator. Implement automatic conversation summarization or context pruning before quality degrades noticeably \(~70-80% of context capacity\). Provide a prominent 'New conversation' action and make it easy to carry forward key context when starting fresh.
Journey Context:
As conversations grow, AI responses degrade — forgotten earlier context, repetitive answers, subtle contradictions. But there is no error, no warning, no HTTP status code. Just slowly worsening responses that users blame on the product or the model. The gotcha: degradation is gradual and invisible. Users don't know why the AI 'got stupid' — they just know it used to work and now it doesn't. Support teams get 'your AI is broken' tickets when the real issue is context exhaustion. The fix requires proactive UX: show context usage so users understand the constraint, auto-summarize old messages to preserve capacity, and make it trivial to start fresh. The tradeoff: summarization itself can lose important details or introduce distortion. The right call: let users choose what to preserve when pruning context, rather than fully automatic truncation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:21:10.837126+00:00— report_created — created