From 856ca2d6b1e5827a19e45b933c0ac425edb516ba Mon Sep 17 00:00:00 2001 From: Richard Palethorpe Date: Wed, 28 Jan 2026 13:44:29 +0000 Subject: [PATCH] fix(qwen3): Be explicit with function calling format (#8265) Qwen3 4b was using the wrong function format (i.e. using "function" instead of "name") within the realtime API. If we specify the function calling format explicitly then it stops it. Signed-off-by: Richard Palethorpe --- gallery/qwen3.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gallery/qwen3.yaml b/gallery/qwen3.yaml index a6f771348..455d2765b 100644 --- a/gallery/qwen3.yaml +++ b/gallery/qwen3.yaml @@ -25,9 +25,9 @@ config_file: | <|im_start|>system You are a function calling AI model. You are provided with functions to execute. You may call one or more functions to assist with the user query. Don't make assumptions about what values to plug into functions. Here are the available tools: {{range .Functions}} - {'type': 'function', 'function': {'name': '{{.Name}}', 'description': '{{.Description}}', 'parameters': {{toJson .Parameters}} }} + {"type": "function", "function": {"name": "{{.Name}}", "description": "{{.Description}}", "parameters": {{toJson .Parameters}} }} {{end}} - For each function call return a json object with function name and arguments + For each function call return a json object with function name and arguments: {"name": , "arguments": } <|im_end|> {{.Input -}} <|im_start|>assistant