Cursor
An AI-first IDE — VS Code fork with deep agent integration. Edit-with-AI, tab completions, repo-aware chat.
Mindmap
The plain-English version
Cursor is an IDE built around AI coding. A fork of VS Code with custom features: in-line chat, multi-file edits, tab-completion driven by an LLM, codebase-aware chat that can search and reason across the whole project. Subscription-based; works with multiple model providers.
The problem it solves
If you live in an editor and want AI woven into every interaction (not a separate chat window), Cursor's UX is hard to beat. The Composer multi-file edit flow, the in-line edit mode, and the tab autocomplete all reduce friction. AI-first IDE has become a category, with Cursor leading.
Alternatives
| Alternative | Type | When it wins |
|---|---|---|
| Claude Code | CLI agent | Anthropic's CLI coding agent. Runs in your terminal, in your repo, with full project context. |
Deep links
The words you'll hear
- Composer
- Multi-file edit mode. Specify the change; Cursor edits across files.
- Tab autocomplete
- Aggressive next-line predictions. Press Tab to accept.
- @ symbols
@file,@codebase,@docs— pull context into chat.- Cmd-K / Cmd-L
- Inline edit / chat toggle. Muscle memory builds fast.
- .cursorrules
- Project-level instructions, similar to CLAUDE.md.
- Apply / Reject
- Review each suggested edit before it lands.
Bad vs. good prompt for Cursor
Why it works: Specifies the library, the file structure, the exact handler to touch, the bound (don't touch others), and the verification step. Cursor's Composer handles this cleanly with these constraints.
What bites real teams
Autocomplete fills in plausible-looking code that's slightly wrong. Read what you accept.
Without scope constraints, Composer will rewrite more than you wanted. Always specify what to leave alone.
Without project rules, the AI re-discovers conventions each session. Set them up early.