iOS Codex follow-up default ignores desktop “Steer” setting and stays queued

Summary

Even after setting Follow-up behavior to Steer in the Codex desktop app, Codex inside the latest iOS ChatGPT app still defaults follow-up messages to Queue. The iOS app also does not appear to expose a separate default follow-up behavior setting, so there is no way to make mobile Codex default to Steer.

Environment

• Desktop Codex app: 26.519.31651 (3017)
• macOS: Tahoe 26.5
• Device: MacBook Pro 16-inch, Apple M5 Max
• Mobile app: latest iOS ChatGPT app available to me
• Same account / connected Codex session between desktop and iOS

Steps to reproduce

1. Open the Codex desktop app.
2. Go to settings and set Follow-up behavior to Steer.
3. Start or continue a Codex run.
4. Open the same/connected Codex chat from the iOS ChatGPT app.
5. While Codex is running, type a follow-up message from iOS.
6. Observe that the message is treated as queued by default, and the message menu shows “Steer instead”, implying the current default is still Queue.

Expected behavior

The iOS Codex experience should either:

1. Respect/sync the desktop Codex app’s Follow-up behavior = Steer setting for the same account/session, or
2. Provide a separate iOS setting for the default follow-up behavior.

When the user has selected Steer, mobile follow-ups should default to steering the active run instead of being queued.

Actual behavior

The iOS ChatGPT app’s Codex UI continues to default follow-ups to Queue, even though the connected desktop Codex app is configured to Steer. There is also no obvious standalone default setting on iOS to change this behavior.

Impact

This makes the mobile Codex experience inconsistent with the desktop app. It is especially disruptive when trying to correct or steer an active run from iOS, because the message is queued instead of immediately affecting the current run. This can cause delayed corrections, wasted time, and unnecessary extra run steps.

Request

Please fix the follow-up behavior default so that iOS Codex either follows the desktop Codex setting or exposes its own persistent default setting. It would also help if the mobile composer clearly displayed whether the next follow-up will be queued or used to steer the current run.

<img width="1430" height="446" alt="Image" src="https://github.com/user-attachments/assets/9bfa0410-aef9-453c-9d61-4a4f2695f481" />

<img width="941" height="2048" alt="Image" src="https://github.com/user-attachments/assets/4536b5cf-92e2-417a-b910-5e00a38d15fb" />