Is VS Code’s IDE Obsolete? Inside Cursor 3’s Agent‑Centric Redesign

What Cursor 3 Brings

Cursor 3 (code‑named Glass) is built from scratch with an agent‑management console as the primary view; the traditional IDE is relegated to an optional pane. Engineers can still write code, but the design assumes most time will be spent scheduling agents, reviewing their outputs, and deciding which tasks to publish.

The workspace supports multiple repositories by default, and both local and cloud agents appear in a unified sidebar that aggregates sessions from desktop, web, Slack, GitHub, and Linear. Cloud agents generate screenshots of their work, allowing engineers to inspect changes without pulling code locally.

The most prominent feature is Cloud Handoff , which lets a running agent session migrate from a laptop to Cursor’s cloud and back, ensuring continuous execution when the local machine is off.

“For the past forty years, software development paradigms were defined by code editors. Cursor 3 bets that supervising agents will soon outweigh editing files.”

Structural Shift

All major AI‑assisted development players agree that agents need a dedicated orchestration layer, but they differ on where that layer should live.

Anthropic – Claude Code : adopts a terminal‑first approach; the CLI is the orchestration surface, independent of any IDE.

OpenAI – Codex : bundles desktop apps, CLI, and a cloud UI, aiming for an omnipresent orchestration layer that is accessible from any interface.

Google – Antigravity : provides both a traditional editor view and a separate agent‑management view, treating them as equal priorities.

Cursor 3 follows Google’s hybrid model but makes the agent console the default view, positioning the IDE as a fallback.

The shift mirrors the evolution of cloud infrastructure control planes: SSH remains for debugging, while the management console becomes the primary decision‑making interface.

Implications for Developers

Model Choice Becomes Infrastructure

Cursor ships Composer 2 as the default model and allows switching to Claude, GPT‑5.4, or Gemini. Model selection is treated like choosing a database or cloud region, with token economics becoming a scaling concern.

Composer 2 pricing (as of March 2026) is $0.50 per million input tokens and $2.50 per million output tokens, lower than comparable Anthropic and OpenAI offerings.

VS Code’s Moat Is Eroding

Cursor originated as a VS Code fork, but Cursor 3’s agent‑centric design could diminish the importance of VS Code extensions if the new interface gains traction. JetBrains faces similar pressure as the primary interaction shifts from file editing to agent management.

Workflow Changes Lead to Role Shifts

Engineers will spend more time reviewing agent‑generated diffs, validating cloud‑generated screenshots, and managing PR workflows, moving the skill set toward platform‑ops and engineering‑management rather than pure coding.

“Software engineers’ roles are merging with application‑layer system‑operations responsibilities.”

Cursor’s December 2025 acquisition of the Graphite code‑review platform illustrates this transition: agents write code, Graphite reviews it, and engineers coordinate the two.

Future Outlook

The orchestration layer for AI coding agents is emerging as a new product category. The open question is whether the layer will live inside IDEs, outside them, or both. Anthropic and OpenAI favor independent tools; Cursor and Google favor integrated consoles. The outcome may shape developer tooling for the next decade, similar to how the cloud‑control‑plane battle defined today’s infrastructure leaders.

If the prediction holds, Cursor 3 could be one of the last traditional code editors, marking the end of an era where the editor was the central development artifact.

Code example

交流技术