Cursor is an AI code editor. You open a folder, and an AI agent can read the project, explain it, edit files and run terminal commands for you. Next to the agent sits Tab, an autocomplete that suggests the next lines as you type. Cursor runs on macOS 12 and later, Windows 10 and later, and Linux, according to its quickstart. (Cursor Docs: Quickstart (opens in a new tab); Cursor Docs: Agent overview (opens in a new tab))

The short version for beginners: let the agent explain before it edits, start with one small change, read every diff, and switch to Plan Mode for anything bigger. That order matches the quickstart Cursor gives new users, and it is the fastest way to learn the tool without breaking your project. (Cursor Docs: Quickstart (opens in a new tab); Cursor Docs: Plan Mode (opens in a new tab))

What you need before you start

Download Cursor from cursor.com/downloads, open the app and sign in. Then pick a folder for a small first task. A personal project, a practice repo or a copy of something you do not mind changing is ideal. (Cursor Docs: Quickstart (opens in a new tab))

Cursor has a free Hobby plan with limited Tab completions and limited agent requests, plus paid plans for heavier use, according to a September 2026 pricing breakdown by Jetadmin. The free plan is fine for learning. Long working sessions can hit its limits. (Jetadmin (opens in a new tab))

Tip: Use Git from day one. Cursor saves checkpoints before big agent edits, but its docs say those checkpoints are stored locally and are not a replacement for version control.

The three parts of Cursor

Agent is the main one. You open it in the side pane with Cmd+I on a Mac or Ctrl+I on Windows and Linux. It can search your code and the web, read files and images, edit files, run shell commands and ask you clarifying questions, according to Cursor's docs. (Cursor Docs: Agent overview (opens in a new tab))

Tab is the autocomplete. Suggestions show up as gray text ahead of your cursor. Press Tab to accept, Cmd+Right Arrow (Ctrl+Right Arrow on Windows and Linux) to accept one word at a time, and Escape or simply keep typing to reject. After you accept, pressing Tab again jumps to the next spot Cursor expects you to edit. (Cursor Help: Tab (opens in a new tab))

Rules are standing instructions. Project rules live as .mdc files in a .cursor/rules folder inside your project. Cursor also reads a plain AGENTS.md file in the project root. User rules, which apply to all your projects, are set under Customize, then Rules. (Cursor Docs: Rules (opens in a new tab))

5 prompts to start with

1. Get a map before you touch anything

Ask the agent to explain the project first

Prompt 1: Explain the codebase

Explain this codebase. Point me to the main entry points, key modules, and anything I should read before making changes.

Why it works

This is the first prompt in Cursor's own quickstart. The agent searches the repo and summarizes how the pieces fit together. Read the answer and open the files it names. You will understand your own project faster, and your later prompts will be more precise.

2. Make one small, safe change

Let the agent suggest, and you choose. Low risk changes like fixing copy or a small layout bug are the right size for a first try.

Prompt 2: Three safe improvements

Suggest three small, safe improvements in this codebase. Explain the tradeoffs and wait for me to choose one.

3. Review the diff and run your checks

After the agent edits, the diff view shows exactly what changed. Then have it run the checks your project already has: tests, the type checker, the linter or a local build.

Prompt 3: Verify the change

Run this project's existing checks: tests, type checker, linter and build.
Fix anything that fails because of your change.
Then list every file you changed and why, in plain English.

4. Use Plan Mode for anything bigger

Press Shift+Tab in the agent input, or use the mode picker, to switch to Plan Mode. The agent researches the code, asks clarifying questions and writes an implementation plan. You can edit the plan before it builds anything. Cursor recommends it for features with several possible approaches, changes across many files, and requirements that are still fuzzy.

Prompt 4: Plan before you build

I want to add [feature, in one or two sentences].
Ask me any questions you need first.
Then write a step by step plan, list the files you will touch, and wait for my approval before writing code.

5. Teach Cursor your preferences once

Type /create-rule in the agent and describe what you want. Cursor generates the rule file and saves it in .cursor/rules. Good first rules are about style and communication, not about the code itself.

Prompt 5: A beginner friendly rule

/create-rule Always explain changes in plain English for a beginner. Keep each change small. Never delete files or add new dependencies without asking me first.

Where Cursor falls short

The agent can be confidently wrong, and the bigger the task, the more ways it can drift. That is why Plan Mode exists. Cursor's own advice when a planned build goes wrong is to revert the changes, make the plan more specific and run it again, which it says is usually faster than patching a run with follow up prompts.

Plain .md files in .cursor/rules are ignored, because project rules need the .mdc format with frontmatter. If a rule seems to do nothing, check the file type first. Checkpoints only restore files, not your conversation, and they live on your machine.

Cursor is also moving toward building whole apps, not only editing code. Its cloud agents can now build and publish web apps with hosting, an optional Postgres database and Cursor sign-in, on paid plans with cloud agents turned on, according to Sam on AI's November 6, 2026 brief and The Neuron. (Sam on AI (opens in a new tab); The Neuron (opens in a new tab))

Tip: Start every new task in a fresh chat. Old conversations carry old assumptions, and a clean start with one clear goal gets better results than a long thread.