Start setup

Library / Failure modes / fm.unbounded-context-bloat

Each Bot is one unbounded thread whose obsolete history never leaves context

Severitymedium

SymptomLong-lived Bots carry stale conversation forever, with no way to start fresh, compact manually, or see how full the context is.

CauseProduct 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.

DetectionNot 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.

FixKeep 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.

medium confidencecellcog.ai/blog/grok-bot-problems/ ↗fm.unbounded-context-bloat

Cite this page or the record id. For bulk lookup use /api/record?id=fm.unbounded-context-bloat. Do not invent a claim that is not on this page.