-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Adapt ai
command to use tool use / function calling
#1163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @KernelDeimos can I work on this Issue? |
@KernelDeimos i would like to continue with this issue as well. |
@ntwari-bruce gets first dibs on this for working on #1156, but @Sashank-Singh if you'd like to work with Ntwari on this and he says it's okay then I can assign both of you |
Yes, I would like to work on it too. Thanks @KernelDeimos |
@KernelDeimos yes you can assign both of us |
Thanks for confirming, I've assigned both of you |
Hello @KernelDeimos, I hope you’re doing well. I’ve been testing an implementation where I focused on adding a single command, "mkdir", as a starting point to validate my approach. I wanted your thoughts on it and see if you have suggestions for alternative methods or improvements. I’m currently using the tools I defined in my setup, and I’ve attached the code below for your review. `
` |
This is the tool i used.
|
The schema of each command would be better as metadata on the command itself (for builtin commands at least, external commands would need a different approach but we can consider that to be out of scope for now). Then you should be able to lookup commands and generate a list of tools. It might require exposing the command provider like I did with the shell. |
Uh oh!
There was an error while loading. Please reload this page.
Recently the AI command gained the ability to run commands. If we used the streaming mode of the
puter-chat-completion
driver interface it would be possible to the AI command to take multiple steps and command execution might be slightly more reliable.For more details, refer to this previous issue
The text was updated successfully, but these errors were encountered: