Why Plan Mode Still Matters in AI Coding Agents (Codex, Claude, Cursor)
Melvin Vivas · X video post · 2026-09-27 · 5:54 · 553 views · Open on X
Topics: AI Dev Tools & Productivity, Prompt & Context Engineering · Level: beginner
Summary
Melvin Vivas argues against removing "plan mode" from AI coding tools like Codex, Claude and Cursor, even as models get smarter. In plan mode the agent can't edit code, so it works as a guardrail. You use it to agree on the architecture and implementation details first, and the agent asks clarifying questions you might skip. Planning first also saves tokens: you don't pay for code and tests you later throw away.
Key points
- Plan mode (or ask mode) is a guardrail: the agent can discuss and plan but cannot touch your code, so a simple question doesn't trigger unwanted edits.
- Use plan mode to map out the architecture and implementation details and check they match what you want before any code is written.
- Example: decide early on SQLite instead of Postgres. Choices like this are cheap to change in a plan and costly to change after the code exists.
- Plan mode asks guiding questions, e.g. whether a new TUI installer should replace the existing setup.sh/PowerShell scripts (scripts become thin wrappers) or sit alongside them. The plan updates from your answers.
- Many requirements only surface while you iterate with the agent, so treat planning as an iterative loop, not a single prompt.
- Skipping the plan on a big feature can waste tokens: the agent builds the scaffolding, writes tests and runs them, then you reject the design and everything has to be redone and retested.
- Pure vibe coding (chat and let it implement) is fine for small things. For large technical features, plan first.
- His closing point: even if models are 'smart enough', you still have to prompt them well, and plan mode gives you a structured way to do that.
Resources mentioned
- Cursor · tool · x.com · free · recommended by both Bashiri Smith & Melvin Vivas
AI-native code editor (VS Code with AI built in).
Also in: Finding Cursor Cloud Agents After the Cursor–X Unification (Melvin Vivas on X · notes), Overnight notebook generation with Grok Bot, Cursor cloud and Grok 4.7 (Melvin Vivas on X · notes), Gemini 4 Argon in Cursor: CursorBench Score and Pricing (Melvin Vivas on X · notes), SpaceX AI / Cursor Ambassador Program Waitlist (Melvin Vivas on X · notes) and 135 more - OpenAI Codex · tool · openai.com · paid · recommended by both Bashiri Smith & Melvin Vivas
OpenAI's coding agent. In the diagram it writes code, fixes review findings and drives the build loop. The creator also used it to make this video.
Also in: Developers moving from ChatGPT/Codex to Claude (Melvin Vivas on X · notes), Creator Opinion: Codex Is Still the Best at Computer Use (Melvin Vivas on X · notes), OpenAI Codex Ambassador applications are open (Melvin Vivas on X · notes), GPT-Live-1.1: Multilingual Voice Update for ChatGPT and Codex (Melvin Vivas on X · notes) and 264 more - Claude Code · tool · code.claude.com · paid · recommended by both Bashiri Smith & Melvin Vivas
Build agents and pipelines from the terminal; the guide's main agentic coding tool.
Also in: First impressions: Claude Code in the cloud is good and fast (Melvin Vivas on X · notes), Why Claude Code feels faster: gzipped turns and instant cloud sessions (Melvin Vivas on X · notes), Watch What Fills Your Coding Agent's Context and When to Clear (Melvin Vivas on X · notes), Claude Code's Right Sidebar and Context Breakdown (Melvin Vivas on X · notes) and 124 more - PostgreSQL · tool · postgresql.org · free · recommended by both Bashiri Smith & Melvin Vivas
An open-source relational database; with the pgvector extension it also stores and searches embeddings.
Also in: Prompt Claude to Plan 3 Production-Grade AI Portfolio Projects (Bashiri Smith on Facebook · notes), Pi Durable: A Runtime for Crash-Proof, Long-Running, Multiplayer Agents (Melvin Vivas on X · notes) - SQLite · tool · sqlite.org · free
A small SQL database that runs inside your program as a single file, with no server to set up.
Also in: Pi Durable: A Runtime for Crash-Proof, Long-Running, Multiplayer Agents (Melvin Vivas on X · notes), Running Qwen3.8-27B EXL3 Locally on an RTX 3090 with 220K+ Context (Melvin Vivas on X · notes), One-Shotting a Slack Clone with Fable 5 (Melvin Vivas on X · notes), Google Antigravity 2.0: Multi-Agent Desktop App Walkthrough (Subagents, Scheduled Tasks) (Melvin Vivas on X · notes) and 1 more
Try this
- Before a large feature, start in plan or ask mode so the agent can't modify code while you discuss it.
- Settle architecture choices (e.g. SQLite vs Postgres) in the plan before implementation.
- Answer the agent's guiding questions and keep refining the plan until it matches what you want.
- Save vibe coding without a plan for small tasks; plan big technical features first to avoid wasting tokens on rework and retesting.
- Build a TUI installer that replaces or wraps existing setup.sh and PowerShell install scripts (the example used in the plan-mode demo).
More in AI Dev Tools & Productivity
- PiG: The Pi Coding Agent Rebuilt in Go as a Single Native Binary
- Why Plan Mode Still Matters in AI Coding Assistants (Codex, Claude, Cursor)
- Why removing Plan Mode from coding agents is a mistake
- Using Claude Code (Opus 5.5) to cut clips from livestreams
- Antigravity 2.0 Adds a /plan Mode for Agent Planning
- Devin's SWE-2 Coding Model Is Free for a Limited Time (Until Oct 8/15)