Add a keybinding to cycle configured models
What variant of Codex are you using?
CLI
What feature would you like to see?
Add a TUI action and keybinding for cycling through a configured shortlist of models without leaving the current session.
Codex already lets me cycle reasoning effort with Shift+Up and Shift+Down. Model selection is becoming similarly granular: with the 5.6 family, I may want to move frequently between variants such as gpt-5.6-sol, gpt-5.6-terra, and gpt-5.6-luna, depending on the task. Opening /model and navigating the picker every time adds friction.
Ideally, config.toml could define the cycle explicitly, with a configurable keybinding for next/previous model. For example:
[tui.model_cycle]
models = ["gpt-5.6-sol", "gpt-5.6-terra", "gpt-5.6-luna"]
next = "..."
previous = "..."The exact config shape isn't important. The useful behavior is a fast, state-preserving next/previous model action, analogous to reasoning-effort cycling, restricted to models the user actually wants in the rotation.
Additional information
The current workaround is /model, or separate launch profiles with a different model value. Profiles don't help when switching within an active conversation, and the picker is heavier than a dedicated cycle action.
11 Comments
+1 to this. only addition I’d prefer
next_modelandprevious_modelto cycle through the models already available in the current session. Those are currently configurable so don't think an extra config option is necessary.As a temporary solution you can use keystroke macros to achieve this. Simulate
/model+enter+3+2to choose specific model and effort.I used Hammerspoon, but you could use others like Keyboard Maestro or possibly Automator
https://github.com/user-attachments/assets/54d1cf54-8f91-434b-b202-86fb7c02b3fb
macro source code
That's a cool idea @tonisives, but does that solution work even when there is text written in the input?
Keybindings are most useful when I type something and then I realize I need a different model/thinking effort.
Yeah wont work if you have text in the field. This macro just simulates what you would write manually. And it exposes a general model selection inconvenience - you need to delete the input to change the model. I currently manually copy > delete > change model > paste. Not ideal.
For quick model selection we need a native solution with shortcuts or an IPC command to do it with a macro.
yeah, i really need this, i wanna use smtg like Alt+C to change between luna and sol, hope this get worked on
@a3ylf make sure to thumbs up the original issue, that's how they prioritize issues
yeah, I often realize mid-prompt that I'd rather use Luna or Sol for the task.
Being able to switch models with a single shortcut, without opening the model picker or losing the current input, would be a huge improvement.
We all do
They should really consider adding this
I’d like to +1 this request from the perspective of frequent model switching in the CLI.
The current
Shift+Up/Shift+Downshortcut for cycling reasoning effort is exactly the kind of interaction I would like for model switching as well: one keystroke to move to the previous/next model without opening/model.Since
Shift+Up/Shift+Downare already used for reasoning effort, a separate pair such asShift+Left/Shift+Right(or configurable keybindings) would work well.A typical workflow is switching frequently between models such as
gpt-5.6-luna,gpt-5.6-terra, andgpt-5.6-soldepending on task complexity. Opening/modeleach time adds unnecessary friction, while a previous/next model shortcut would make model routing much more practical during an active session.Exactly. I find myself needing to do that all the time. I've resorted to some shell aliases like
c_landc_tfor opening Codex with Luna and Terra, but a keybinding would be so much better UX.