-
-
Notifications
You must be signed in to change notification settings - Fork 52.9k
Open
Labels
staleMarked as stale due to inactivityMarked as stale due to inactivity
Description
Description
Telegram channel receives "Context overflow: prompt too large for the model" error messages while the webchat dashboard shows correct, complete responses for the same session/messages.
Environment
- Clawdbot version: 2026.1.24-3
- Model: anthropic/claude-opus-4-5
- Context usage: 42% (84k/200k) - well under limit
- Channels: Telegram + Webchat dashboard
Steps to Reproduce
- Have both Telegram and webchat dashboard open for the same session
- Send messages that trigger tool calls (e.g.,
execwith grep) - Observe: Dashboard shows full response, Telegram shows "Context overflow" error
Expected Behavior
Both channels should show the same response since they share the same session.
Actual Behavior
- Dashboard: Shows complete, correct response with tool results
- Telegram: Shows "Context overflow: prompt too large for the model. Try again with less input or a larger-context model."
The error appears multiple times on Telegram, interleaved with valid responses.
Investigation Results
- No actual overflow: Session status shows 84k/200k tokens (42%)
- No errors in session files:
grep isError:truereturns 0 results across all session files - Model is working: Responses are generated successfully (visible in dashboard)
- Error not logged: The overflow errors sent to Telegram are not recorded in session
.jsonlfiles
Evidence
Screenshots show:
- Same timestamp messages
- Dashboard: full response with tool output
- Telegram: "Context overflow" error (2x)
This suggests the error is generated in a Telegram-specific code path, not from the actual model/session.
Possible Causes
- Race condition in message delivery
- Retry mechanism failing on Telegram but not dashboard
- Stale error messages being replayed
- Different error handling paths for different channels
Workaround
None found - issue is intermittent but reproducible.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
staleMarked as stale due to inactivityMarked as stale due to inactivity