Plan mode reuses existing plan file when re-entering — no way to create a new plan
Resolved 💬 5 comments Opened Mar 5, 2026 by miqcie Closed May 12, 2026
Problem
When re-entering plan mode in the same session, it reassigns the same plan file from the previous planning session. There's no way to create a new plan file while preserving the existing one.
Steps to Reproduce
- Enter plan mode → creates
plan-01.md - Write a plan for Task A, exit plan mode, execute
- Later in the same session, enter plan mode for a different Task B
- Plan mode assigns the same
plan-01.mdwith the message "this is the only file you are allowed to edit" - The only way to write the new plan is to overwrite the old one
Current Behavior
- Re-entering plan mode reuses the existing plan file
- System message says the existing file is "the only file you are allowed to edit"
- No option to create a fresh plan file
- Workaround: exit plan mode entirely and write the plan to a regular file, losing plan mode benefits
Additional Issue: ExitPlanMode rejection contradiction
During the same session, ExitPlanMode was rejected multiple times with "the user doesn't want to proceed" while the system reminder simultaneously said "Exited Plan Mode." This created a confusing state where it was unclear whether plan mode was active or not.
Expected Behavior
- Re-entering plan mode should create a new plan file (
plan-02.md) rather than reassigning the existing one - OR there should be a way to specify "create new plan" vs "continue existing plan" when entering plan mode
ExitPlanModerejection messages should not contradict the system state
Environment
- Claude Code CLI
- Model: Opus 4.6
- macOS Darwin 25.2.0
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗