Cursor Reached 5 Million Developers. VS Code Is Watching.

VS Code is still the dominant developer tool by every measure that matters: 75.9% daily usage in 2025, a massive extension ecosystem, deep integration with GitHub, and Microsoft's full engineering weight behind it. And yet, in the same year, Cursor — a three-year-old fork of VS Code built around AI-first workflows — grew 120% year-over-year to reach 5 million developers by May 2026, with 67% of Fortune 500 companies deploying it in at least one team.

That trajectory warrants attention. Not because VS Code is losing, but because Cursor's growth reveals something about what developers now expect from their tools.

What "AI-Native" Actually Means

Most IDE plugins and extensions add AI as a sidebar — a chat panel you invoke, a suggestion you can accept or dismiss. Cursor's model is different: it treats the codebase as the primary context for all AI interactions. Its Composer mode lets you make changes across multiple files simultaneously, referencing functions and data structures throughout the project rather than just the file you're currently editing.

The diff-level autocomplete doesn't just suggest line completions — it suggests multi-line refactors in the context of surrounding code, often anticipating the purpose of the change based on the function signature and adjacent code. Codebase-aware chat means you can ask "why does the auth middleware reject requests with this header?" and get an answer that has actually read your middleware implementation rather than giving a generic explanation of how JWT works.

These aren't features that fit cleanly into a plugin model. They require access to the full workspace state at the IDE level. That's why Cursor needed to be an editor, not an extension.

The VS Code Advantage That's Also a Constraint

VS Code's dominance partly stems from its extension ecosystem: over 50,000 extensions covering every language, framework, and workflow. Cursor inherits this entirely — it runs VS Code extensions natively, which eliminated most of the switching friction. A developer moving from VS Code to Cursor doesn't lose their theme, their language server, or their debugger configuration.

But that same backwards-compatibility creates constraints. VS Code's architecture was designed before large language models existed. The extension API reflects assumptions about what a "code suggestion" looks like that don't map well to multi-file generative edits. Microsoft has been adding AI capabilities through Copilot, but it's working within an architecture that wasn't designed for it.

Cursor, having forked VS Code at the base level, can instrument the editor's core in ways that extensions cannot. This is where its performance on multi-file tasks comes from — it's not a workaround; it's architectural access.

Zed: The Other Challenge

While Cursor competes on AI depth, Zed competes on fundamentals. The Rust-native editor launched v1.0 in April 2026, with startup times of 0.12-0.4 seconds (versus VS Code's 1.2-3.0 seconds) and idle memory usage of 142-200 MB (versus VS Code's 650 MB to 1.2 GB).

For developers running on MacBooks with 16 GB of RAM and a dozen browser tabs open, the memory gap is noticeable. Zed's 120fps rendering through GPU-accelerated text layout makes scrolling through large files feel categorically different from the browser-based rendering VS Code inherits from Electron.

Zed's extension model uses WASM-based sandboxing — smaller ecosystem than VS Code's, but more performant and more secure. Its AI integration runs through an open API rather than a vendor-specific implementation, which makes it easier to swap underlying models.

What Developers Are Actually Choosing

JetBrains' January 2026 AI Pulse survey found 18% of developers using Cursor at work and 18% using Claude Code — the command-line coding agent — at near-parity with each other but well below VS Code's base. GitHub Copilot remains the most widely deployed AI coding tool by absolute numbers, but its growth has slowed as alternatives gained traction.

The pattern emerging: Cursor dominates among teams doing greenfield development or working on large, complex codebases where multi-file context matters. Zed attracts developers for whom performance is a constraint — large monorepos, older hardware, or preference for lightweight tooling. VS Code remains the default for teams where standardization and plugin compatibility matter more than either AI depth or raw performance.

The Question for Microsoft

Microsoft has the resources to build what Cursor built — and has been moving in that direction with GitHub Copilot's increasingly deep VS Code integration. The challenge is that architectural decisions made in 2015 now constrain what's possible without a major rewrite.

The IDE wars aren't over, and VS Code isn't in danger of losing its plurality. But the definition of "best developer tool" is shifting from "most features and extensions" toward "most effective at AI-assisted development." That's a race where a small, focused competitor with architectural flexibility has advantages that market share and legacy don't offset.