Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

The following comment was made by an LLM, it may be inaccurate:

Based on my search, I found several related PRs that address retry logic, though none appear to be direct duplicates of PR #18443:

Related PRs (not duplicates):

1. PR feat(session): add opt-in retry delegation for plugin-controlled fallbacks #17507 - feat(session): add opt-in retry delegation for plugin-controlled fallbacks - addresses retry mechanism
2. PR feat: Enhance rate limit error retry for some providers #15858 - feat: Enhance rate limit error retry for some providers - specifically about rate limit retry handling
3. PR fix: retry on AI_TypeValidationError from provider 5xx responses #16228 - fix: retry on AI_TypeValidationError from provider 5xx responses - retry behavior for specific errors
4. PR fix: retry on timeout errors instead of failing #13502 - fix: retry on timeout errors instead of failing - general retry improvements

No duplicate PRs found

Please provide a bit more info, what providers are u hitting this error with? When does a 429 set isRetryable to false?

Thanks for updating your PR! It now meets our contributing guidelines. 👍

Good question.

We’re seeing this on OpenAI-compatible/proxy paths (including OpenRouter-style setups). In those paths, a transient 429 can still be tagged with isRetryable=false, so the run stops even though retrying would usually recover.

This PR only changes that case: 429s that look transient are retried; hard quota failures are still treated as terminal (insufficient_quota, usage_not_included, free-usage exhaustion).

Rebased on upstream/dev (HEAD: 1256228). CI re-running.

Already on upstream/dev. HEAD: 1256228

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.