Cursor for non-engineers: install, ask, change one thing

Open a folder you already have. Ask the app to explain it. Change one low-risk thing, then read the diff before you keep it. Cursor is the desktop app for that job. The download page describes it as "An agent-first experience, with all the best parts of the editor for when you need them." You can follow the first session without a programming course.

Cursor's Quickstart is the session. It is four moves: install and sign in, ask for an explanation, make one small edit, review the result. The folder can be a site, a notes directory, a project someone else started, or any pile of files you can already open. Payments, sign-in, and deploy files stay out of the first change.

Use Cursor on a folder you already have

The Quickstart states the scope of a first session in one paragraph.

"This guide gets you from install to your first useful change in Cursor. You'll sign in, ask Cursor to explain your codebase, make a small edit, and review the result."

"Codebase" is the folder you opened. The Quickstart uses that word for any project, whatever language the files happen to be in. This page stays on those four moves. It does not add lessons, exercises, or a language to learn first.

If the folder is not yours, stop. The rest of the steps assume you can edit the files and you can throw the edit away.

Install the app and sign in

The install instruction on the Quickstart is three sentences.

"Download Cursor. Open the app and sign in. Then pick a folder and start with a small task."

The installer is on cursor.com/download. The download page says the desktop app is available for macOS, Windows, and Linux. The operating-system requirements are on the Quickstart, and they differ by machine.

• Mac: macOS 12 (Monterey) or later. The installer is a native .dmg. The Quickstart lists Apple Silicon and Intel.
• Windows: Windows 10 or later. The installer is a native .exe.
• Linux: the Quickstart calls Debian and Ubuntu the recommended path, and it prints terminal commands. RHEL and Fedora get a separate set. An AppImage is the portable option.

On a Mac or a Windows PC, download the installer, open it, and sign in. The Quickstart does not name the account buttons, so use the sign-in the app shows. Then pick one folder, which is the next instruction on that page, and keep the first task small.

On Linux, the Quickstart's recommended commands for Debian and Ubuntu are these. They are copied from that page.

# Add Cursor's GPG key
curl -fsSL https://downloads.cursor.com/keys/anysphere.asc | gpg --dearmor | sudo tee /etc/apt/keyrings/cursor.gpg > /dev/null

# Add the Cursor repository
echo "deb [arch=amd64,arm64 signed-by=/etc/apt/keyrings/cursor.gpg] https://downloads.cursor.com/aptrepo stable main" | sudo tee /etc/apt/sources.list.d/cursor.list > /dev/null

# Update and install
sudo apt update
sudo apt install cursor

RHEL and Fedora, again from the Quickstart:

sudo tee /etc/yum.repos.d/cursor.repo << 'EOF'
[cursor]
name=Cursor
baseurl=https://downloads.cursor.com/yumrepo
enabled=1
gpgcheck=1
gpgkey=https://downloads.cursor.com/keys/anysphere.asc
EOF

sudo dnf install cursor

The portable AppImage is the third option. The Quickstart says to download the .AppImage from cursor.com/downloads, which currently opens the same download page, then:

chmod +x Cursor-*.AppImage
./Cursor-*.AppImage

The Quickstart prefers the apt and yum packages over the AppImage. The reason it gives is concrete.

"The apt and yum packages are preferred over AppImage. They provide desktop icons, automatic updates, and CLI tools."

Those commands need a terminal and permission to install software. If you do not have that permission on the machine, the .dmg or the .exe on a computer you do administer is the path the Quickstart actually spells out for Mac and Windows.

Signing in is where the plan appears. The monthly prices below are the ones printed on cursor.com/pricing, checked October 5, 2026. The page also has a yearly toggle. A yearly dollar figure is not printed beside these monthly ones, so none is listed here.

Plan	Price on the page	What the card lists
Hobby	Free	No credit card required. Limited Agent requests. Access to Composer.
Individual	$20 / mo.	Everything in Hobby, plus extended limits on Agent, generous limits for Grok, access to frontier models, Grok Bot access, MCPs, skills, and hooks, cloud agents, and Bugbot on usage-based billing. The card names Pro, Pro+, and Ultra. A separate monthly price for Pro+ or Ultra is not printed.
Teams	$40 / user / mo.	Everything on Individual, plus centralized billing and administration, a team marketplace for internal rules, skills, and plugins, cloud agents and automations with shared team context, Grok Bot access, agentic code reviews with Bugbot, usage analytics, team-wide privacy mode, and SAML/OIDC SSO. The card names Standard and Premium. A separate Premium price is not printed.
Enterprise	Custom	Everything on Teams, plus pooled usage, invoice and PO billing, SCIM seat management, repository, model, and MCP access controls, auto-run, browser, and network controls, audit logs and service accounts, an AI code tracking API, access, network, and audit controls for Grok Bot, and priority support and account management.

Hobby is the plan that starts without a card. The card calls the Agent allowance "Limited Agent requests" and does not print the number. The next monthly price the page does print is Individual at $20 a month. Do not fill the blank with a guess.

The button under the Individual card reads "Get Pro." Pro, Pro+, and Ultra are names on that same card, next to the single printed price of $20 a month. Cursor's FAQ recommends two of those names and still does not attach dollars to them.

"We recommend Pro+ for daily agent users, and Ultra for agent power users."

The same FAQ says the Teams plan is for people collaborating, and Enterprise is for organizations that need invoicing, pooled usage, or advanced security. A first folder does not require either.

Two more lines from that FAQ belong next to the table, because both of them are easy to over-read. Every plan includes a set amount of model usage. On-demand usage lets you continue after that amount, billed in arrears. The FAQ does not print the included amount. And prices are exclusive of applicable taxes.

The FAQ's answer to how Cursor uses your data is short enough to quote whole. The Security page is the link that answer names.

"Privacy mode can be enabled in settings or by a team admin. When it is enabled, we guarantee that code data is not used for training by us or our model providers."

Turn that on in settings if you want it, including on a team where an admin can set it. This page does not add a claim past that sentence.

Ask Agent to explain the folder

With the folder open, the Quickstart says to open Agent with Cmd+I. The same key graphic on that page shows Ctrl+I as the alternate shortcut. Paste the prompt the Quickstart prints.

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

The Quickstart says what comes back.

"Cursor will search your repo, read relevant files, and summarize how the project fits together."

Read the summary before you ask for an edit. "Entry points" and "modules" are the docs' words for where the folder starts and how the pieces split. If a name in the summary is unfamiliar, ask which file holds the words a visitor actually sees, or the heading you already know from the live page. The first change should land in that file. A summary that points at a payments file, a sign-in file, or a deploy file is a map, not an invitation to edit those files today.

Change one low-risk thing

Once the summary makes sense, the Quickstart's next prompt asks for options and then waits.

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

The Quickstart names the kind of task it considers a good first one.

"Good first tasks are low risk, like improving some copywriting or fixing small UI issues."

Use that bar on the three suggestions. Pick the one that changes wording, layout, or a small visual fix. If one of them touches payments, sign-in, or a deploy step, leave it. You are choosing among the three, and the prompt told the app to wait until you do. Reply with the one you want, and say to leave the other two alone.

The Quickstart also covers the case where you already know the edit. Ask for it directly and describe the result you want. One sentence is enough: change the headline to the sentence you already wrote, and do not edit any other file. A vague "make it better" is how a small task becomes a tour of the folder.

Review the diff and run the checks

The Quickstart says you can watch the work, and that the diff view shows the changes the agent made. Read it before you keep anything. The lines on screen should be the change you picked. A headline edit that also rewrites a config file, a lockfile, or a script you did not mention is a different task. Say so, and do not keep that diff.

Then ask for the checks the project already uses. The Quickstart names them.

"When it finishes, review the diff and ask Cursor to run the checks your project already uses. That can mean tests, the type checker, linting, or a local build."

Point at the command the folder already has, if you know it, or ask Agent to run whichever of those four the project already contains. If the folder has no tests, no linter, no type checker, and no build, stop there. Do not ask for a new test framework, a new linter, or a new build setup. A new toolchain is a second project, and it is no longer the one small change.

Keep the edit only after both checks are done: the diff matches the request, and any check the folder already had has been run. If a check fails, ask Agent to fix the failure from that check. If the failure sits in payments, sign-in, or deploy, do not keep the edit. Widening the task to reach those files is how a copy change becomes a release.

Turn on Plan Mode for bigger work

The one small change does not need Plan Mode. The Quickstart brings it in after the basics, for work that spans multiple files, needs research, or needs an approval before any code is written.

Press Shift+Tab in the agent input. The Quickstart says that toggles Plan Mode, and that Cursor will do four things instead of writing immediately:

1. Research your codebase to find relevant files.
2. Ask clarifying questions about your requirements.
3. Create a detailed implementation plan.
4. Wait for your approval before building.

Answer the questions in plain language. Read the plan the same way you read the diff: look for payments, sign-in, and deploy, and look for files you did not mean to touch. Approve it when the plan is still the change you asked for. The Quickstart's rule on this step is the wait. It does not build until you approve.

If the plan is larger than you wanted, do not approve it. Ask for a smaller plan, or go back to the single-file edit. Plan Mode is the brake for a bigger task. It is not a reason to start with a bigger task.

Leave when the job has no files

Stay when the job is to edit files in a folder you own. The session is the Quickstart's session: explain the folder, change one low-risk thing, review the diff, run the checks the folder already has. Plan Mode is the later step, for a change that no longer fits in one file.

Leave when the job has no folder. A question, a search, or a draft that does not have to land in a file is a different product. ChatGPT is the chat entry in this directory. Perplexity is the research entry. This walkthrough does not treat the desktop app as a substitute for either of them when there is nothing to open.

The job	Where it goes
Edit files in a folder you own	Cursor. Explain the folder, change one low-risk thing, review the diff.
The change spans many files and you want a plan first	Plan Mode in the same app. Shift+Tab, then approve before it builds.
A question or a search, and no files to edit	ChatGPT or Perplexity.

Download the app, sign in, and open the folder you already have. The rest of the session is the Quickstart. Prices, including the ones this page left blank, stay on the pricing page. The directory note is /tools/cursor.