Avoid persistent model-change notices when cycling Plan and Default modes

Open 💬 0 comments Opened Jul 11, 2026 by leeyspaul

What variant of Codex are you using?

CLI (codex-cli 0.144.1)

What feature would you like to see?

When using Shift+Tab to cycle between Plan and Default modes, Codex can add persistent bulleted notices to the conversation history:

• Model changed to gpt-5.4 medium for Plan mode.
• Model changed to gpt-5.4 default for Default mode.

Please avoid adding these notices to the transcript when the model or reasoning effort changes automatically as part of a mode switch.

The existing footer already communicates the relevant state: it displays the active model and shows Plan mode (shift+tab to cycle) when Plan mode is active. Returning to the normal footer communicates that Default mode is active. This persistent indicator should be sufficient without adding conversation-history entries.

Expected behavior

Cycling modes should update the existing footer only:

  • Update the active model and reasoning display.
  • Show or hide the Plan-mode indicator as appropriate.
  • Do not add a bulleted information row to conversation history.

Explicit model changes made through the model picker can continue showing their existing confirmation notice. This request is limited to model or reasoning changes caused automatically by cycling collaboration modes.

Additional information

These notices add visual noise and become part of the scrollback even though they describe transient UI state rather than conversation content. Keeping mode state in the footer would make cycling feel cleaner while preserving visibility of the active configuration.

View original on GitHub ↗