Add a persistent “Steer by default” toggle for mid-run messages

What variant of Codex are you using?

Codex App (Desktop)

What feature would you like to see?

Problem

When a message is submitted while Codex is working, it enters the follow-up queue. The queued-message chip then provides a Steer action that promotes that individual message into the active run.

For users who usually intend mid-run messages to refine or correct the active task, manually promoting every queued message adds unnecessary friction and makes it easy for an intended correction to remain queued as later work.

Proposed behavior

Add a persistent two-state delivery mode:

• Steer by default: Messages submitted during an active run steer it automatically instead of first entering the follow-up queue.
• Queue as follow-up: Preserve the current behavior. Each queued message can still be individually promoted using its Steer action.

The selected mode should persist for at least the current task. Ideally, Settings would also let users make Steer by default their global preference.

The composer should clearly indicate where the next message will go, for example:

• "Steer the active run…"
• "Queue a follow-up…"

The existing per-message Steer action should remain available as an escape hatch when queue-as-follow-up mode is selected.

Expected result

Users who frequently guide work in progress can leave steering enabled instead of manually promoting each queued message, while users who prefer to queue later work retain the current workflow.

Additional information

Suggested scope

A useful progression would be:

1. Remember the mode for the current task.
2. Optionally support a global default in Settings → Agent behavior → Steer mid-run messages by default.
3. Keep the existing one-message promotion action regardless of the selected default.

Accessibility

• The toggle should have an unambiguous on/off state that does not rely on color alone.
• The composer should explain whether the next message will steer or wait.
• Keyboard users should be able to change the mode.
• Screen readers should announce the current mode and mode changes.

Comparable interfaces

Pi and OpenCode route mid-run interaction through their normal prompt editors without requiring users to promote each message from a separate queued-message control. Their execution semantics differ, but they demonstrate that mid-run delivery can be treated as an input policy.

• Pi settings: https://github.com/badlogic/pi-mono/blob/main/packages/coding-agent/docs/settings.md
• Pi SDK steering behavior: https://github.com/badlogic/pi-mono/blob/main/packages/coding-agent/docs/sdk.md
• OpenCode TUI: https://opencode.ai/docs/tui/

Related issues searched

I searched for "Steer button", steer hide, steer toggle, and "steering" "button". I found issues about steering behavior or button interaction—including #20935, #11060, and #11062—but none requesting a persistent default delivery mode.