Fix Kimi-K2 tool-call parsing issues (help wanted) #17376
Draft
+193
−48
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
4 tasks
hksdpc255
changed the title
4 tasks
|
seems to work. i've been using the copy of this PR in ik_llama.cpp and it solved the problems I was having with Roo Code not working after they hardcoded openai compatible endpoints to use native tool calling instead of XML style |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Kimi-K2 still appears to have issues with tool-call parsing.
However, the model is too large to run on my hardware, even with the most aggressive quantization, so I’m currently unable to reproduce or test the problem myself.
This PR is therefore left as a draft to collect community bug reports and reproduction cases.
I will work on fixing all parser-related issues as soon as actionable information becomes available.
Closes #17155.