Repository navigation
Conversation
This branch has not been deployed
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.
Summary
Qwen tool rendering and parsing landed in #1794, but the
qwen36family still publishescapabilities.tools=false. Clients using the public metadata can therefore disable tools even though the gateway supports them.Set only that capability flag and add a regression test against
public_metadata. No engine, parser, template, or other capability changes.Validation
env -u OMP_NUM_THREADS make -C c -j4 check: clean portable CPU build and C tests passed; 2,402 Python tests ran, 305 skipped, no failures.git diff --checkpassed.88f25a60.Compatibility
Related: #1794 (implemented tool calling); this corrects its remaining registry metadata mismatch.