Report #77028
[gotcha] AI silently 'forgets' earlier conversation context when the context window fills, with no warning or UI indication
Track cumulative token usage across the conversation. When approaching 80% of the context limit, show a proactive UI warning \('This conversation is getting long — earlier messages may be forgotten'\). Implement a summarization or context management strategy before hitting the limit. Never silently truncate — always inform the user.
Journey Context:
Every LLM has a fixed context window. When a conversation exceeds it, the model silently drops the oldest messages. The user has no indication — the AI just stops referencing earlier context. This is devastating in long working sessions: the user builds on shared context for 30 minutes, then the AI acts as if the first 20 minutes never happened. There's no error, no warning, just a subtle shift to worse, context-free responses. The user often blames themselves \('I must have been unclear'\) rather than recognizing a system limitation. The fix requires proactive token tracking and UI communication. Some implementations summarize old context and inject it as a system message, but summarization loses detail and can introduce errors. The honest approach is to warn the user and offer to start a fresh session with a summary carryover. The gotcha: many developers assume the API will error or warn on context overflow — it doesn't. It silently truncates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T11:53:13.401965+00:00— report_created — created