Theme 1 – Planning mode adds useful structure and iteration
Many commenters say a dedicated planning step lets them separate design from implementation, refine ideas, and keep complex projects on track.
“I use Claude's Plan mode daily and it's great. I almost always have feedback to refine the plan and I want a clean separation of planning time before writing code.” – dbbk
“I ask it to give me a plan, as a living document, and we spend a good hour or two iterating over the plan.” – spacedcowboy
Theme 2 – Newer models make explicit plan mode unnecessary
Several users argue that modern LLMs can follow conversational instructions well enough that a separate “plan mode” is just a prompt reminder and has become redundant.
“The real reason why plan mode is dead is because you can just conversationally instruct the agent to not make changes to the repository … and it will listen.” – tcdent
“Claude code’s plan mode began its slow march towards deprecation when they hid the ‘clear context and implement’ option behind a flag.” – nojs
“Plan mode came about because earlier models were loose cannons… Today's models follow instructions better enough to not need a separate mode.” – esafak
Theme 3 – Desire for better collaboration, auditability, and flexibility
Some find generated plans hard to review or lacking an audit trail, and they prefer more flexible workflows (sub‑agents, external tools, or iterative conversation) that keep them closely involved.
“The plan can be detailed and technically correct, but still be hard to review because the important bits are buried and feel distant from my own thinking.” – aymandfire
“It also doesn't allow leaving an audit trail of plans and decisions (by default, anyway).” – throwaway27448
“I'd like a brainstorming mode, with limited side effects… I want it to go and read stuff but also invoke some commands and generate reports.” – 6thbit