Add Queue and Steer controls to Codex mobile

What version of Codex CLI is running?

5.5

What subscription do you have?

pro

Which model were you using?

_No response_

What platform is your computer?

_No response_

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

_No response_

Codex doctor report

What issue are you seeing?

Feature request

Please add Queue / Steer controls to Codex mobile, matching the workflow available in the Codex CLI / IDE extension.

Context

Feedback thread ID: 019e906f-d791-7be1-b128-6c0c9add09c6

On desktop/CLI/IDE, it is very useful to distinguish between:

• Steer current task: add an instruction to the currently running turn
• Queue next task: schedule an instruction to run after the current task finishes

On mobile, the same distinction is important because users often check Codex progress away from their PC and want to add follow-up work without accidentally disturbing the currently running task.

Requested behavior

1. While Codex is running, mobile should let the user choose one of the following before sending a message:

• Steer current task: add the instruction to the currently running turn
• Queue next task: run the instruction after the current task completes

1. Mobile should show a visible task queue with basic operations:

• view queued prompts
• reorder queued prompts
• edit queued prompts
• delete queued prompts
• pause / resume the queue

1. The UI should clearly indicate whether the next message will steer the current task or be queued for the next turn.

Expected benefit

This would make mobile Codex closer to the IDE extension workflow, improve local-to-cloud/mobile handoff, and reduce mistakes where a follow-up instruction accidentally steers the current task when the user intended to queue it for later.

What steps can reproduce the bug?

Uploaded thread: 019e906f-d791-7be1-b128-6c0c9add09c6

What is the expected behavior?

Mobile Codex should provide the same Queue / Steer distinction available in the CLI / IDE workflow.

Expected behavior:

1. While Codex is running, mobile should let the user choose before sending a message:

• Steer current task: add the instruction to the currently running turn
• Queue next task: run the instruction after the current task completes

1. Mobile should show a visible task queue with basic operations:

• view queued prompts
• reorder queued prompts
• edit queued prompts
• delete queued prompts
• pause / resume the queue

1. The UI should clearly indicate whether the next message will steer the current task or be queued for the next turn.

This is important because mobile users often check Codex progress away from their PC and want to add follow-up work without accidentally disturbing the currently running task.

Additional information

Feedback thread ID: 019e906f-d791-7be1-b128-6c0c9add09c6

This would make mobile Codex closer to the IDE extension workflow, improve local-to-cloud/mobile handoff, and reduce mistakes where a follow-up instruction accidentally steers the current task when the user intended to queue it for later.