How Do You Start Using Cursor on a Real Project?
Install Cursor, open a repository you already know, and press Cmd+I (Ctrl+I on Windows and Linux) to open Agent. Ask it to explain the codebase, then have it make one small change, and review the diff. A project you know is the best first test, because you can tell when Agent is wrong.
Give me a tour of this codebase: where execution starts, which modules matter most, and what I should read before changing anything. Then propose three low-risk improvements in [folder or feature], with the pros and cons of each. Don't change anything until I pick one. When I pick, make only that change, then run [npm test / your test, type check or lint command] and tell me what passed.
- 1Open a folder
- 2Ask for a tour
- 3Make one small change
- 4Review and run checks
Try it now
- 1Download Cursor from cursor.com/download, sign in, and choose File > Open Folder to open a project you know.
- 2Press Cmd+I (Ctrl+I on Windows and Linux) to open Agent, and paste the prompt above with the brackets filled in.
- 3When Agent finishes, read the changes in the diff view and reject anything you didn't ask for. It worked if the change matches your choice and the check command passes.
Use it when
Your first hour with Cursor, or when you open a repository you haven't worked in. It suits any project with at least a test, type check, lint or build command that Agent can run to check its work.
Skip it when
Skip the small-change step on a production branch with uncommitted work you care about. Commit or stash first, because Agent's edits land in your working files. If you only want to read code and change nothing, use Ask mode instead, which is read-only.
Why it works
Agent isn't a chat box beside your code. Cursor's docs describe it as searching your repo, editing files and running terminal commands, so it has to work on real files to show what it can do. Its edits are applied as it works, and you review them in the diff view. Starting with a tour also tells you whether it found the right entry points before you let it change anything. Cursor's Quickstart recommends this exact order: explain, one small change, review the diff, run the checks your project already has.
Example
Say you maintain a small Express API. You ask for the tour and Agent names server.ts, the routes/ folder and the database module. You check those against what you know. It suggests a clearer error message, a missing input check and a renamed variable, and you pick the input check. It edits one route, you read the diff, and it runs npm test. You now know how far to trust it on this codebase, and nothing else has been touched.
Going further
Cursor offers Free, Plus, Premium, Super and Ultra plans, and they differ in ways that affect your first week. Plus at $8 has no Auto, Cloud Agents, Bugbot or third-party models, and Free has limited usage. Claude, GPT and Gemini need Premium or higher and are paid from prepaid credit. Older tutorials that mention Pro at $20 describe a legacy plan new customers can't buy. Once this first task works, add a rule for anything you had to correct twice.
Common mistakes
- Judging Cursor on an empty scratch file. Agent has nothing to search, and Tab has little to work from.
- Asking for a whole feature first, then being unable to tell whether the result is right.
- Stopping at the diff. Cursor's Quickstart adds a last step: ask it to run your existing tests, type checker, linter or build.
- Following a tutorial that says to press Cmd+K for inline edit. That shortcut now sends your selection to Agent.
Sources
- Quickstart, Cursor Docs
- Download and install Cursor, Cursor Help
- Your first project, Cursor Help
- Agent mode, Cursor Help
- Models & Pricing, Cursor Docs
Checked 6 November 2026. Products change often, so confirm details with the vendor.