Repository navigation
ContextOverflowError kills session instead of triggering compaction #14824
Description
Bug Description
When the LLM API returns a context overflow error (e.g., Bedrock Claude hitting context limit), the session dies permanently. Users must create a new session, losing all conversation context.
Root Cause
In processor.ts, the ContextOverflowError catch block has a // TODO: Handle context overflow error comment that does nothing. The error falls through to be treated as fatal (message.error = error, return 'stop').
Expected Behavior
The session should auto-compact (summarize conversation, reduce context) and continue, similar to how Codex and Cline handle context overflow.
Steps to Reproduce
- Use a provider with limited context (e.g., Bedrock Claude)
- Have a long conversation with many tool calls
- Eventually hit context limit → session becomes unresponsive
Environment
- Provider: AWS Bedrock (Claude)
- Also affects any provider with context limits
Activity
github-actions commentedon Feb 23, 2026
This issue might be a duplicate of existing issues. Please check:
// TODO: Handle context overflow errorinprocessor.tswith no implementation, causing context overflow to kill the session instead of triggering compaction. That report also proposes auto-compaction as the fix and references the same code paths.If your issue is specifically about Bedrock/provider-agnostic context token limits (as opposed to 413 payload size errors), it may still be worth keeping open as a distinct scenario, but please review #14562 first and comment there if it covers your case.
github-actions commentedon Apr 25, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.