Issue #1: Copilot goes usage-based, Claude Code keeps winning hearts, Cursor ships hard

The week ending June 9, 2026 gave us a complete picture of where this race actually stands. GitHub Copilot flipped its pricing model — same move that burned Cursor users a year ago — while Claude Code quietly released a stat that should make every developer team rethink their tool stack. Cursor, meanwhile, shipped real engineering substance in 3.7.

Here's who got better, in what area, and whether any of it changes the calculus on switching.

Copilot's week had two stories, and they pull in opposite directions.

The good story: at Microsoft Build 2026 on June 2, GitHub launched the Copilot App — a standalone desktop application that turns Copilot from an in-editor suggestion engine into a multi-agent orchestrator. Each agent session runs in its own isolated git worktree, a "My Work" dashboard surfaces all parallel sessions at once, and a new Agent Merge feature handles the CI monitoring / review cycles / auto-merge loop automatically. For teams already deep in the GitHub ecosystem, this is genuinely meaningful: the workflow (issue → agent session → PR → merge) is now fully automatable without leaving Copilot.1

The bad story: on June 1, Copilot moved from flat-rate subscriptions to usage-based billing.2 This is the same structural change Cursor made in June 2025 — the one that triggered surprise overage bills, a community revolt, and a public apology from Cursor on July 4, 2025. Copilot is now walking the same path.3 r/GithubCopilot lit up with posts calling it the "end of an era." Based on what happened to Cursor's community twelve months prior, that reaction is not overblown.4

The gap between Copilot's product ambitions and its developer sentiment numbers is hard to ignore. In the February 2026 Pragmatic Engineer survey of 15,000 developers, only 9% of senior developers named Copilot their favorite tool — despite it holding 29% workplace adoption and sitting in 90% of Fortune 100 companies.5 Copilot is everywhere because procurement bought it. Developers tolerate it.

Verdict: The Copilot App is the most interesting thing Copilot has shipped in a year. But announcing it the same week you flip to usage-based billing is a rough combination. Watch the overage complaint threads over the next 30 days — that's where this lands.

This week, Anthropic published internal data showing that more than 80% of code merged into Anthropic's own codebase is now authored by Claude — and engineers are shipping eight times as much code per day as they were before.6 On the hardest, least-specified coding tasks, Claude succeeded 76% of the time in May 2026 — up 50 percentage points in six months.7

There's an obvious caveat: Anthropic is both the developer and the vendor, so this is not an unbiased benchmark. But a few things make it less dismissible than it first appears. First, the paper acknowledged Claude-written code was "somewhat worse" than human-written code in late 2025 and is at rough parity today — that's not the language of a company writing a press release. Second, independent testing from Builder.io found Claude Code uses roughly 5.5x fewer tokens than Cursor on identical tasks, a consistency-of-pattern that held across multiple test scenarios.8

The satisfaction data backs the quality story: 46% of senior developers in the Pragmatic Engineer survey named Claude Code their favorite tool — the highest of any tool, by a large margin.9 It also reached $2.5B ARR from a standing start in nine months, the fastest ramp in AI coding tool history.

The downside is structural, not capability-based. Claude Code has no visual diff. There's no built-in approval workflow. If your team needs to see before they merge — which most enterprise teams do — Claude Code is harder to sell internally than Cursor. That's a real constraint, not a marketing problem.

Verdict: Claude Code is pulling further ahead on capability and developer trust. The 80% number is marketing-adjacent, but the directional story is solid. If you're not currently using it for complex multi-file work, the cost of not trying it is getting higher each month.

Cursor 3.7 shipped three meaningful updates this week.10

The SDK (version 0.1.6) now supports custom tools via local.customTools — developers can expose their own functions to the agent through a built-in MCP server without standing up a separate stdio server. Nested subagents are now fully supported, meaning a reviewer subagent can spawn a test-writer subagent and so on, with each level maintaining its own prompt and model. Auto-review routing lets you define natural-language policies for which tool calls require human approval and which run automatically — a step toward the autonomous-but-auditable sweet spot that enterprise teams want.

Design Mode got two additions: multi-element selection (click multiple UI elements, ask the agent to make them consistent) and voice input that queues changes while an agent mid-run, so you're not blocked waiting.

None of this is minor. Cursor is shipping serious engineering depth.

The pricing picture is messier. The June 2025 credit-based switch (Pro at $20/month with a $20 credit pool, Ultra at $200 with a $400 credit pool) still generates complaints. Developers who default to manually selecting Claude Opus burn through Pro credits in roughly two weeks. Teams trying to budget Cursor at 10 or 25 people face wide cost variance — $450-600/month and $1,200-1,800/month respectively, before factoring in heavy usage.3 The Facebook group post asking "what are you switching to?" after the pricing change still has active replies.

The multi-model flexibility is Cursor's real structural advantage: you can route between Cursor's own model, Claude, and GPT-4 based on task. No other tool in this comparison offers that directly. For teams with mixed task types — some needing speed, some needing depth — that matters.

Verdict: Cursor is the best IDE-native experience in this category, full stop. The feature gap between Cursor and its competitors has been closing; the pricing predictability gap has not.

The week's clearest loser on optics: GitHub Copilot, launching usage-based billing the same week it needs developers to trust its agent-mode ambitions. The week's clearest winner on substance: Cursor shipped tangible engineering depth. The ongoing winner on every metric that matters for actual code quality: Claude Code.

From Copilot to anything: If you're on Copilot because IT chose it, and you haven't tried Claude Code for a complex multi-file refactor, do that this week. The satisfaction delta is real. Usage-based billing makes this the right moment to reassess the TCO.

From Cursor to Claude Code: Not an either-or. The evidence from 70% of senior developers is that you run both — Cursor for interactive daily editing, Claude Code for heavy architectural work. If you're on Pro and burning through credits, try Claude Code Pro at $20 for the tasks eating your Cursor budget.

Staying put: Copilot at $10/month flat-rate (before the billing change lands on your invoice) is still the cheapest entry point if you're not doing agentic work. Once you are, the $10 price advantage evaporates quickly.