Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-04-08 · source-backed
Cursor just admitted that code editing isn't the main event anymore.
Cursor 3 abandons its VS Code fork entirely. Not an extension. Not a theme. Gone. Rewritten from scratch in Rust and TypeScript as what Anysphere is calling an "agent orchestration platform." The default view when you open Cursor 3 isn't a code editor. It's a panel where you dispatch and manage swarms of AI agents running across local and cloud machines simultaneously.
This is the clearest signal I've seen that AI coding has outgrown the IDE paradigm. When the most popular AI code editor decides code editing should be a secondary view, something has shifted.
The timing connects directly to the harness engineering story. If OpenAI's team of three is shipping 1M LOC with zero human-written code, the tool you need isn't a better text editor. It's a better agent dashboard. Cursor's team apparently reached the same conclusion.
There's a cost story here too. Early Cursor 3 users are flagging costs. One developer spent $2,000 in two days. That's the agent orchestration tax: when you're running multiple agents in parallel across cloud compute, the meter spins fast. It also explains why Claude Code's terminal-based approach keeps gaining ground in the JetBrains survey data. A $20/month Pro subscription with a usage cap is a lot more predictable than dispatching cloud agent swarms.
The Rust rewrite matters for a separate reason. VS Code's Electron base was always a compromise. Performance ceilings, memory overhead, limited native OS integration. Cursor's bet is that agent orchestration needs lower-level control than a web browser runtime can provide. I don't know if that's right yet, but I respect the conviction of burning down your own VS Code fork to find out.
For builders: don't switch to Cursor 3 today. It's brand new and the cost model isn't clear. But start thinking about what your workflow looks like when the agent panel is the primary interface and the editor is the secondary one. That's where all of this is heading.
Each link below shares sources, entities, or timing with this story.
Codex competes with Claude Code / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Codex competes with Claude Code); both cover Anysphere, Claude Code, Cursor, Electron; overlapping topics (agent, code, cost, cursor, orchestration).
Codex competes with Claude Code / Shared entities / Same source / Shared topic / What happened next / Tension
Linked by a graph relationship (Codex competes with Claude Code); both cover Claude Code, Gone, IDE, VS Code; cite the same source (JetBrains survey data).
Codex competes with Claude Code / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Codex competes with Claude Code); both cover Claude Code, Cursor, Electron, IDE; overlapping topics (agent, code).
Windsurf uses Claude Code / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Windsurf uses Claude Code); both cover Cursor, Electron, IDE, Rust; overlapping topics (agent, code, cursor, editor).
Codex competes with Claude Code / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Codex competes with Claude Code); both cover Claude Code, Cursor, Editor, IDE; overlapping topics (agent, code, editor).
Linked by a graph relationship (Codex competes with Claude Code); both cover Claude Code, Cursor, IDE, VS Code; overlapping topics (agent, code, cursor).
OpenAI uses Claude Code / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (OpenAI uses Claude Code); both cover Claude Code, Cursor, IDE, Rust; overlapping topics (agent, cloud, code, orchestration).
Claude Code uses VS Code / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Claude Code uses VS Code); both cover Claude Code, Cursor, IDE, VS Code; overlapping topics (agent, code, editor, orchestration).