Plan mode is dead
The creator of a failed AI coding app argues that standalone plan modes are becoming obsolete as models improve and planning merges with execution.
read it This candid startup post-mortem offers valuable insights into shifting AI coding interfaces, paired with a heavyweight Hacker News debate.
summary
The developer behind a failed AI coding tool reflects on why standalone plan modes and heavy AI-generated specs fail to resonate with users. As models become more capable, explicit planning artifacts get in the way, and developers prefer an iterative loop of understanding and acting. Rigid workflows force users to prematurely finish thinking, whereas real engineering involves interleaved, organic cycles of experimenting and revising. The accompanying discussion features intense pushback from engineers who rely on plan modes to prevent agents from wasting time and to maintain oversight.
key points
- The author conflated the cognitive process of planning with generating a large structured document that users ultimately dislike reading.
- As LLMs improve at exploring codebases and making reasonable assumptions, the need to explicitly instruct them with pre-made specs shrinks.
- Commenters strongly push back, arguing that plan modes remain vital for complex tasks to prevent expensive mistakes and maintain human control.
who should read it
Software engineers and developer-tool builders navigating AI-assisted coding workflows and agent interfaces.
discussion mixed
consensus
Commenters are deeply split; while tool creators agree that rigid standalone plan modes are fading, many experienced engineers defend them as an essential guardrail against runaway agents.
pushback
A prominent insider notes that plan mode was historically just a lightweight prompt hack rather than a deep architectural feature, validating the author's observations.
[I work on Claude Code] I broadly agree with the author’s point: plan mode was useful, and is no longer useful.
In Claude Code, all plan mode does is add a little reminder to every user message along the lines of “you’re in plan mode, please don’t code yet”. It’s something I came up with late on a Sunday night many months ago, when I got tired of asking Claude to plan with me first before coding in each new session. Something people might not realize is plan mode has always been a prompt — it has never changed the toolset because doing so would break the prompt cache, and so would be …
It provides valuable industry perspective from a Claude Code developer confirming that plan modes were always just simple prompt injections.
Generated by an LLM from the article and thread. Check the sources before relying on it.