fix(agentic): report exhausted responses clearly - #188
Open
OllieinCanada wants to merge 1 commit into
Open
Conversation
Signed-off-by: Oliver Slapinski <olliefromcanada@gmail.com>
OllieinCanada
marked this pull request as ready for review
August 16, 2026 23:07
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
Prevent exhausted WTI analyst runs from surfacing as misleading JSON parse
failures, and give the code-execution preset enough response headroom to finish
tool work and return its structured forecast.
Type of Change
Changes Made
AgentPredictorreceives an empty responseTesting
ruff checkon all changed Python files)Manual testing details:
Both regressions were first run against the original implementation and failed:
the empty response leaked
JSONDecodeError, and the WTI preset returned 16,384.The same focused tests pass after the fix. No model, API, or external service was
used.
Related Issues
Fixes #180
Deployment Notes
No migration or deployment change is required.
Checklist