What version of the Codex App are you using (From “About Codex” dialog)?
26.730.61639
What subscription do you have?
Plus
What platform is your computer?
macOS 15.7.7
What issue are you seeing?
Description
After Codex generated an implementation plan, I disabled Plan mode in the desktop UI and asked it to execute the approved plan. However, Codex continued to report that it was still in Plan mode and refused to modify the repository.
The UI indicated that Plan mode was disabled, but the task could not proceed to execution.
Steps to reproduce
- Open a repository task in the Codex desktop app.
- Enable Plan mode.
- Ask Codex to analyze the task and generate an implementation plan.
- Disable Plan mode in the UI.
- Send a message such as “Execute the approved plan.”
- Observe that Codex continues to report that it is in Plan mode and does not modify files.
Expected behavior
After Plan mode is disabled, Codex should execute the approved plan in the same task and be able to modify the repository.
Actual behavior
Codex continues to behave as if Plan mode is active and refuses to execute the plan. Reopening the task did not resolve the issue.
This resulted in multiple additional turns and consumed Codex usage without producing the requested code changes.
Environment
- Codex App version: 26.730.61639
- macOS version: 15.7.7
- Subscription: [Free / Plus / Pro / Business]
What steps can reproduce the bug?
- Open a repository task in the Codex desktop app.
- Enable Plan mode.
- Ask Codex to analyze the task and generate an implementation plan.
- Disable Plan mode in the UI.
- Send a message such as “Execute the approved plan.”
- Codex continues to report that it is in Plan mode and refuses to modify files.
- Close and reopen the task, then repeat step 5. The issue still occurs.
What is the expected behavior?
After Plan mode is disabled, Codex should switch the current task to execution mode. It should execute the approved plan in the same task and be able to modify the repository.
The task should not remain stuck in Plan mode after the UI indicates that Plan mode has been disabled.
Additional information
The issue caused several additional turns and consumed Codex usage without producing the requested code changes.
Codex App version: 26.730.61639
macOS version: 15.7.7
Task ID: 01a03d3d-cc0d-7ae2-8166-234b02117331
The issue may be related to the potential duplicate shown by GitHub (#40444), but the behavior described above is reproducible in this task.
What version of the Codex App are you using (From “About Codex” dialog)?
26.730.61639
What subscription do you have?
Plus
What platform is your computer?
macOS 15.7.7
What issue are you seeing?
Description
After Codex generated an implementation plan, I disabled Plan mode in the desktop UI and asked it to execute the approved plan. However, Codex continued to report that it was still in Plan mode and refused to modify the repository.
The UI indicated that Plan mode was disabled, but the task could not proceed to execution.
Steps to reproduce
Expected behavior
After Plan mode is disabled, Codex should execute the approved plan in the same task and be able to modify the repository.
Actual behavior
Codex continues to behave as if Plan mode is active and refuses to execute the plan. Reopening the task did not resolve the issue.
This resulted in multiple additional turns and consumed Codex usage without producing the requested code changes.
Environment
What steps can reproduce the bug?
What is the expected behavior?
After Plan mode is disabled, Codex should switch the current task to execution mode. It should execute the approved plan in the same task and be able to modify the repository.
The task should not remain stuck in Plan mode after the UI indicates that Plan mode has been disabled.
Additional information
The issue caused several additional turns and consumed Codex usage without producing the requested code changes.
Codex App version: 26.730.61639
macOS version: 15.7.7
Task ID: 01a03d3d-cc0d-7ae2-8166-234b02117331
The issue may be related to the potential duplicate shown by GitHub (#40444), but the behavior described above is reproducible in this task.