Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Feature Request: Allow configuring default action for “Implement this plan?” (prefer staying in Plan mode) [1 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#19752•Fetched 2026-04-28 06:37:45
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
PBK-BPBK-B
Participants
PBK-BPBK-B
Timeline (top)
labeled ×3unlabeled ×1

In Plan Mode, Codex prompts:

"Implement this plan?"

Currently, the default action is effectively "Yes" (execute/implement) when pressing Enter.

I would like the ability to configure the default behavior to:

"No, stay in Plan mode"

Root Cause

In Plan Mode, Codex prompts:

"Implement this plan?"

Currently, the default action is effectively "Yes" (execute/implement) when pressing Enter.

I would like the ability to configure the default behavior to:

"No, stay in Plan mode"

Code Example

plan_confirmation_default = "stay"

---

CODEX_PLAN_DEFAULT=stay
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

CLI

What feature would you like to see?

Summary

In Plan Mode, Codex prompts:

"Implement this plan?"

Currently, the default action is effectively "Yes" (execute/implement) when pressing Enter.

I would like the ability to configure the default behavior to:

"No, stay in Plan mode"

Problem

When iterating on a plan, it's easy to accidentally press Enter and trigger execution prematurely.

This leads to:

  • Unintended code changes
  • Interrupted planning workflow
  • Extra overhead reverting or stopping execution

For users who primarily use Plan Mode for iterative design, the current default is risky.

Expected Behavior

Provide a way to configure the default selection for the confirmation prompt.

For example:

  • Default = "Implement" (current behavior)
  • Default = "Stay in Plan mode" (requested)

Proposed Solutions

Any of the following would solve the issue:

  1. Config option (preferred)

    plan_confirmation_default = "stay"

  2. CLI flag / environment variable

    CODEX_PLAN_DEFAULT=stay

  3. Keybinding behavior change

    • Enter = stay in plan
    • Ctrl+Enter = implement

  4. Optional: remember last choice per session

Alternatives Considered

  • Using prompts like "do not implement" → not reliable
  • Avoiding Plan Mode → loses structured planning workflow
  • Hooks → cannot intercept or modify this UI behavior

Additional Context

This feature would improve safety and usability for users who:

  • Iteratively refine plans
  • Prefer explicit execution triggers
  • Work on large or sensitive codebases

Impact

Low complexity, high UX improvement:

  • Reduces accidental execution
  • Aligns with "safe by default" workflows
  • Makes Plan Mode more practical for real-world usage

Thanks for considering this!

Related requests

https://community.openai.com/t/feature-request-plan-mode-add-an-optional-message-box-when-confirming-plan-execute-in-codex-vs-code/1374051/2?utm_source=chatgpt.com

Additional information

No response

extent analysis

TL;DR

To address the issue, consider introducing a configuration option to set the default behavior for the "Implement this plan?" prompt in Plan Mode to "No, stay in Plan mode".

Guidance

  • Introduce a config option, such as plan_confirmation_default = "stay" in a TOML file, to allow users to set their preferred default behavior.
  • Alternatively, consider adding a CLI flag or environment variable, like CODEX_PLAN_DEFAULT=stay, to provide flexibility in setting the default.
  • Evaluate the feasibility of changing the keybinding behavior, where Enter stays in plan mode and Ctrl+Enter implements the plan, as a potential solution.
  • Assess the value of remembering the last choice per session as an optional feature to enhance user experience.

Example

plan_confirmation_default = "stay"

This example illustrates how a config option could be implemented to set the default behavior to "stay in Plan mode".

Notes

The proposed solutions aim to provide a way to configure the default selection for the confirmation prompt, addressing the issue of accidental execution in Plan Mode. The choice of solution depends on the specific requirements and constraints of the Codex application.

Recommendation

Apply a workaround by introducing a config option, as it provides a flexible and user-friendly way to set the default behavior, aligning with the "safe by default" principle.

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…
#environment variable#search optimization#API routing#API middleware#SSR setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING