fix(agents): strengthen Claude stream retries - #641
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
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.
Summary
Validation
Note
Low Risk
Localized resilience change in Claude streaming retries with bounded delays; no auth or data-handling changes.
Overview
Claude message streaming now retries transient failures up to three attempts (was effectively two with a single retry), using smarter delays instead of a fixed 1s sleep.
_stream_responseadds_stream_retry_delay: for inlineAPIStatusErrorresponses it prefersRetry-After/Retry-After-Ms(clamped to 0–5s); otherwise it uses full-jitter exponential backoff (1s base, 5s cap). Retry logging reports delay and attemptn/3. Which errors qualify for retry is unchanged.Tests were updated for two backoff sleeps before success, exhaustion after three failures, and header-based delay behavior (including capping long
retry-aftervalues).Reviewed by Cursor Bugbot for commit ca11eb0. Bugbot is set up for automated code reviews on this repo. Configure here.