codex - 💡(How to fix) Fix Plan mode appears to bind to the next runnable task instead of the queued prompt it was selected for [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18155Fetched 2026-04-17 08:31:59
View on GitHub
Comments
3
Participants
3
Timeline
6
Reactions
0
Author
Timeline (top)
commented ×3labeled ×3
RAW_BUFFERClick to expand / collapse

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

26.409.20454 (1462)

What subscription do you have?

Pro

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

I’m seeing behavior in Codex where plan mode does not appear to stay attached to the specific queued prompt I selected it for.

What steps can reproduce the bug?

Prompt A → executing Prompt B → queued Enable Plan mode Queue Prompt C Prompt A finishes Prompt B starts → runs in Plan mode (unexpected) Disable Plan mode Prompt B finishes Prompt C starts → runs as a normal prompt (not Plan)

What is the expected behavior?

When I queue Prompt C with plan mode enabled, plan mode should apply only to Prompt C, regardless of when it executes

Additional information

No response

extent analysis

TL;DR

The issue can be mitigated by disabling Plan mode after the intended prompt has been queued and before the previous prompt finishes executing.

Guidance

  • The problem seems to be related to the scope of Plan mode, which is not being applied correctly to the queued prompts.
  • To verify the issue, follow the steps provided in the bug report and observe the behavior of Plan mode when switching between prompts.
  • A possible workaround is to disable Plan mode after queuing the desired prompt and before the previous prompt finishes executing, as this seems to reset the mode correctly.
  • Further investigation is needed to determine why Plan mode is being applied to the wrong prompt, potentially involving the queue management logic.

Notes

The provided information does not specify the exact implementation details of Plan mode or the queue management system, making it difficult to provide a definitive fix.

Recommendation

Apply workaround: Disabling Plan mode after queuing the desired prompt seems to be the most straightforward way to mitigate the issue until a more permanent fix can be found.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING