Add retry logic and graceful recovery to research loop#116
Merged
Conversation
API errors (500, overloaded) now trigger up to 3 retries with exponential backoff (30s/60s/90s). If all retries fail, the iteration is skipped without counting against the max. When an iteration completes but has no handoff signal (partial crash), the loop continues with the same persona and injects context about the failure into the handoff file so the next iteration knows to check git status and resume rather than redo work. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
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
1 participant
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
MAX_ITERATIONS— the loop skips and continuesHANDOFF.mdso the next iteration knows to check git status and resumeTest plan
"type":"api_error"🤖 Generated with Claude Code