[BUG] plan mode handles only one plan and is likely to lose plans

Resolved 💬 3 comments Opened Apr 7, 2026 by davidcok Closed Apr 10, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Plan mode is convenient for having Claude do planning, allowing it to read lots of files without doing any editing (though sometimes it does editing anyway).

However, it seems (and Claude confirms this) that it can only work on one plan. Once in plan mode and it makes a plan, if one asks it to save that plan and work on a new topic, the old plan is likely to be overwritten and lost despite explicit statements to save it. Claude says it cannot just switch to another plan.

This is a real limitation in work flow and it easily accidentally causes unnecessary rework. Claude ought to be able to readily switch between multiple plans, saving some, making new ones, executing and then deleting others, in whatever order works for the user. For example, my unit tests take a few hours to run. After a big change we need to run them without changing git branch or doing other editing -- so pair planning on multiple topics is a good use of time then.

What Should Happen?

Claude should be able to easily juggle multiple plans while in plan mode.

Error Messages/Logs

Steps to Reproduce

  • Be in plan mode (Clause Code Max for me)
  • - Work on a plan
  • - Tell Claude to save the plan
  • - Start work on a new plan
  • - The first plan will likely be overwritten and lost.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.92 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗