{"found":true,"collection":"failure_modes","library_url":"https://www.grokbotdb.com/library/fm.unbounded-context-bloat","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"fm.unbounded-context-bloat","title":"Each Bot is one unbounded thread whose obsolete history never leaves context","symptom":"Long-lived Bots carry stale conversation forever, with no way to start fresh, compact manually, or see how full the context is.","cause":"Product design: one continuous thread per Bot, with summarisation only near the limit. Confirmed by Cursor staff on 2026-08-20: no same-Bot fresh session, no manual compaction, no visible context meter.","detection":"Not directly observable, since there is no context meter. Suspected as a contributor to the usage-burn reports, because context is re-sent on every step and metering is by token.","fix":"Keep changing facts in a file the Bot reads and reopens before every run rather than in its memory. Where a clean context is needed, create a new Bot rather than trying to reset an existing one.","severity":"medium","source_id":"src.tp.cellcog.problems","source_url":"https://cellcog.ai/blog/grok-bot-problems/","confidence":"medium","first_seen":"2026-09-03","last_verified":"2026-09-03"}}