Merged
Conversation
## Summary - Extract retry-after header from 429 API errors and include timing guidance in the user-facing error message - Previously, non-quota 429 errors showed a generic message with no guidance on when to retry, only a link to status.anthropic.com ## Impact - user-facing impact: 429 error messages now tell users when to retry instead of just linking to a status page - developer/maintainer impact: none ## Testing - [x] `bun run build` - [ ] `bun run smoke` - [ ] focused tests: error formatting is pure string construction, verified via build + manual inspection ## Notes - provider/model path tested: applies to all providers returning 429 - screenshots attached (if UI changed): n/a - follow-up work or known limitations: 529 errors could get similar treatment in a follow-up https://claude.ai/code/session_01D7kprMn4c66a5WrZscF7rv
kevincodex1
approved these changes
Apr 4, 2026
Contributor
kevincodex1
left a comment
kevincodex1
left a comment
There was a problem hiding this comment.
nice! this is looks great
gnanam1990
approved these changes
Apr 5, 2026
euxaristia
pushed a commit
to euxaristia/openclaude
that referenced
this pull request
Apr 13, 2026
## Summary - Extract retry-after header from 429 API errors and include timing guidance in the user-facing error message - Previously, non-quota 429 errors showed a generic message with no guidance on when to retry, only a link to status.anthropic.com ## Impact - user-facing impact: 429 error messages now tell users when to retry instead of just linking to a status page - developer/maintainer impact: none ## Testing - [x] `bun run build` - [ ] `bun run smoke` - [ ] focused tests: error formatting is pure string construction, verified via build + manual inspection ## Notes - provider/model path tested: applies to all providers returning 429 - screenshots attached (if UI changed): n/a - follow-up work or known limitations: 529 errors could get similar treatment in a follow-up https://claude.ai/code/session_01D7kprMn4c66a5WrZscF7rv Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix: include retry timing in 429 error messages
Summary
guidance in the user-facing error message
guidance on when to retry, only a link to status.anthropic.com
Impact
instead of just linking to a status page
Testing
bun run buildbun run smokeverified via build + manual inspection
Notes
treatment in a follow-up