What is Cursor? Cursor is an AI-native code editor: a fork of Visual Studio Code rebuilt from the ground up around artificial intelligence. Instead of bolting an assistant onto a traditional editor, Cursor weaves AI into the core editing loop with features like Tab (predictive multi-line completion), inline edits, a multi-file Composer, an autonomous Agent, and a chat panel that understands your codebase. The result feels familiar to anyone who has used VS Code, but the day-to-day workflow is faster and more conversational. This guide explains what Cursor does, who it is for, its core features, and how it differs from plain VS Code and from terminal-based agentic tools. (Cursor Drops is an independent project that tracks Cursor releases. It is not affiliated with Cursor or its maker, Anysphere.)
What is Cursor, exactly?
Cursor is a desktop code editor made by Anysphere. Because it is built on the open-source core of VS Code, your existing extensions, themes, keybindings, and settings largely carry over, which makes the switch low-friction. What sets Cursor apart is that AI is treated as a first-class part of the editor rather than a side panel. As you type, Cursor predicts your next edit. When you describe a change in plain language, it edits the relevant files for you. When you hand it a larger task, an agent can plan and execute across your project, run commands, and iterate against the results.
In short, Cursor keeps the editor you know and changes how you interact with it. You spend less time typing boilerplate and navigating files, and more time describing intent and reviewing diffs. For the authoritative description of how each feature works, the official Cursor documentation is the source of truth, since the product evolves quickly.
Core features of Cursor
Cursor's value comes from a handful of tightly integrated capabilities. Exact names and behaviors can shift between releases, so treat the descriptions below as durable concepts and check the docs (or the Cursor changelog) for current specifics.
- Tab is Cursor's predictive autocomplete. Rather than completing a single token, it suggests multi-line edits and can predict your next move across a file, so you accept changes by pressing Tab repeatedly as you work.
- Inline edit lets you select a block of code (or place your cursor), describe the change in natural language, and have Cursor rewrite it in place. It is ideal for focused, surgical edits without leaving the editor.
- Composer is a multi-file workspace for larger changes. You describe a feature or refactor, Cursor proposes edits across several files at once, and you review them together before applying.
- Agent takes things further: it can autonomously work through a task, reading files, making edits, running terminal commands, and reacting to output until the goal is met. You supervise and approve as it goes.
- Chat is a conversation panel with codebase awareness. You can ask questions about your project, reference specific files or symbols, and get answers grounded in your actual code.
- Codebase context ties it together. Cursor indexes your project so its suggestions, answers, and edits reflect your real files, conventions, and structure rather than generic snippets.
Who is Cursor for?
Cursor suits a broad range of developers, but it shines for a few groups in particular. If you already live in VS Code, Cursor is the most natural on-ramp to AI-assisted coding because the editor feels identical while the workflow gets supercharged. If you value staying inside a graphical editor (with your debugger, source control panel, and extensions one click away), Cursor keeps you there rather than pushing you to the terminal.
- VS Code users who want AI deeply integrated without relearning their editor.
- Full-stack and front-end developers who do a lot of hands-on editing, prototyping, and rapid iteration.
- Developers new to AI coding who want a gentle learning curve and visible, reviewable changes.
- Teams standardizing on a shared editor, where a familiar VS Code base lowers onboarding cost.
It is less of a fit if you strongly prefer a terminal-first or headless workflow, or if you want to script an AI agent into CI pipelines and repeatable automation. Those use cases lean toward command-line agentic tools, which we cover in the comparison below and in our guide on Claude Code vs Cursor.
How Cursor differs from VS Code and agentic CLIs
Two comparisons come up constantly when people ask what is Cursor and whether they need it. The first is against plain VS Code; the second is against terminal-based agentic tools. The table below summarizes the practical distinctions.
| Dimension | Cursor | Plain VS Code | Agentic CLI |
|---|---|---|---|
| Form factor | AI-native GUI editor (VS Code fork) | General-purpose GUI editor | Terminal-first agent (command line) |
| AI integration | Built into the core editing loop | Added via extensions, if any | The agent is the product |
| Primary interaction | Tab, inline edits, Composer, chat | Manual editing plus extensions | Natural-language prompts that drive autonomy |
| Best at | Fast in-editor editing and reviewing diffs | A neutral, extensible base editor | Autonomous multi-file work and scripting |
| Extensions | VS Code ecosystem mostly carries over | Full VS Code Marketplace | Hooks, MCP, shell composition |
| Made by | Anysphere | Microsoft | Varies by tool |
Against plain VS Code, the difference is depth of AI integration. You can install AI extensions in VS Code, but Cursor designs the whole experience around AI, so Tab prediction, inline edits, and codebase-aware chat feel cohesive rather than bolted on. Against agentic CLIs, the difference is form factor: Cursor keeps you in a graphical editor where you edit alongside the AI, while a terminal-first agent is built for the dispatch-and-review loop and composes naturally with shell, git, and CI.
Pricing and models (high level)
Cursor offers a free tier plus paid plans, and a key selling point is model flexibility: it lets you choose among multiple model providers in-app rather than locking you to one vendor. Paid tiers generally raise usage allowances and unlock heavier or background-agent work, with team seats priced per user. Specific dollar amounts, request limits, and the exact roster of available models change regularly, so confirm current details on Cursor's official pricing and documentation pages before you budget.
Bottom line and how to stay current
So, what is Cursor? It is an AI-native code editor that keeps the familiarity of VS Code while rebuilding the editing experience around AI: Tab predictions, inline edits, a multi-file Composer, an autonomous Agent, and codebase-aware chat. It is a strong choice if you want an augmented graphical editor, especially if you already know VS Code, and it sits alongside (rather than fully replacing) terminal-first agentic tools.
Cursor ships updates frequently, so the most reliable way to keep your mental model accurate is to follow its release notes. You can read the official Cursor docs directly, or let the independent Cursor Drops app surface and summarize new releases and push you a notification when one drops. Browse the Cursor changelog to see what has shipped recently, grab the app on the App Store, or read our guide to Cursor's new features to go deeper.
Sources
Maintainer, Claude Drops
Ian builds Claude Drops and reads every Claude Code release so you don't have to. He writes plain-English guides to Claude Code's features, drawing directly from the official changelog and documentation.