Cursor · Basics

Getting started

Import your VS Code setup, open a repository you know, choose an Agent mode, and review your first diff.

Getting started with Cursor

Pick a project you can judge

Your first test should be on code you already understand, so you can tell when the agent is wrong. A small repo with a test or build command is ideal, because Agent can run it to check its own work. Cursor runs on macOS 12 or later and Windows 10 or later, and on Linux through apt, dnf or an AppImage.

Set up once, then change one thing

If you use VS Code, import your settings first, then look for your must-have extensions, since some may not be on Open VSX. Don't configure much else yet. Rules and Cloud Agents will make more sense once you've seen what Agent gets wrong on your own code.

Frequently asked
How do I install Cursor?

Go to cursor.com/download, download the installer for your operating system, open it, and sign in with a Cursor account. Then choose File and Open Folder to open a project.

Can I import my VS Code settings into Cursor?

Yes. Press Cmd+Shift+J, or Ctrl+Shift+J on Windows and Linux, go to General then Account, and click Import under VS Code Import. It brings over extensions, themes, settings and keybindings.

What should my first Cursor prompt be?

Cursor's Quickstart suggests asking for an explanation of the codebase, including where it starts, its key modules and what to read first.

Which mode should a beginner use in Cursor?

Start in Agent, the default, for most tasks. Switch to Ask when you only want an explanation and no edits, and press Shift+Tab to move between modes.