Cursor CLI Agent installieren: Anmeldung und erste Repo-Aufgabe

Offizielles Install-Skript, agent login, ein prüfbares Diff im Repo. Cursor-Konto nötig.

The first hour with Cursor Agent in the terminal usually breaks on PATH, skipping agent login, or never landing a reviewable diff. Install the official agent binary, sign in, then change one small thing in a repo you own.

The query is how to install and use Cursor CLI Agent. This page follows Cursor docs at cursor.com/docs/cli/installation, cursor.com/docs/cli/overview, and cursor.com/docs/cli/reference/authentication. It is Cursor’s terminal agent, not this site’s meeting product. To walk a diff on a short call, open a room on wbmeet; see how to create and join a room.

What Cursor CLI does

Cursor CLI lets you work with an AI agent in the terminal: read files, propose edits, and run commands (with sandbox controls). Run agent interactively, or use non-interactive flags such as agent -p "…" in scripts. Default mode is Agent; /plan or Shift+Tab switches to Plan, and /ask is read-only. Usage and models follow your Cursor account plan—see official pricing.

Install Cursor CLI

1. 1

   Run the official installer

   macOS, Linux, WSL: curl https://cursor.com/install -fsS | bash. Native Windows PowerShell: irm 'https://cursor.com/install?win32=true' | iex. Add ~/.local/bin to PATH per the installation page (bash/zsh profile + source).

2. 2

   Verify

   New terminal: agent --version. command not found means PATH is missing $HOME/.local/bin—this is the standalone CLI, not only the IDE integrated terminal.

3. 3

   Optional manual update

   The CLI tries to auto-update. Run agent update when you want to pull the latest build explicitly.

Authenticate: browser or API key

1. 1

   Browser login (recommended)

   agent login opens your browser to sign in with your Cursor account. Set NO_OPEN_BROWSER=1 to print the URL for headless machines. agent status should show you as authenticated.

2. 2

   API key (scripts/CI)

   Create a user API key in Cursor Dashboard → API Keys. Export CURSOR_API_KEY or pass --api-key once. Never commit live keys.

3. 3

   Switch or sign out

   agent logout clears stored credentials. Billing and model access follow your subscription—official Cursor docs are the source of truth.

First task in your repo

1. 1

   cd to the repo root

   Work in a Git repo you own. Run git status before the agent edits files.

2. 2

   Start a session

   Run agent, or agent "explain the entry module in one paragraph". On large trees, start with /ask or read-only questions.

3. 3

   Land a reviewable change

   Follow up with a concrete ask: add a unit test for one untested helper or input validation on one public function—show the diff first. Read git diff line by line. Use agent resume to continue context.

# First hour · Cursor CLI · 2026-09
curl https://cursor.com/install -fsS | bash
agent --version
cd /path/to/your/project
agent login
agent
# task: one unit test; show diff first

Modes and pitfalls

Official path: curl install → agent --version → agent login → agent in your repo → review diff. Trust cursor.com/docs/cli for details.

Vs Claude Code / Copilot CLI

Different install and auth. See our Claude Code and Copilot CLI notes.

Cursor IDE required?

The CLI runs standalone; IDE and CLI share account login but are separate entry points.

Not a meeting-product guide

Only Cursor CLI’s first hour. Short call: wbmeet.

Questions worth checking