fix(agent): implement exponential backoff retry in loop - #32
Merged
Conversation
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.
This PR resolves BUG-002 from the v2 roadmap by implementing an exponential backoff retry mechanism inside the agent's main execution loop.
Key Changes:
internal/agent/loop.goto wrap thea.provider.Stream()call in a retry loop.ctx.Err()), the retry loop immediately breaks to prevent unkillable processes.todo/11_BUGFIXES.mdto check off BUG-001 (previously fixed in PR feat(memory): implement token-aware sliding window memory management #28), BUG-002, and BUG-003.