fix(coding-agents): bound automatic reflect budget - #3364
Merged
nicoloboschi merged 1 commit intoAug 12, 2026
Merged
Conversation
Contributor
|
👋 Suggestion: PR #3364 (bound automatic reflect budget) and PR #3343 (route repository surveys explicitly) both harden the coding-agents subsystem. Consider combining into a single "coding-agents: budget and routing hardening" PR — both are small, same area, and a unified PR would be easier to review and test. |
nicoloboschi
approved these changes
Aug 12, 2026
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
hindsight_reflectMCP calls on the existing high-budget path.Root cause
The automatic hook requested
budget: highwhile enforcing a hard 25-second deadline. High-budget reflect may perform several LLM/tool iterations and can legitimately exceed that window. In a live comparison against the same self-hosted endpoint, a high-budget reflect took 35.169 seconds, while the equivalent low-budget control completed in 6.580 seconds. Concurrent page refreshes can worsen tail latency, but an idle control also exceeded 25 seconds, so increasing workers or changing the database would not fix the contract mismatch.Validation
--noEmit: passed.No timeout, hook configuration, server, database, provider, dependency, or schema change.