undefined

points

[-]

Yes as lostdog says, it’s a new feature that writes plans in plan mode to ~/.claude/plans. And it thinks it needs to continue the same plan that it started.

So you either need to be very explicit about starting a NEW plan if you want to do more than one plan in a session, or close and start a new session between plans.

Hopefully this new feature will get less buggy. Previously the plan was only in context and not written to disk.

by manmal1 days ago|

prev|

[-]

Why don’t you reset context when working on something else?

by mrieck1 days ago|

parent|

[-]

It’s additional features that are related.

For example making a computer use agent… Made the plan, implementation was good, now I want to add a new tool for the agent, but I want to discuss best way to implement this tool first.

Clearing context means Claude forgets everything about what was just built.

Asking to discuss this new tool in plan mode makes Claude rewrite entire spec for some reason.

As workaround, I tell Claude “looks good, delete the plan” before doing anything. I liked the old way where once you exit plan mode the plan is done, and next plan mode is new plan with existing context.

by manmal1 days ago|

parent|

[-]

I get where you're coming from. But you'll likely get better results by starting fresh and letting it read key files or only just a summary of the project goals/spec. And then implement the next feature building up on the previous one. It's unlikely you'll need all the underlying code of the foundation in context to implement something that builds up on it - especially if interfaces are clean. Models still get dumber the more context is loaded, and the usable window isn't all that big, so starting fresh gives best results usually. I try to avoid compaction in any way possible, and I rarely continue the session after compaction, for that reason.

by lostdog1 days ago|

prev|

[-]

Yes, I've also been confused by things like this. Claude code is sometimes saving plans to ~/.claude/plans under animal names. But it's not really surface where the plan goes, not what the expected way to refer back to them is?

by theshrike794 hours ago|

parent|

[-]

It's a cache pretty much. Before it wrote them to the project directory by default, which is really annoying.

Now it has a file it can refer to (call it "memory" to be fancy) without having to keep everything in context. The plan in the file survives over autocompact a lot better and it can just copy it to the project directory without rewriting it from memory.