Plan Mode vs. Agent Mode
Plan mode is when the AI proposes steps, scope, and files before executing; agent mode is when it runs tools and edits immediately within policy.
The split implements intent preview as a product mode, not only a one-off confirmation dialog.
Share
What it means
Plan mode outputs a readable plan users can edit; agent mode executes tool calls and side effects, often with optional “plan first” as default for risky tasks.
Why designers should care
Mode clarity prevents surprise autonomy. Users should always know which mode is active, how to switch, and what changes when they promote a plan to execution.
Example
Cursor Plan mode lists files to touch and test commands; user clicks Build and the same thread switches to agent mode with a timeline of executed steps.
Common mistakes
- • Agent mode as default on destructive workflows with no plan step.
- • Plans in raw markdown with no structured edit or approve controls.
- • Mode toggle hidden in settings instead of visible in the composer.