3 ms·
I always get Claude Code to create a plan unless its trivial, it will describe all the changes its going to make and to which files, then let it rip in a new co
by small_model 8mo ago
I always get Claude Code to create a plan unless its trivial, it will describe all the changes its going to make and to which files, then let it rip in a new context.
- dionian 8mo agoWhy use a new context? Or you mean, just accept the plan and it automatically clears the context.
- small_model 8mo agoYes sorry, CC does it, then rereads all the files from scratch with the plan in mind.
- steveklabnik 8mo agoRecently, Claude gives you these options when asking you to accept a plan: Would you like to proceed? > 1. Yes, clear context and auto-accept edits (shift+tab) 2. Yes, auto-accept edits 3. Yes, manually approve edits 4. Type here to tell Claude what to change So the default is to do it in a new context. If you examine what this actually does, it clears the context, and then says "here's the plan", points to the plan file, and also points to the logs of the previous discussion so that if it determines it should go back and look at them, it can.
- small_model 8mo agoYes, its basically another way to compact context, means it there is less chance start compacting part way through the plan.
- jbonatakis 8mo ago(Mildly) shameless plug, but you might be interested in a tool I’ve been building: https://github.com/jbonatakis/blackbird https://github.com/jbonatakis/blackbird It breaks a spec (or freeform input) down into a structured json plan, then kicks off a new non-interactive session of Claude or codex for each task. Sounds like it could fit your workflow pretty well.