Draft: Add user tool discovery#2
Draft
screenfluent wants to merge 1 commit into
Draft
Conversation
Owner
|
This is a great idea, I wanted to implement something like this too, sorry, I've only noticed the PR now, but I've actually added a global config dir, that'll be the place where the tools go |
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.
Draft proposal for user-level tools.
I’d like to make it possible to keep personal tools while still updating mi from upstream. This explores
~/.agents/tools/*.mjs, mirroring the existing user-level skills directory.This draft:
tools/*.mjsplus user~/.agents/tools/*.mjs{ name, description, parameters, handler }contractnpm run linesat 30 totalMain question: does this direction and path feel right for mi, or would you prefer a different shape?
Checks: