feat(agent): bound agent builder retries and improve chat scrolling - #89
Merged
Conversation
ripgrim
marked this pull request as ready for review
August 7, 2026 20:42
github-actions
Bot
changed the title
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 14 files
Tip: instead of fixing issues one by one fix them all with cubic
Re-trigger cubic
github-actions
Bot
changed the title
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
Improve private agent chat scrolling and prevent agent-builder failures from turning into runaway retries.
Problem
The builder chat used ordinary overflow scrolling, so streamed responses did not reliably follow the reader's intent. Separately, a model structured-output miss could cause the parent to delegate again, guess invalid resource contracts, continue editing after a successful save, and eventually exhaust the session token budget.
Solution
Adopt the shared message-scroller behavior with stable turn anchors, saved-thread positioning, and a jump-to-latest control. Move clarification into the builder specialist's durable Eve question flow, enforce one delegation per creation turn, canonicalize integration inputs, lock the draft after save, and cap tool calls, save attempts, and session tokens.