[MODEL] Claude Code will override an existing `~/.claude/plans/` plan markdown file, rather than creating a new file

[SeanHollen]

Preflight Checklist

• I have searched existing issues for similar behavior reports
• This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Claude modified files I didn't ask it to modify

What You Asked Claude to Do

Plan files, once created, should not be edited unless the user explicitly asks for it. Plan files are a historical record of plans which have been requested in the past.

No matter what I try, I cannot get Claude to create a new plan file, rather, it always overrides the existing plan file.

• Putting this requirement explicitly in the CLAUDE.md or a README.md does not help
• Creating a claude rule does not help
• Telling it do otherwise does not help

At this point, I am out of options.

What Claude Actually Did

If you make 2 plans within the same session, then claude will attempt to read the plan that it wrote earlier in the session, and when it realizes that that plan is out of date, it will DELETE that plan, overriding the file contents in favor of a new plan. Not only does this pollute the context with an irrelevant plan, but it deletes history.

Expected Behavior

When entering plan mode, the agent should only be allowed to write to new plan files. It should be given the name of a designated plan file to create, which should not match the name of any of the plan files which exited earlier in the session. If it sees any earlier plan files, it should only be because the user explicitly requested for Claude to read them.

Files Affected

Anything in ~/.claude/plans/

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, almost every time I make a plan

Steps to Reproduce

Enter plan mode twice within the same session, and request it to write a plan

Claude Model

Opus 4.5

Impact

Critical - Data loss or corrupted project

Claude Code Version

2.1.19 (Claude Code)

Platform

Anthropic API

Additional Context

No response

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Claude clobbers/overwrites old plan files, rather than creating new #18258
2. [Bug] Plan mode resurfaces old plans after session compaction with Claude 4.5 Opus #12505
3. [Bug] Plan mode reuses previous plan instead of generating new plan per session #12827

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[SeanHollen]

Found 3 possible duplicate issues:

1. [BUG] Claude clobbers/overwrites old plan files, rather than creating new #18258
2. [Bug] Plan mode resurfaces old plans after session compaction with Claude 4.5 Opus #12505
3. [Bug] Plan mode reuses previous plan instead of generating new plan per session #12827

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

#2 is somewhat similar, however I simply don't want CC to override the older plan.

[phatmandrake]

I've lost a lot of time to plan merging. I'd love it to just use a versioned plan.

[SeanHollen]

So I got claude to write my plans to an unrelated file with particularly strong language in the CLAUDE.md, however when I do that, then selecting "clear all context and accept all edits" will result in claude forgetting the plan and reading the wrong plan file.

[SeanHollen]

To confirm there is no workaround here, I had this interesting exchange

⏺ The project rule says I must never modify an existing plan file after approval, and must create a new plan file instead. But the designated plan file polymorphic-giggling-lake.md already has content (the Clerk-to-Google-OAuth plan). Plan mode says I can only edit this specific file.                                                     
                                                                                                                                                                                                                                                                                                                                                  
  This is the exact conflict described in the rule. I must halt and tell you.                                                                                                                                                                                                                                                                     
                                                                                                                                                                                                                                                                                                                                                  
  I cannot write the plan. The designated plan file (polymorphic-giggling-lake.md) already contains the approved Clerk-to-Google-OAuth migration plan. Your project rule says I must never modify an existing plan file after approval — I must create a new file instead. But plan mode restricts me to only editing that one designated file.   
                                                                                                                                                                                                                                                                                                                                                  
  You'll need to grant me permission to create a new plan file (or resolve this conflict) before I can write the plan. The plan is fully designed and ready to write — here's a quick summary of what it covers: