Closed
Conversation
- register shell as a compatibility alias for bash in plugin tool hooks\n- keep existing bash behavior unchanged\n- add unit coverage asserting shell tool registration
Owner
|
Hey mate. You are a legend I did see the I’ve addressed the remaining intent directly on Closing as superseded by the current tool-loop/provider-boundary direction. |
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.
Fixes #16
What
shellmaps to the same handler/schema asbash.bashbehavior unchanged.shellis registered in plugin hooks.Why
Some tool/subagent flows emit
shellinstead ofbash.Without this alias, those calls fail with:
Model tried to call unavailable tool 'shell'This change makes tool-call interception more robust across agent variants.
Validation
bun test tests/unit/plugin-tools-hook.test.tsbun run test:ci:unitbun run test:ci:integration