codex - 💡(How to fix) Fix Private live plan file for Plan Mode [1 comments, 2 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#19125Fetched 2026-04-24 06:00:25
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×3commented ×1unlabeled ×1
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

CLI

What feature would you like to see?

This is a summary of my discussion with codex. Inspired by Claude Code feature that I've found very useful when working in plan mode.


Feature Request: Private Live Plan File In Plan Mode

Codex Plan Mode should maintain an up-to-date Markdown copy of the current working plan in a private, untracked agent directory, separate from the repo workspace. The user should be able to open this file in an external editor with auto-refresh while Codex remains in Plan Mode.

Problem

Long plans are hard to read and review in terminal chat. Plan Mode currently blocks file writes, which is correct for repo safety, but it also prevents a useful read-only review workflow.

Proposed Behavior

  • When Plan Mode is active, Codex writes the latest plan draft to a private local path, for example under $CODEX_HOME/plans/ or another agent-owned scratch directory.
  • The file is never inside the repo unless explicitly requested after leaving Plan Mode.
  • Codex shows the file path to the user.
  • Updates happen whenever the plan changes.
  • The file is clearly marked as temporary/private and not authoritative until emitted as <proposed_plan>.
  • No repo-tracked files are changed, so this does not violate Plan Mode’s no-mutation guarantee.

Acceptance Criteria

  • User can open the file in a GUI editor of choice and watch changes live.
  • The file persists for the planning session.
  • It is excluded from git and normal workspace mutation rules.
  • It does not contain secrets unless already present in the plan text.
  • The final <proposed_plan> remains the official handoff artifact.

Additional information

No response

extent analysis

TL;DR

To address the issue of reviewing long plans in terminal chat, consider implementing a feature to write the current plan to a private, untracked file that can be opened in an external editor for live review.

Guidance

  • The proposed behavior suggests writing the plan to a private local path, such as $CODEX_HOME/plans/, to enable live review without modifying repo-tracked files.
  • To verify the feasibility of this approach, check if the Codex CLI has any existing mechanisms for writing temporary files or if there are any security concerns with storing plan drafts in a private directory.
  • Consider implementing a mechanism to clearly mark the temporary file as non-authoritative and exclude it from git and normal workspace mutation rules.
  • Evaluate the acceptance criteria to ensure the proposed solution meets the requirements, including live updates, persistence, and exclusion from git.

Notes

The implementation details of the proposed feature are not provided, and the issue lacks technical specifics about the Codex architecture and existing functionality.

Recommendation

Apply workaround: Implement a private file writing mechanism to enable live review of plans, as this approach seems to address the core issue without requiring significant changes to the existing Codex functionality.

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