Don't treat Agent like a chat box
Don't treat Agent like a chat box: a first success is a reviewed diff, not a paragraph.
Treat Cursor Agent like a chat box and the first run ends as a paragraph while the repo stays untouched. Open the pane with Cmd+I (Windows/Linux: Ctrl+I), give a result that can land on disk, then review the diff. Sketch the target first in a wbstorm room.
The official Quickstart’s first useful outcome is one small, reviewed edit, not a tour of “what this repo probably does.” Install, sign in, open a folder, then Agent.
Where chat-box thinking stalls
You only want an explanation
“Explain this codebase” will search and read. The tree does not change. That is warmup, not the first success.
You skip the result
“Take a look” has nothing to check. The docs’ example: three low-risk improvements, wait for you to pick one, then edit.
You skip the diff
Agent edits files and runs the terminal. A first success is the diff plus checks you already run—not how long the reply is.
The first run that actually lands
- 1
Open the repo
Install from cursor.com and sign in. macOS 12+, Windows 10+; Linux has apt / dnf / AppImage. Open the folder you will change. An empty window has nothing to edit.
- 2
Open the Agent pane
Cmd+I / Ctrl+I. Docs: Agent can complete complex coding tasks, run the terminal, and edit code. Tool calls in a task have no documented cap.
- 3
Ask for a result that can land
Describe what “done” looks like. Or follow Quickstart: three safe improvements, you pick one. Copy or a small UI fix is a good first cut.
- 4
Review the diff, then existing checks
Read the diff. Ask it to run tests, the type checker, lint, or a local build you already use. Restore from a timeline checkpoint if needed; that reverts files only, not messages, and is not Git.
| Move | Chat-box habit | Agent habit |
|---|---|---|
| First line | “What is this project?” | “Change X; done means Y” |
| Success | A summary | Reviewed diff + existing checks |
| Mode | Read-only Q&A | Agent tools; Plan for big work |
The first prompt to paste
Suggest three small, safe improvements in this codebase.
Explain the tradeoffs and wait for me to choose one.After you pick, add the result. Do not turn it back into small talk. While Agent works, Enter queues the next instruction; Cmd+Enter injects into the current turn. Repeat the same constraint in Cursor Rules as a .mdc.
Sketches and votes stay out of the editor: use a room ID and whiteboard basics. This page does not claim wbstorm edits your code.
Cmd+I does nothing?
cursor.com/docs/reference/keyboard-shortcuts: Cmd+I toggles the sidepanel. Search Agent in the command palette. Open a folder first.
I only want answers, no file edits?
That is not a first Agent success. CLI docs call Ask a read-only exploration mode. In the editor, use Plan Mode (Shift+Tab) before a wide edit.
Do checkpoints replace Git?
No. Docs: checkpoints are local and separate from Git, for undoing Agent changes. Keep history in Git.
How big should the first change be?
Quickstart: low risk—copy or a small UI fix. Multi-file or unclear scope: Plan first, then build.