You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think I found one specific case of this. On v1.15.7 with mimo-v2.5-free,
my session hit the 1,048,576 token context limit and the provider returned
a context_length_exceeded error. But fromError() classified it as
NamedError.Unknown with message "Network connection lost." — which isn't
retryable and doesn't trigger compaction.
The fix would be to detect context overflow patterns in the Error catch-all
before it falls through to NamedError.Unknown. Something like checking for
/context|token|limit|exceed in the error message.
Activity
fix(opencode): classify context overflow errors that bypass APICallEr…
AdityaPagare619 commentedon Jun 23, 2026
I think I found one specific case of this. On v1.15.7 with mimo-v2.5-free,
my session hit the 1,048,576 token context limit and the provider returned
a context_length_exceeded error. But fromError() classified it as
NamedError.Unknown with message "Network connection lost." — which isn't
retryable and doesn't trigger compaction.
The fix would be to detect context overflow patterns in the Error catch-all
before it falls through to NamedError.Unknown. Something like checking for
/context|token|limit|exceed in the error message.
github-actions commentedon Aug 23, 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.