Before submitting your bug report
Relevant environment info
- OS: Linux
- Continue version: 2.0.0
- IDE version: VSCode 1.135.0
- Model: Qwen3.6-35B-A3B, Aliased as "Coder" (both tested)
- config:
models:
- name: Cerval Coder Thinking
provider: llama.cpp
model: Coder
apiBase: https://<llama-server>
roles:
- chat
- edit
- apply
defaultCompletionOptions:
reasoning: true
reasoningBudgetTokens: 2048
- name: Cerval Coder Quick
provider: llama.cpp
model: Coder
apiBase: https://<llama-server>
roles:
- chat
- edit
- apply
defaultCompletionOptions:
reasoning: false
requestOptions:
extraBodyProperties:
reasoning_budget: 0
Description
The OpenAI provider pipeline in the VS Code extension automatically intercepts the model name and injects reasoning parameters/wrappers into the payload under the hood. If a user sets up a local llama-server instance where reasoning/thinking is explicitly turned off globally, and adds directive in config.yaml to disable thinking in the request payload, Continue overrides this behavior, perhaps because it detects the string "Qwen" or "DeepSeek" in the models configuration.
Setting defaultCompletionOptions: { reasoning: false } is completely ignored.
To reproduce
- Run a local
llama-server with --alias "Coder,Qwen3.6-35B" and thinking disabled.
- Verify via raw
curl that the endpoint returns clean text with NO reasoning fields or tags.
- Configure
config.yaml to use provider: openai, model: Coder, and reasoning: false as illustrated below.
- Observe that the model responds with blocks despite user directive to explicitly disable thinking.
Log output
{
"reasoning": false,
"model": "Qwen3.6-35B",
"maxTokens": 4096
}
<think>
Here's a thinking process:
1. **Analyze User Input:** ...
*** Output from curl http://llama-server/models
{
"models": [
{
"name": "Coder",
"model": "Coder",
"modified_at": "",
"size": "",
"digest": "",
"type": "model",
"description": "",
"tags": [
""
],
"capabilities": [
"completion",
"multimodal"
],
"parameters": "",
"details": {
"parent_model": "",
"format": "gguf",
"family": "",
"families": [
""
],
"parameter_size": "",
"quantization_level": ""
}
}
],
"object": "list",
"data": [
{
"id": "Coder",
"aliases": [
"Coder",
"Qwen3.6-35B"
],
"tags": [],
"object": "model",
"created": 1788340597,
"owned_by": "llamacpp",
"meta": {
...
}
}
]
}
Before submitting your bug report
Relevant environment info
Description
The OpenAI provider pipeline in the VS Code extension automatically intercepts the model name and injects reasoning parameters/wrappers into the payload under the hood. If a user sets up a local
llama-serverinstance where reasoning/thinking is explicitly turned off globally, and adds directive in config.yaml to disable thinking in the request payload, Continue overrides this behavior, perhaps because it detects the string "Qwen" or "DeepSeek" in the models configuration.Setting
defaultCompletionOptions: { reasoning: false }is completely ignored.To reproduce
llama-serverwith--alias "Coder,Qwen3.6-35B"and thinking disabled.curlthat the endpoint returns clean text with NO reasoning fields or tags.config.yamlto useprovider: openai,model: Coder, andreasoning: falseas illustrated below.Log output
{ "reasoning": false, "model": "Qwen3.6-35B", "maxTokens": 4096 } <think> Here's a thinking process: 1. **Analyze User Input:** ...*** Output from
curl http://llama-server/models{ "models": [ { "name": "Coder", "model": "Coder", "modified_at": "", "size": "", "digest": "", "type": "model", "description": "", "tags": [ "" ], "capabilities": [ "completion", "multimodal" ], "parameters": "", "details": { "parent_model": "", "format": "gguf", "family": "", "families": [ "" ], "parameter_size": "", "quantization_level": "" } } ], "object": "list", "data": [ { "id": "Coder", "aliases": [ "Coder", "Qwen3.6-35B" ], "tags": [], "object": "model", "created": 1788340597, "owned_by": "llamacpp", "meta": { ... } } ] }