~/VibeHandbook
$39
≡
Read the BookReferencePhilosophyGet the PDFFAQ

AI Services

cursor.com ↗

Cursor

What it is

Cursor is an AI-first code editor built by Anysphere. It is built on a copy of VS Code, a popular free code editor, with AI added throughout. That means inline completions, a chat panel that knows your codebase, and an mode — a helper that can make changes across many files on its own. It connects to several underlying AI models (from Anthropic, OpenAI, and others), so you choose which one answers.

Strengths

  • Familiar VS Code experience with extensions and keybindings carried over.
  • Codebase-aware chat and editing — it reads and maps your whole project up front (indexing), so answers reference your actual code.
  • Fast inline autocomplete that predicts multi-line and multi-file edits.
  • Agent mode can plan and apply changes across files, then run commands.
  • Model choice: pick a different underlying model to match the task or budget.

Trade-offs

  • Usage-based pricing — you pay for what you use (the number of requests / how much the model works), not a flat all-you-can-use subscription. Heavy agent runs can quietly add up to a surprise bill. So watch your usage dashboard and set a spend limit.
  • Suggestions can be wrong or out of context; you still review every change.
  • Heavy indexing and AI features can feel sluggish on very large repos or weaker machines.
  • Being a separate editor, it lags slightly behind upstream VS Code releases.
  • Autocomplete can be distracting if you prefer to write code yourself.

Best for

Developers who want AI deeply integrated into a graphical editor — fast inline edits, codebase-aware chat, and agent-driven multi-file changes without leaving the IDE (Integrated Development Environment), the single app where you write, run, and fix code.

Vibe coding fit

Cursor suits vibe coding for people who prefer a visual editor over a : you can describe a change in chat, watch it edit the relevant files, and accept or reject diffs inline. The codebase indexing means you can refer to "the auth flow" or "this component" and it usually finds the right place. Concrete tip: add a project rules file (e.g. .cursor/rules) describing your stack, your conventions, and any "don't do this" constraints. Cursor feeds it into every request. So the agent stops re-introducing patterns you've already rejected.