The headline numbers look like a clear story: GitHub Copilot is winning. Four million-plus subscribers, 75% year-over-year growth, baked into the world's largest code host. It's the default choice for anyone with a GitHub account and a IDE.

But look closer and something strange is happening. Copilot's market share has dropped from 67% to 51% in under two years. Cursor — a $20-a-month VS Code fork — crossed $2 billion in annual recurring revenue with just over one million paying users. Claude Code grew 6x in the same period and consistently tops developer satisfaction surveys. The market leader isn't winning. It's being slowly encircled.

The Model Gap Closed. The Ecosystem Gap Didn't.

For the first 18 months of the AI coding wars, the differentiator was model quality. Claude was smarter. GPT-4 was broader. Copilot had GitHub's context. Developers argued endlessly about which model wrote better code.

That's largely over. The models have converged. When Cursor, Copilot, and Claude Code all use competitive underlying models — and all have access to Claude 3.5, GPT-4o, and their own fine-tuned variants — raw intelligence stops being the moat. What matters now is what you build around the model.

Cursor's entire bet was interface. Multi-file agentic editing, inline diffs, composable context windows, and a chat interface that actually understands your codebase structure. It won the developer-luxury vote: people who tried it didn't want to go back to Copilot, even at double the price. That's why its revenue outpaced its user count — users who switched brought their companies with them.

The Enterprise Trap

Copilot's subscriber count is real, but it's misleading. A significant chunk of those 4.7 million seats are enterprise licenses — thousands of developers at a single company, auto-deployed by IT departments, rarely used to their full potential. Enterprise software doesn't die; it just quietly accumulates inactive users.

Cursor and Claude Code spread the opposite way. Individual developers adopt them first — on their own machines, with their own money — and then the team notices. "Hey, what are you using?" becomes a cascade. That's a bottom-up adoption curve, and it's much harder to kill from the top down.

JetBrains' April 2026 developer survey put Claude Code at the top of the satisfaction charts: 46% of developers who tried it called it their primary tool. That's not a lead you'd bet against. Developers who love their tools evangelize. Developers with enterprise seat licenses stay quiet.

What Copilot Still Has

None of this means Copilot is in trouble. It has two things that are genuinely hard to replicate.

First, GitHub's integration surface. Copilot knows your pull requests, your issues, your repo history — not because it's smarter, but because it's already there. For organizations already living in GitHub, the data moat is real. The context advantage isn't in the model; it's in the ecosystem.

Second, Microsoft's sales machine. Enterprise deals move slowly but last years. Copilot is winning the IT procurement war even as it loses the developer sentiment war. Those are different battles, and right now they're being fought by different people.

The Real Prize: Team Context

Here's what the market share numbers miss: AI coding assistants are becoming team infrastructure, not individual tools. The value isn't in writing a single function better. It's in the cumulative context an AI builds about a team's codebase, conventions, and decisions over time.

That context is sticky. The longer a team uses one assistant, the more useful it becomes. Switching costs aren't about the monthly subscription — they're about everything the AI has learned. And in software, accumulated knowledge is the real moat.

That's why the race isn't really about individual developers. It's about which platform becomes the default team operating system for code. GitHub is trying to make Copilot that platform through integration. Cursor is trying it through product experience. Anthropic is trying it through model quality leadership. The battle will be decided by which company's bet on developer behavior is correct.

For individual developers, the good news: competition is keeping prices low and quality high. For teams, the calculus is harder. Pick a side, commit, and build the context. The real cost of an AI coding assistant isn't the subscription. It's what you lose by switching after two years of accumulated understanding.