fix: honor built-in tool contracts - #181
Merged
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
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.
Problem
The model-facing read schema advertises line ranges, but the executor ignored them. Large tool results explicitly tell the Agent to use that range, so the recovery path was not actually closed. The bash schema also advertised restart even though Mango runs independent sandbox commands and has no persistent shell to restart.
Changes
Acceptance criteria
Non-goals
This does not add a persistent shell, change the public HTTP API, or reuse a host-side SDK executor outside the Mango sandbox abstraction.
Verification