Codex App: Queue applies follow-ups after an intermediate turn instead of waiting for task completion

What version of the Codex App are you using (From “About Codex” dialog)?

26.707.30751 (5018)

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

With Settings → General → Follow-up behavior set to Queue, queued follow-up prompts are sometimes released after an intermediate internal agent turn, while the original task is still in progress.

The agent has not reached its final completion state or delivered its final result, but the queued prompt is applied anyway. This can change direction or start dependent work before the original task is finished.

Earlier Codex App versions treated Queue as task-level sequencing: prompts waited until the agent had fully completed the task. That behavior is essential for workflows where I queue dependent instructions while the agent works autonomously.

The current behavior makes Queue unreliable for that purpose. “Queue” appears to mean “next internal turn” rather than “after the task completes,” but that distinction is neither sufficient for dependent workflows nor clear in the UI.

What steps can reproduce the bug?

1. Open Codex App.
2. Go to Settings → General → Follow-up behavior and select Queue.
3. Start a task complex enough to require multiple internal turns or continued autonomous work.
4. While the task is still running, queue a dependent follow-up such as:

> After fully completing the current task and its verification, do [next task].

1. Wait for Codex to reach an intermediate turn boundary.
2. Observe that the queued follow-up is applied even though the original task is still in progress and Codex has not produced its final completion response.

This does not happen predictably on every task, but it happens often enough to break queue-based workflows.

What is the expected behavior?

Queue should preserve task-level sequencing:

• A queued follow-up must not be applied until the original task or goal reaches its final completed state.
• Intermediate model or agent-turn boundaries must not release queued prompts.
• If Codex supports both behaviors, the UI should offer an explicit choice:
• Queue for next turn
• Queue until task completion
• The previous task-completion queue behavior should be restored or made available as the default/option.

Additional information

This is a workflow regression, not a request to make steering faster.

I rely on Queue to prepare a chain of dependent prompts while Codex works in the background. If a follow-up is released early, it can interrupt, redirect, or prematurely start work that depends on the original task being complete and verified.

I can provide a screen recording, timestamps, task/thread details, and redacted example prompts if useful.