Blog · Cursor 使用指南 · Published

How to Start Using Cursor: Download, Sign-In, and Your First Project

Based on Cursor's official quickstart, this guide sets out the order for downloading, signing in, and starting your first project: which installer to use on each system, what to confirm after signing in, opening the Agent with Cmd/Ctrl+I to explain the codebase first, then making a small change, reviewing the diff, and running the checks your project already uses. When a task spans multiple files, requires research first, or needs your approval before code is written, use Plan Mode. The article includes a download comparison table, guidance on when Plan Mode applies, and a five-step troubleshooting sequence for when you get stuck, and explains why third-party repackaged installers are not recommended.

If you're using Cursor for the first time, following the official quickstart gives you a clear sequence: get the installer for your system from the download page, open the app and sign in, choose a folder, open the Agent with Cmd+I (macOS) or Ctrl+I (Windows and Linux), have it explain the codebase first, then make a small change, and finally review the diff and run the checks the project already uses (Cursor Quickstart). You don't have to start by rewriting an entire module—the official low-risk examples are things like changing copy or fixing a small UI issue. When a task spans multiple files, requires research first, or needs your approval before code is written, it's better to press Shift+Tab to switch to Plan Mode and get a plan first.

1. Download: Check the Installer Against Your System First

The official download list is split by system, and the differences go beyond the installer's file extension:

System Version requirement stated by Cursor Installer format Other notes on the page
macOS macOS 12 (Monterey) or later Native installer (.dmg) Supports both Apple Silicon and Intel
Windows Windows 10 or later Native installer (.exe) No other requirements listed on the page
Debian / Ubuntu Not listed on the page apt repository Marked on the page as the recommended option
RHEL / Fedora Not listed on the page dnf repository Install using the repository file Cursor provides
Linux portable version Not listed on the page AppImage Grant execute permission before running

Native installers (.dmg, .exe) are the standard route: download, double-click, and follow your system's prompts to install. They don't go through an app store and don't require an additional software source. The macOS row lists a single .dmg and notes that both chip types are supported, so there's no need to pick a chip-specific version.

Only the three Linux rows require a choice. Cursor states that the apt and yum packages take priority over the AppImage because they provide a desktop icon, automatic updates, and a CLI. The page labels the AppImage as a portable version: download it, run chmod +x to grant execute permission, then run it directly. Cursor lists automatic updates under the apt and yum packages, not under the AppImage.

Where to get them follows the same split: desktop installers come from the download page at cursor.com, and the Linux repository addresses are at downloads.cursor.com (Cursor Quickstart). Installers from forums, cloud drives, or tutorial attachments can't be checked for source or modifications, so this article does not recommend third-party repackaged versions.

2. Sign-In: The Official Guide Says One Step; You Need to Confirm Two Things

The quickstart covers sign-in in a single step—"open the app and sign in"—and then moves straight to choosing a folder and starting with a small task. The page doesn't expand on account types, plans, or billing; the docs homepage collects models and pricing under Models & Pricing and points account and billing questions to the official Support entry point (Cursor Docs).

So on your first sign-in, you only need to confirm two things: you can reach the app's main interface, and you can select a local folder. If both hold, you can move on. If you're stuck at this step, go back to the official download page and check your OS version first; switching to a third-party repackaged installer is not recommended.

If the interface doesn't match the tutorial screenshots you're looking at, the docs homepage also has a Changelog entry—check what changed recently before deciding you clicked the wrong thing.

3. Your First Project: Let It Explain First, Then Let It Act

Once you've picked a folder, open the Agent with Cmd+I or Ctrl+I. The recommended first request is to have it explain the codebase: point out the main entry points, the key modules, and which files you should read before making changes. It searches the repository, reads the relevant files, and summarizes how the parts of the project fit together.

One prerequisite can't be skipped: the Agent reads the folder you selected. Pick the wrong directory and it will explain a different project, and later changes will land in the wrong place. So the first step isn't rushing to write a prompt—it's checking that the folder name in the project pane is correct.

You can write the prompt in plain language; just make the scope and the desired output clear. Both official examples start by stating what you want it to do, and the second also asks it to explain the trade-offs and wait for your choice before acting. The example below adds a line—"don't modify any files yet"—that you can keep if you need it (an illustrative example, not an official quote):

Don't modify any files yet. Read through this project and tell me where the entry points are, which core modules exist, which files I must read before changing code, and flag anything you can't confirm.

4. Your First Change: Small, Checkable, Reversible

Once you understand the structure, ask it to suggest a few small, safe improvements with their trade-offs; pick one and let it make the change. If you already know what you want, just describe the result. The official low-risk examples are changing copy or fixing a small UI issue—small in scope and easy to roll back if something goes wrong.

As it works you'll see a diff, marking added, deleted, and modified lines. The official guidance at this step is specific: when it's done, review the diff first, then have it run the checks the project already uses. These checks usually fall into four kinds, each meaning something different:

  • Tests: run the existing test cases to see whether anything broke.
  • Type checking: check that the types of variables and data line up.
  • Lint: a code-style check covering formatting and error-prone patterns.
  • Local build: check whether the project packages or starts up properly.

This step turns "it looks right" into "it ran." The diff shows exactly which lines changed, and the checks tell you whether anything else broke. If both pass, move on to the next task; if only one passes, have it explain why the other failed before adding more requirements.

5. When the Task Gets Bigger: Switch to Plan Mode for a Plan

Cursor states that Plan Mode suits three kinds of tasks: those spanning multiple files, those that require research first, and those where you want to approve before code is written. To switch, press Shift+Tab in the Agent input box. Once in Plan Mode, it doesn't write code right away; it proceeds in order: research the codebase to find the relevant files, ask questions about the requirements, produce a detailed implementation plan, and wait for your approval before acting.

Your task Suggested mode What you'll see What you need to do
Change one line of copy, adjust one style Edit directly A diff Review the diff, run the project's existing checks
A new feature or refactor touching multiple files Plan Mode Relevant files, questions, an implementation plan Answer the questions, approve the plan
Requirements you can't articulate yet Plan Mode It asks you questions Clarify the requirements before approving

The most direct test is whether this change touches several places at once. If the task also requires research first, or needs your approval before code is written, Plan Mode fits for the same reasons.

6. If You Get Stuck, Troubleshoot in This Order

Work through these in order—each step yields a definite answer:

  1. Can't install: check your OS version first (macOS 12+, Windows 10+); on Linux, prefer the apt or dnf repository; the AppImage must be given execute permission before it will run.
  2. Can't open the Agent: use Cmd+I on macOS, Ctrl+I on Windows and Linux.
  3. Unsure whether a change is correct: open the diff and read it line by line, then have it run the project's existing tests, type checking, lint, or local build.
  4. The changes are making things messier: stop, switch to Plan Mode for a plan, and let it act only after you approve.
  5. Account, billing, and questions the docs don't cover: use the Models & Pricing and Support entry points on the docs homepage.

The logic behind the order: causes you can verify yourself—a wrong installer, a wrong shortcut—come first; account and billing issues need the official channels, so they come later.

7. Once Familiar, Write Repeated Instructions as Rules

The quickstart's next steps list Rules: long-lived instructions for a project so you don't have to repeat yourself every time. This isn't required to get started—write them once you find yourself giving the same instruction repeatedly in the same project. The docs homepage collects customization material under Customize and lists integrable workflows including GitHub, GitLab, Azure DevOps, Bitbucket, JetBrains, Slack, and Linear; look up the corresponding page when you need one (Cursor Docs).

8. If You Want to Compare Paid Tiers, Read This Section

That covers downloading, signing in, and the basics of using Cursor. This article only answers getting-started questions and does not compare prices; for account and billing questions, follow the official Support link on the docs homepage.

This site is a third-party top-up service and is not affiliated with OpenAI. It handles ChatGPT membership orders only; Cursor is outside its scope (Top-Up Service Terms). If you also want to compare ChatGPT tiers by usage and decide whether to pay, see the subscription cost overview; current tiers and prices are on the ChatGPT top-up plans page. Each top-up covers 1 month only, with no automatic charges, and the RMB price is not on the same basis as OpenAI's official USD pricing, so the two shouldn't be converted and compared directly.

Ken|Operations Lead at TopupCat

Content is compiled by the TopupCat content team and published under the name of Ken, Operations Lead.View author profile

Related reading

Related products: ChatGPT Go · ChatGPT Plus · ChatGPT Pro · Top-up guide · FAQ · Self-service troubleshooting