-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Native Tool Call #2866
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
Native Tool Call #2866
Conversation
- Implemented tool call support across various tools, enabling the use of tool calls instead of XML-based prompts. - Updated `attemptCompletionTool` to handle tool results with `toolUseId`. - Enhanced `applyDiffTool` to process diffs with tool calls, including handling search and replace scenarios. - Modified `listFilesTool`, `searchFilesTool`, and `writeToFileTool` to accommodate tool call configurations. - Introduced `ToolCallSettingsControl` in the UI for enabling/disabling tool calls. - Added localization for tool call settings in multiple languages. - Updated tests to cover new tool call functionalities and ensure proper behavior when tool calls are enabled.
|
…s with optional mode
…f undefined values
# Conflicts: # src/api/providers/openai.ts
The alternative PR #2833 is merged, but we can keep this one open a while for improvement ideas. |
I'm happy to see Kilo introduce experimental native tool calls. I think my pull request can be closed, but the current draft still needs the following enhancements:
Hope with the continuous feedback from the community, this function will become more and more perfect. |
Absolutely, thanks for your support @NaccOll |
Context
Use native tool calls instead of XML
Implementation
Without major refactoring of the existing workflow, the tool call based on XML-formatted text prompts was converted to tool call based on json.
Tools
Provider
Screenshots
How to Test
Configure the model in the supported provider and enable native tool calls for testing based on the screenshots.
Get in Touch
NaccOll