Skip to content

[FEATURE]: retry automatically after internet server error #19100

Closed as not planned

Description

@imqqmi

Feature hasn't been suggested before.

  • 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.

Thoughts?

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Mar 25, 2026
  2. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Mar 25, 2026
  3. github-actions commented on Mar 25, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  4. MartyMcFlyInTheSky commented on Mar 30, 2026

    @MartyMcFlyInTheSky

    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..

  5. PGoski commented on Apr 5, 2026

    @PGoski

    Retry logic seems to strict. Would be great to have configuration for below issue.

    Image
  6. LbsEvan commented on Apr 8, 2026

    @LbsEvan

    Sometimes, when the model service provider's interface returns an empty result, the opencode will get stuck there and will never retry.

  7. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  8. github-actions commented on Jul 5, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions