What happened?
In the VSCode extension, when I switch the model in an existing chat pane (e.g., to glm-5) and then create a new chat pane, the new pane does not use the same model. Instead, it defaults back to the default model (e.g., qwen3.5-plus).
What did you expect to happen?
When creating a new chat pane, it should inherit the model selection from the existing/active chat pane, so that I can continue using the same model without having to manually switch it again.
Client information
Client Information
Run qwen to enter the interactive CLI, then run the /about command.
$ qwen /about
# paste output here
Login information
API Config
Anything else we need to know?
This makes it inconvenient when working with non-default models, as every new chat pane requires manually switching the model again. The expected behavior would be for the model selection to persist across new chat panes within the same VSCode session.
What happened?
In the VSCode extension, when I switch the model in an existing chat pane (e.g., to
glm-5) and then create a new chat pane, the new pane does not use the same model. Instead, it defaults back to the default model (e.g.,qwen3.5-plus).What did you expect to happen?
When creating a new chat pane, it should inherit the model selection from the existing/active chat pane, so that I can continue using the same model without having to manually switch it again.
Client information
Client Information
Run
qwento enter the interactive CLI, then run the/aboutcommand.Login information
API Config
Anything else we need to know?
This makes it inconvenient when working with non-default models, as every new chat pane requires manually switching the model again. The expected behavior would be for the model selection to persist across new chat panes within the same VSCode session.