An AI-native code editor built as a fork of VS Code, designed around the idea that code editing should be a conversation with an AI model. Cursor integrates LLMs deeply into the editing experience: inline code generation, multi-file editing, codebase-aware context, and natural language commands. It's part of the broader AI coding assistant wave alongside GitHub Copilot, Windsurf, and Claude Code.
Why it matters
Cursor represents a bet that AI will fundamentally change how code is written — not just autocomplete suggestions, but AI as a collaborator that understands your entire codebase. Its rapid adoption (millions of users within a year) and the productivity gains reported by developers make it one of the most tangible examples of AI changing knowledge work today.
Deep Dive
Cursor's technical approach centers on context: the editor indexes your codebase, identifies relevant files and symbols, and includes them in prompts to the LLM. This codebase-awareness is what separates it from generic chat interfaces — when you ask "refactor the auth module to use JWT," Cursor knows which files contain the auth module, what the current implementation looks like, and what other files depend on it.
The Editor vs. Plugin Debate
Cursor's decision to fork VS Code (rather than building a plugin) was controversial but strategic. A fork lets them deeply integrate AI into the editing experience — custom keybindings, inline diff views, AI-aware file navigation — in ways that a plugin's limited API surface doesn't allow. The trade-off is maintaining compatibility with VS Code's extension ecosystem while diverging on core features. Competitors like GitHub Copilot and Claude Code take different approaches: Copilot as a VS Code extension, Claude Code as a terminal-based tool.
