Which Cursor Agent Mode Should You Use?
Use Agent for most work, Ask when you want answers with no edits, Plan when you want to approve an approach for a multi-file change, and Debug for bugs you can't explain from the code. Press Shift+Tab in the chat input to rotate through them, or Cmd+. (Ctrl+.) to open the mode menu.
I'm not sure which Cursor mode this task needs. Task: [describe the task] Files involved, if known: [@file or "unknown"] How I'd know it's done: [test, command or behavior] Recommend Agent, Ask, Plan or Debug, with one sentence of reasoning. Don't make any changes yet.
Try it now
- 1Open Agent with Cmd+I (Ctrl+I), then press Shift+Tab until the mode shows Ask.
- 2Ask how a feature you know works, such as "How does the authentication flow work?" You'll see it read files without proposing an edit.
- 3Press Cmd+. (Ctrl+.) to open the mode menu, choose Plan, and describe a small multi-file change. It worked if you get a plan with a Build button rather than edits.
Use it when
At the start of each task, and any time you realize a task is different from what you assumed. A bug fix that stalls in Agent is a reason to move to Debug. A question that turns into a change is a reason to move from Ask to Agent.
Skip it when
Don't switch modes in the middle of a thread to continue the same work without thinking about it. Cursor's help says each mode uses its own context, so switching starts a fresh context window. You'd lose what the agent had already read, so carry over any findings yourself.
Why it works
Each mode changes what the agent does first. Ask can't edit files at all. Plan researches, asks clarifying questions and waits for you to click Build. Debug forms hypotheses and adds log statements before it fixes anything. Agent starts exploring and editing straight away. Picking the mode matters because the expensive errors come from the wrong starting move, such as editing before anyone understood the code. Cursor's help says project, user and team rules apply in all four.
Example
Say a login page has three separate tasks. "Where are sessions created?" goes to Ask. "Add remember me across the form, API and session store" goes to Plan, because it touches several files and you want to see the approach. "Users get logged out at random" goes to Debug, because reading the code won't show a timing problem. "Fix the typo in the button label" goes straight to Agent.
Going further
Beyond the four built-in modes, you can keep a skill on for a whole session. Pick it from the / menu and press Option+Enter (Alt+Enter on Windows) to use it as a Custom Mode, so a checklist like /tdd stays in context until you exit. Cursor's docs list Custom Modes for the Agents Window and the CLI. The CLI's mode table lists Agent, Plan and Ask, with /plan and /ask as commands, and doesn't list Debug.
Common mistakes
- Staying in Agent for a question, then finding it has edited something you only wanted explained.
- Using Plan for a one-line fix. Cursor's docs say jumping straight to Agent is fine for quick changes.
- Asking Agent to retry a timing bug for the fifth time when Debug would collect real evidence.
- Assuming a new mode remembers the last one. It starts with fresh context.
Sources
- Agent mode, Cursor Help
- Ask mode, Cursor Help
- Plan Mode, Cursor Docs
- Debug Mode, Cursor Docs
- Keyboard shortcuts, Cursor Help
- Prompting agents, Cursor Docs
- Cursor CLI, Cursor Docs
Checked 6 November 2026. Products change often, so confirm details with the vendor.