[CLI] Shift+Down no longer cycles reasoning effort to Ultra

Open 💬 2 comments Opened Jul 13, 2026 by f1nando

What version of Codex CLI is running?

codex-cli 0.144.3

What subscription do you have?

ChatGPT account with Ultra access; the exact tier is not exposed in the CLI.

Which model were you using?

gpt-5.6-sol

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What terminal emulator and version are you using (if applicable)?

Windows Terminal / Windows PowerShell 5.1.26100.8655; no terminal multiplexer.

Codex doctor report

{
  "status": "not available",
  "reason": "codex doctor --json timed out after 60 seconds while the active Codex CLI session was running"
}

What issue are you seeing?

After updating Codex CLI from 0.144.2 to 0.144.3, Shift+Down no longer lets me cycle the reasoning-effort selector all the way to Ultra in the TUI.

Previously, this was a very convenient and fast way to switch reasoning effort without opening /model.

Ultra is still available for gpt-5.6-sol through /model or model_reasoning_effort="ultra", so this appears to be a TUI shortcut/model-picker regression rather than an availability issue.

What steps can reproduce the bug?

  1. Run Codex CLI 0.144.3 in Windows Terminal with PowerShell.
  2. Use model gpt-5.6-sol in an interactive TUI session.
  3. Press Shift+Down to cycle the reasoning-effort selector.
  4. Continue cycling toward the highest reasoning setting.
  5. Observe that the quick selector no longer reaches Ultra as it did in 0.144.2.

Uploaded thread: 019f5d37-957a-7bf0-a3d7-fb73a9193c4d

What is the expected behavior?

Shift+Down should continue cycling through the available reasoning-effort settings, including Max and Ultra, as it did previously. Alternatively, please provide an option that includes Max and Ultra in quick reasoning-effort cycling.

Additional information

The model catalog still advertises Ultra for gpt-5.6-sol, and setting model_reasoning_effort="ultra" is accepted. The regression affects the convenient keyboard workflow rather than access to Ultra itself.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗