In this categoryCursor ยท 27
CursorBeginner

Cursor Setup Guide: From Install to Your First AI Edit

Install Cursor, bring over your VS Code settings and extensions, pick a model, and make your first AI edit with Tab, the Agent, and a project rule.

10 minBeginner

To set up Cursor: download it at cursor.com, sign in, and import your VS Code extensions and settings in one click during onboarding. Pick a model (Auto is the safe default), accept a Tab suggestion, ask the Agent for one scoped change, then add a project rule. Total time: about 10 minutes.

Cursor is an AI code editor built as a fork of VS Code, so the layout, keybindings, and extensions feel familiar while the AI features sit on top. This guide takes you from a fresh download to your first accepted AI edit using the current Cursor 3 interface: install the app, import your VS Code setup, choose a model, and try the three core tools, Tab, the Agent, and project rules.

What you need

  • A Mac, Windows, or Linux machine
  • A Cursor account (free Hobby plan is fine to start)
  • A small project or folder to open
  • About 10 minutes

Step 1: Install Cursor

Download the installer for your platform from cursor.com and run it. On first launch Cursor shows an onboarding wizard where you sign in or create an account and choose a keyboard layout. No credit card is required for the free Hobby plan.

Cursor - onboarding
Welcome to Cursor
Sign in / Create account
Keyboard: [ Default ] [ VS Code ] [ Vim ]
Import from VS Code? [ Import ] [ Skip ]
The first-run wizard signs you in and offers to import your VS Code setup.

Step 2: Import your VS Code settings and extensions

Because Cursor is built on VS Code, it can bring over your extensions, themes, keybindings, and user settings in one click. Accept the import prompt during onboarding. If you skipped it, you can trigger it later from Cursor Settings, under General, Account, Import VS Code Settings, or from the three-dots menu in the Extensions panel.

Cursor Marketplace runs on Open VSX, not the VS Code Marketplace
Extensions in Cursor come through the Cursor Marketplace, a proxy in front of the Open VSX registry that screens submissions for malware and supply-chain risk before they are installable. Most popular VS Code extensions are available, but a few Microsoft Marketplace-only ones may be missing or behave slightly differently, and extension-specific settings are not always carried over, so spot-check anything you rely on.

Step 3: Pick a model

Open the AI input (Cmd/Ctrl+L for the chat sidebar) and use the model picker in the chat header. Auto mode routes your request to a suitable model automatically, Composer is Cursor's own in-house model tuned for speed, and you can also pin a specific third-party frontier model such as Claude Sonnet or a GPT model. The available models and how usage is billed depend on your plan.

Step 4: Understand the plans before you commit

You can do everything in this guide on the free tier. The table below was verified against the public plans on cursor.com in July 2026: paid plans run on a monthly credit pool worth the same dollar amount as the price, so Pro carries a $20 pool and Ultra a $200 pool, while Auto mode stays unlimited and does not draw from it. Pricing and limits change, so confirm the current numbers on the official pricing page before you upgrade.

PlanPriceRoughly who it is for
HobbyFreeTrying Cursor; limited Agent requests and Tab completions
Pro$20 / monthSolo developers; unlimited Tab, extended limits, frontier models, a $20 credit pool
Pro+$60 / monthHeavier premium-model use; roughly 3x the Pro usage pool
Ultra$200 / monthPower users; roughly 20x the Pro usage pool, priority access to new features
Teams$40 / user / monthTeams; centralized billing, SSO, shared context, admin controls
EnterpriseCustomOrgs needing pooled usage, SCIM, access controls, audit logs
Check the live pricing page
Cursor adjusts tiers and usage credits periodically. For the exact current prices, included credits, and any trial details, see the official page at cursor.com/pricing rather than relying on a cached number.

Step 5: Make your first edit with Tab

Tab is Cursor's autocomplete on steroids. Start typing in a file and Cursor suggests multi-line completions, including edits across nearby lines. Press Tab to accept a suggestion. This is the fastest way to feel the difference from a plain editor.

src/format.ts
// Start typing a function signature and let Tab complete the body:
export function formatPrice(cents: number): string {
  // press Tab here; Cursor suggests the implementation
}

Step 6: Ask the Agent for a change

The Agent is the conversational, multi-file mode. Open it with Cmd/Ctrl+L, describe a concrete change, and it proposes edits across the relevant files. Review each diff and accept or reject it, just like reviewing a pull request. Keep your first request small and specific.

Bigger jobs move to the Agents Window
Cursor 3, shipped April 2, 2026, split multi-agent work out of the classic editor into a dedicated Agents Window (open it with Cmd/Ctrl+Shift+P, then search Agents Window). Cursor's own changelog describes it as a place to "run many agents in parallel across repos and environments: locally, in worktrees, in the cloud, and on remote SSH", per the official Cursor 3 changelog. For your first edit, the inline Agent in the main editor is still the right tool; reach for the Agents Window once you are running more than one task at a time.
Cursor - Agent
You
Add input validation to formatPrice so a negative number throws a clear error.
Agent
I'll add a guard at the top of formatPrice in src/format.ts. Here's the proposed diff for you to review.
Describe one scoped change; the Agent proposes diffs you approve.

Step 7: Add a project rule

Rules give the AI persistent context about your project so you stop repeating conventions in every prompt. Project rules live in the .cursor/rules folder as .mdc files with frontmatter. You can also drop an AGENTS.md file in the project root for plain-markdown instructions without frontmatter.

.cursor/rules/conventions.mdc
---
description: Project coding conventions
globs: src/**/*.ts
alwaysApply: true
---

- Use named exports, never default exports.
- Currency values are integer cents, never floats.
- Add a Vitest test for every new exported function.
Plain .md files are ignored in .cursor/rules
A file inside .cursor/rules needs the .mdc extension and frontmatter (description, globs, alwaysApply) to be picked up. A plain .md there is skipped. If you want a simple markdown-only file, use AGENTS.md in the project root instead.

Result: Cursor is installed with your VS Code setup intact, a model selected, and you have made an edit with Tab, run a change through the Agent, and added a rule the AI will respect going forward. From here, every larger task is the same loop at greater scope.

Related guides

Watch related tutorials

Free weekly email

New guides in your inbox

Fresh step-by-step how-to guides as we publish them. One email a week, no more.

Tags
#cursor setup#cursor pricing#install#vscode#agent#tab#agents window