Repository navigation
feat(agent): project wire tool names per model family - #1253
Merged
TheGreatAxios merged 1 commit intoOct 2, 2026
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.
Summary
defaultvsgptprofiles) so model families receive their native tool naming conventions while engine IDs remain unchanged.update_planschema when aliasingmanage_tasksfor thegptprofile.Verification
bun run typecheck,bun run build, andbun test ./srcpass cleanly.src/agent/tool-aliases.test.tsasserts per-family tool profiles, dispatch round-trips, and plan schema translation.Fixes CL-9530