[FEATURE] Config setting for plans save directory
What feature would you like to see?
A configuration setting (e.g. plansDirectory) that lets users specify where Codex writes plan files.
Problem: Currently there's no way to control where plans are saved. Users may want to:
- Keep plans in the project directory (e.g.
.codex/plans/) for easy reference or version control - Separate plans from the default location for organizational purposes
- Gitignore project-local plans while still having them colocated with code
Proposed behavior:
A plansDirectory setting in codex.json (or equivalent config) that accepts a relative or absolute path:
{
"plansDirectory": ".codex/plans"
}Relative paths would resolve from the project root. An absolute path would be used as-is.
Additional information
Claude Code (Anthropic's CLI) ships a plansDirectory setting in its settings.json that does exactly this. It's a small but useful quality-of-life feature for developers who want plans colocated with their codebase.
Related: #10486 (export plan to Markdown) — complementary features; a configurable save directory would make exported plans easier to organize.
8 Comments
This would be a nice addition, I appreciate the new
/copycommand too for nowany update on this?
Would like this feature too. I'm currently just copying and manually saving them in a
.codex/plans/directory thats project specific that is git ignored. But having it a config option that lets you specify the projects codex plan or ~/.codex/plan would be idealWould really like this feature to, plans persistence is really importent and should come out of the box.
Claude code just saves the plan under .claude/plans it will really useful to have a similart thing
Have you tried simply asking the agent to write the plan to a specific directory? You could also create a skill if you do this frequently. It's not clear that a built-in mechanism is the best approach here because each user may have somewhat different preferences in terms of how the plan is written (format, etc.), where it's written (e.g. folder hierarchy), etc.
I think the understanding is that the built-in
plan modeshould save the final plan to disk beforeImplement the planis selected - as is. In practice even if you ask Codex to 'save plan to disk' it doesn't do this when its within plan mode (as it's read-only) and there's no way to add a final comment / instruction when acceptingImplement this plan- one cannot even/copythe plan at that point without hitting escape and interrupting it.Other than helping codex stay on course (in between context compressions), saving the plan to disk would be super helpful when you're simply keeping track / archive of recently implemented plans.
I second what @guidedways said.
Also:
This is obnoxious in practice and obvious to anyone on these boards. A PLAN needs to be durable so that said PLAN may be executed fully. Otherwise, why not add some explanatory text in the UI?
"Plan Mode - Create a plan your agent will plan to execute, but likely forget about entirely."
Just a bad feature copy from Claude. I see a pattern here.