anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[Feature Request] Configurable Retry Mechanism via opencode.json #1985

New Issue
Open
opened 2026-02-16 17:33:34 -05:00 by yindo · 8 comments
yindo commented 2026-02-16 17:33:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @H0llyW00dzZ on GitHub (Oct 7, 2025).

Originally assigned to: @rekram1-node on GitHub.

This is a request to add a retry mechanism that can be configured through opencode.json.

For example, we should be able to define retry settings per provider—such as allowing up to 3 retries within a customizable time window (e.g., 5 seconds). This would improve reliability, especially since the current implementation lacks configurable retries.

Originally created by @H0llyW00dzZ on GitHub (Oct 7, 2025). Originally assigned to: @rekram1-node on GitHub. This is a request to add a **retry mechanism** that can be configured through `opencode.json`. For example, we should be able to define retry settings per provider—such as allowing up to 3 retries within a customizable time window (e.g., 5 seconds). This would improve reliability, especially since the current implementation lacks configurable retries.
yindo commented 2026-02-16 17:33:35 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Oct 7, 2025):

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

  • #833: Already requests automatic retry handling for LLM overload errors with configurable retry limits and delays
  • #2455: Requests improved error handling with retry counters and timeout displays (mentions "Retrying 1 or 10" with countdown)
  • #1592: Requests configurable request delay settings between API calls
  • #2974: Related timeout configuration issues that aren't being respected in opencode.json

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Oct 7, 2025): This issue might be a duplicate of existing issues. Please check: - #833: Already requests automatic retry handling for LLM overload errors with configurable retry limits and delays - #2455: Requests improved error handling with retry counters and timeout displays (mentions "Retrying 1 or 10" with countdown) - #1592: Requests configurable request delay settings between API calls - #2974: Related timeout configuration issues that aren't being respected in opencode.json Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:33:35 -05:00
Author
Owner
Copy Link
Copy Source

@H0llyW00dzZ commented on GitHub (Oct 7, 2025):

Also This retry mechanism should also handle provider-specific API errors.

@H0llyW00dzZ commented on GitHub (Oct 7, 2025): Also This retry mechanism should also handle provider-specific API errors.
yindo commented 2026-02-16 17:33:35 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Oct 7, 2025):

Yeah we do already have retries setup but making it configurable makes sense. This is probably a lower priotiery currently tho

@rekram1-node commented on GitHub (Oct 7, 2025): Yeah we do already have retries setup but making it configurable makes sense. This is probably a lower priotiery currently tho
yindo commented 2026-02-16 17:33:35 -05:00
Author
Owner
Copy Link
Copy Source

@H0llyW00dzZ commented on GitHub (Oct 7, 2025):

Yeah we do already have retries setup but making it configurable makes sense. This is probably a lower priotiery currently tho

@rekram1-node, regarding the configurable retry mechanism for handling API errors, I think it would be better to use a fixed interval. For example, we could set 4 retries over 10 seconds—so each retry happens every 2.5 seconds—or simply retry every 10 seconds. This would be simpler than increasing the delay between retries (i.e., exponential backoff).

@H0llyW00dzZ commented on GitHub (Oct 7, 2025): > Yeah we do already have retries setup but making it configurable makes sense. This is probably a lower priotiery currently tho @rekram1-node, regarding the configurable retry mechanism for handling API errors, I think it would be better to use a fixed interval. For example, we could set 4 retries over 10 seconds—so each retry happens every 2.5 seconds—or simply retry every 10 seconds. This would be simpler than increasing the delay between retries (i.e., exponential backoff).
yindo commented 2026-02-16 17:33:35 -05:00
Author
Owner
Copy Link
Copy Source

@kierr commented on GitHub (Oct 8, 2025):

Yeah we do already have retries setup but making it configurable makes sense. This is probably a lower priotiery currently tho

What's the default for retries at the moment? It might be low priority for those using stable internet, reliable providers, and perfectly compatible models... but for those who aren't so lucky... it's an easy way to recover from errors and hiccups without having to habitually say "Continue".

Claude Code has the ENV var CLAUDE_CODE_MAX_RETRIES which I have set to 100. That works for API errors as well as API timeouts. Opencode seems to give up after a single timeout?

@kierr commented on GitHub (Oct 8, 2025): > Yeah we do already have retries setup but making it configurable makes sense. This is probably a lower priotiery currently tho What's the default for retries at the moment? It might be low priority for those using stable internet, reliable providers, and perfectly compatible models... but for those who aren't so lucky... it's an easy way to recover from errors and hiccups without having to habitually say "Continue". Claude Code has the ENV var `CLAUDE_CODE_MAX_RETRIES` which I have set to 100. That works for API errors as well as API timeouts. Opencode seems to give up after a single timeout?
yindo commented 2026-02-16 17:33:35 -05:00
Author
Owner
Copy Link
Copy Source

@kierr commented on GitHub (Oct 8, 2025):

There is also this! #2116

@kierr commented on GitHub (Oct 8, 2025): There is also this! #2116
yindo commented 2026-02-16 17:33:35 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Oct 8, 2025):

yeah it looks like itd be pretty simple to add a config setting or an env var, I will take a look at pr later

@rekram1-node commented on GitHub (Oct 8, 2025): yeah it looks like itd be pretty simple to add a config setting or an env var, I will take a look at pr later
yindo commented 2026-02-16 17:33:35 -05:00
Author
Owner
Copy Link
Copy Source

@adamal commented on GitHub (Jan 24, 2026):

Using OpenCode with gpt-5.2-codex from Azure, I frequently get ratelimit errors and timeouts. In Codex, setting max retries to 100 mostly solves the problem. In OpenCode, I frequently have to say "continue".
Very annoying for unsupervised sessions.

@adamal commented on GitHub (Jan 24, 2026): Using OpenCode with gpt-5.2-codex from Azure, I frequently get ratelimit errors and timeouts. In Codex, setting max retries to 100 mostly solves the problem. In OpenCode, I frequently have to say "continue". Very annoying for unsupervised sessions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1985
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?