What would you like to be added?
I would like the ability to perform an inline model override – that is, switch the active model and send a prompt in a single input line, rather than the current two‑step process.
Currently, changing the model requires two separate inputs:
$ /model deepseek-v4-flash
$ <prompt>
I want to do this in one line:
$ /model deepseek-v4-flash <prompt>
Expected behaviour after this single command:
- The model switches to the specified model.
- The remainder of the line () is immediately sent to that model.
- After the response, the model reverts to the previously active default model.
Why is this needed?
This feature reduces friction in everyday model switching:
-
One‑off usage – Currently, using a model once requires 2 steps (/model + prompt) and often a third to switch back. Inline override lets you do it in 1 step and automatically reverts afterward.
-
Less‑used models – Makes specialised models (e.g., DeepSeek, Gemini) instantly accessible without changing your default session model.
-
Overall UX – The two‑step flow breaks momentum. Inline override feels more natural and keeps power users in flow.
Additional context
No response
What would you like to be added?
I would like the ability to perform an inline model override – that is, switch the active model and send a prompt in a single input line, rather than the current two‑step process.
Currently, changing the model requires two separate inputs:
I want to do this in one line:
Expected behaviour after this single command:
Why is this needed?
This feature reduces friction in everyday model switching:
One‑off usage – Currently, using a model once requires 2 steps (/model + prompt) and often a third to switch back. Inline override lets you do it in 1 step and automatically reverts afterward.
Less‑used models – Makes specialised models (e.g., DeepSeek, Gemini) instantly accessible without changing your default session model.
Overall UX – The two‑step flow breaks momentum. Inline override feels more natural and keeps power users in flow.
Additional context
No response