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
{{ message }}
Repository navigation
[FEATURE]: retry automatically after internet server error #19100
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
There are many issues opened for specific 'internal server error' messages, but this one is about a generic way to handle this error. As it is now, opencode just stops interacting with the LLM provider. What I propose is to retry in 5 seconds or so, which beats me having to write continue and keep watch all the time for long running agent sessions.
It's funny that I also wrote "continue" or "try again" all the time when network failed. For my part, I'd already be happy with a /retry command or something similar. It's a bit odd to have to inform the ai about a broken connection..
Activity
github-actions commentedon Mar 25, 2026
This issue might be a duplicate of existing issues. Please check:
MartyMcFlyInTheSky commentedon Mar 30, 2026
It's funny that I also wrote "continue" or "try again" all the time when network failed. For my part, I'd already be happy with a
/retrycommand or something similar. It's a bit odd to have to inform the ai about a broken connection..PGoski commentedon Apr 5, 2026
Retry logic seems to strict. Would be great to have configuration for below issue.
LbsEvan commentedon Apr 8, 2026
Sometimes, when the model service provider's interface returns an empty result, the opencode will get stuck there and will never retry.
github-actions commentedon Jul 5, 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.