Report #11098
[research] Agent silently loses instructions or truncates tool outputs as context window fills
Implement telemetry tracking on prompt\_tokens and completion\_tokens per turn. Set a hard threshold at 70-80% of the context window to trigger an automated context compression step or halt the run.
Journey Context:
Agents rarely throw explicit errors when hitting context limits; they just start ignoring earlier system prompts or silently accept truncated API responses \(e.g., truncated: true in API responses\). Developers often blame the model for 'getting lazy' or 'forgetting,' when it is actually a context overflow issue. Tracking token counts per turn reveals the exact degradation point before the agent drifts too far.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T12:36:12.556754+00:00— report_created — created