wbmeet

Installer Cursor et utiliser le mode Agent : connexion et premier diff relisible

Installer Cursor, mode Agent, un changement relisible dans le dépôt.

La première heure avec Cursor Agent dans l’éditeur bloque surtout sur l’absence d’install desktop depuis cursor.com, l’absence de connexion Cursor, ou le fait de rester en chat read-only au lieu du mode Agent.

The query is utiliser le mode Agent de Cursor dans l’éditeur. This page follows Cursor docs at cursor.com/docs, cursor.com/docs/get-started/installation, and Agent overview material (e.g. cursor.com/docs/agent/overview—paths may shift). For the terminal agent CLI, see our Cursor CLI Agent note. This is IDE Agent only, not a meeting-product guide.

Install CursorSign in + open repoAgent task + diff

What Agent does in Cursor

Cursor is an AI code editor built on VS Code. Agent in the sidebar can read your workspace, propose multi-file edits, and run terminal commands after you approve (exact prompts depend on your build). Ask is for read-only exploration; Plan helps break large work into steps (labels and shortcuts follow official docs, often a mode picker or Shift+Tab). Usage, models, and billing show in your Cursor account—trust cursor.com pricing pages.

Agent
Repo tasks
Ask
Read-only
git diff
Review edits

Install the Cursor desktop app

  1. 1

    Download from the official site

    Go to cursor.com/download and pick macOS, Windows, or Linux. On Linux, follow the installation page for AppImage, .deb, or your package manager.

  2. 2

    First launch and updates

    Start Cursor after install. Use Check for Updates (often under Help) to stay current. If you migrate from VS Code, you can import extensions and keybindings; for hour one, let Cursor Agent own file edits so other AI extensions do not fight it.

  3. 3

    Not the CLI

    This page is in-editor Agent. Terminal workflows use the agent binary—see our Cursor CLI install guide. IDE and CLI usually share one Cursor login but are different entry points.

Sign in to Cursor

  1. 1

    Start sign-in

    On first run, choose Sign in and complete OAuth in the browser with your Cursor account. Check Settings → Account (label may vary) for status.

  2. 2

    Plan and models

    Trials and Pro/Business limits show in your account UI. Available Agent models change with product updates—use the in-app model picker, not blog guesses.

  3. 3

    Sign out when switching

    Sign out from Account before using another identity. Do not share session links or tokens.

Open the repo and enter Agent mode

  1. 1

    File → Open Folder

    Open the root of a Git repo you own. Run git status in the integrated terminal (Ctrl+` / Cmd+`) before the agent edits files.

  2. 2

    Open the Agent panel

    Use the Agent/Chat icon or the shortcut from cursor.com/docs. Select Agent mode—not Ask—if you want file writes in hour one.

  3. 3

    Attach context with @

    @ one file, folder, or docs entry instead of the whole monorepo. Start with an entry file or README.

First reviewable repo task

  1. 1

    Prompt one: read-only

    Example: “In three sentences, explain the main exports of @this file.” Confirm paths match disk.

  2. 2

    Prompt two: small diff

    Example: “Add a unit test for one untested helper; show the patch before applying.” Accept or reject hunks—avoid Accept All on the first run.

  3. 3

    Approve commands carefully

    When Agent proposes npm test or pytest, read the command and output before Allow/Run. Finish with git diff; use git restore if the change is wrong.

# First hour · Cursor Agent · editor · 2026-10-13
# cursor.com/download → Sign in
# File → Open Folder (your git repo)
# git status
# Agent mode → @ one entry file
# Prompt 1: explain exports (read-only)
# Prompt 2: one unit test; show diff first → git diff

Mode comparison

ModeGood forFirst-hour note
AgentMulti-step edits + commandsRead diff and commands first
PlanLarge featuresPlan before big refactors
AskExplain, searchAsk then Agent works well
CLI agentTerminal, CISeparate CLI guide
01

Agent never writes files

Confirm Agent mode (not Ask); check workspace trust; see if edits were rejected.

02

Too many files touched

Narrow @ scope; ask for one file; use Plan to split work.

Suggested path: official install → sign in → Open Folder → Agent → read-only prompt → small diff + git diff. Trust cursor.com/docs for your version.

Vs Cursor CLI
Editor Agent gives graphical diffs and @ file tree; CLI fits SSH and scripts. See Cursor CLI Agent.
Pro required?
Trials and paid tiers are defined on cursor.com—this page does not guarantee free Agent quota.
Scope of this page
Only Cursor editor Agent’s first hour. wbmeet on this site is a different product.

Questions à vérifier

Is Cursor just VS Code?

Cursor is a separate app that can import VS Code settings. Agent is built into Cursor, not a typical Marketplace-only extension name.

Will Agent git push for me?

It should not push without your workflow; git commands run only after approval. Commit yourself in hour one.

Must the first task be a test?

No. Any small reversible change counts—doc fix, validation, or one test—as long as you review with git diff.

Does private code leave my machine?

Follow Cursor’s official privacy and data docs; enterprise controls may apply. Read policy before Agent on sensitive repos.

Démarrer une réunion gratuite