The real reason why plan mode is dead is because you can just conversationally instruct the agent to not make changes to the repository or to make changes to selected documents only, and it will listen. There was a time when we needed to enforce this via selected tool use, but we have surpassed that.

▲

Feathercrown 4 hours ago | parent | next [-]

It seems unwise not to implement sandbox measures just because the chance of misuse has gotten lower.

▲

monster_truck 4 hours ago | parent | next [-]

Plan was never a sandbox or a permissions system

▲

ImaCake 2 hours ago | parent [-]

Plan mode does have different permission controls though? Its difficult for me to parse the docs on this but it does seem to imply more than just a prompt although less than a full sandbox. https://code.claude.com/docs/en/permission-modes#analyze-bef...

	▲	fy20 an hour ago \| parent [-]
		The way it worked originally was it would trigger a different system prompt, and then the permissions system would prompt you (even on YOLO mode) before running any non-readonly actions. Cursor would also write a plan document, which was useful when working on larger tasks (due to context size). I still find that part useful today.

▲

diegof79 4 hours ago | parent | prev | next [-]

Yes, but plan mode wasn’t that.

You can use Docker’s sbx or similar VM/containers for that.

▲

brianwawok 4 hours ago | parent | prev [-]

What? Nothing to do with that

▲

throwaway27448 4 hours ago | parent | prev | next [-]

It also doesn't allow leaving an audit trail of plans and decisions (by default, anyway). Most of my mutating prompts look like "Propose a plan for change X and write to file Y" and "Execute steps M-N from file Y".

RE the article: I don't think it's obvious why this process is worth following until you find your time and attention wasted. Conversationally-building is the express train to waste. I'm not sure why you would even be talking to claude if you don't understand what you want to build.

▲

esafak 4 hours ago | parent | prev [-]

I agree. Plan mode came about because earlier models were loose cannons, doing what they pleased. Today's models follow instructions better enough to not need a separate mode. However, there is still value in using a separate, smarter model for planning than execution, and persisting it for auditing on completion.

If you do use plan mode you might like https://plannotator.ai/

I typically converse with the default model to point the plan in the right direction, then have it iterate with a smarter reviewer to find flaws until the plan file is converged.