[FEATURE]: call the session.retry hook when the built-in retries run out #54862

Activity

1. opencode-agent commented on Oct 12, 2026

   

   opencode-agentBot

   on Oct 12, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for re-filing this for 2.0, @JoaoBerne. You're asking for the session.retry hook to run when the built-in schedule runs out, with decision: { retry: false } as the default, so a plugin can keep retrying past the 10th retry.

   I checked packages/core/src/session/runner/retry.ts and it works as you describe. When Schedule.recurs(10) is done, policy returns { retry: false } before the hook is called. A plugin can't work around that, so this needs the core change you propose. Maintainers will consider it.

   Related:

   • Configurable retry policy: expose maxRetries / initialDelay / backoffFactor / maxDelay via config #43596: the V1 request for a configurable retry policy (maxRetries etc.)
   • feat: make the session retry policy configurable #44517: your V1 PR
   • feat(plugin): add session retry hook #45999: the PR that added the session.retry hook
   • [FEATURE]: Per-Provider Quota-Aware Auto-Retry with Configurable Reset Schedule #43324: quota-aware auto-retry that waits for the provider's reset time
2. JoaoBerne

   added a commit that references this issue on Oct 12, 2026

   docs: say up front that opencode 2.x does not need this

   ...

   21db0dc
3. akrisfx commented on Oct 16, 2026

   

   akrisfx

   on Oct 16, 2026

   More actions

   very usefull

   ❤️React with ❤️1Reacted by JoaoBerné
4. deanm0000 commented on Nov 4, 2026

   

   deanm0000

   on Nov 4, 2026

   More actions

   A maxRetries config key would do it too, for people who'd rather not write a plugin to change a number, but the hook change is the smaller ask.

   This would be my preference. For reference my use case is using the flex tier on openai and just letting it poll indefinitely. In that same vein I'd like if we could override the backoff timer and just always wait a fixed amount of time. Would that customization mean I have to make a plugin?

   ❤️React with ❤️1Reacted by JoaoBerné
5. JoaoBerne commented on Nov 5, 2026

   

   JoaoBerne

   on Nov 5, 2026

   Author

   More actions

   @deanm0000 For the fixed delay, yes, currently that requires a plugin, but just a small one. The retry hook can replace the delay, and core uses the value you set. Place this in .opencode/plugins/:

   export default {
     id: "fixed-retry-delay",
     async setup(ctx) {
       ctx.session.hook("retry", (event) => {
         if (event.decision.retry) event.decision.delay = 30_000
       })
     },
   }

   I tested this on 2.2.5 with a server that always returns a 500 error: with the delay set to 1s, retries came exactly 1 second apart, then stopped after the 10th attempt. That stop is the part no plugin can change yet, and it's the whole point of this issue.

   A quick update on the pointers above: since #56497, the limit lives in packages/core/src/model-retry.ts (Schedule.recurs(10), line 27). retry.ts still returns { retry: false } (line 38) before calling the hook (line 47), so the diagnosis is unchanged.

   As for the config key, either option works for me. I suggested changing the hook because it's a smaller diff, but the decision is up to the maintainers.