Getting Started with Cursor: Install, Configure, Tab Completion & Agent Guide

What Cursor is

Cursor is an AI‑enhanced code editor that combines a VS Code‑style interface with AI code completion, chat, and an Agent that can edit files and run commands.

Core capabilities

Automatic code completion

Project explanation

Inline code modification

On‑demand function generation

Test generation

Cross‑file edits via the Agent

Error diagnosis assistance

Installation

Download the installer from https://cursor.com/download and select the package for macOS, Windows, or Linux. macOS offers Apple Silicon, Intel x64, and Universal builds. Run the installer and launch Cursor.

First launch configuration

On first launch Cursor guides you through keyboard shortcut style, theme, terminal preferences, account login, and optional import of VS Code settings. Importing VS Code configuration preserves existing theme and shortcuts.

Ctrl + Shift + P
Search:
Cursor: Start Onboarding

Opening a project

Open a real project via File → Open Folder or from a terminal with: cursor . Cursor indexes the codebase; progress is visible in the “Indexing & Docs” settings.

Tab completion

Start typing code (e.g., function calculate) and accept gray suggestions with Tab. Tab can complete multiple lines, function parameters, bodies, repeated logic, and related changes in adjacent files.

Inline edit (Ctrl + K)

Select a snippet, press Ctrl + K, type a natural‑language request such as “add null‑check to this function” or “make this code more concise without changing logic”, then press Enter to apply. Suitable for localized edits.

Chat (Ask mode)

Open the Chat panel (default shortcut Ctrl + I) and ask questions like “where is the entry file?”, “explain this module’s call chain”, or “what could cause this error?”. Ask mode is read‑only and intended for project understanding.

Agent modes

Ask – read‑only exploration, suitable for understanding code, asking questions, and planning.

Agent – can edit multiple files and run commands; used for feature development, bug fixing, and refactoring.

Custom – configurable tools and commands for bespoke workflows.

Recommended beginner sequence: Ask → Inline Edit → Agent.

Using the Agent to generate code

Example request: “add unit tests for this function and run them.” The Agent will:

Read the relevant source files.

Locate the test directory.

Create or modify test files.

Execute the test command.

Iterate based on any failures.

Agent‑generated code must be reviewed before merging.

Project rules

Define rules in .cursor/rules (or legacy .cursorrules) to guide the AI. Rules are version‑controlled and can be shared across a team.

.cursor/rules
- Use pnpm, not npm.
- Run pnpm lint after TypeScript changes.
- Do not add dependencies unless explicitly requested.
- Preserve existing directory structure.

Safety boundaries

Never paste .env files, keys, or tokens into the AI.

Avoid uploading customer‑private data.

Do not let the Agent execute dangerous commands.

Run tests after modifying core logic.

Review diffs before merging.

Comply with team security and compliance policies.

Recommended beginner workflow

Download & Install Cursor
→ Log in
→ Import VS Code config
→ Open a local project
→ Wait for indexing
→ Ask about project structure
→ Use Tab for completion
→ Ctrl + K for small edits
→ Agent for a small cross‑file task
→ Review diff and test results

Key entry points

Tab – everyday code completion.

Ctrl + K – localized inline edits.

Ask – project understanding and Q&A.

Agent – cross‑file development and automation.

Rules – codify project conventions for the AI.