Cursor 3 Ships a New Interface Built From Scratch, Bets Everything on Agents

Two weeks after shipping Glass as an alpha toggle and Composer 2 as a proprietary model, Cursor just made the agent-first interface official. Cursor 3 launched today, April 2, 2026, with an announcement post from co-founders Michael Truell and Sualeh Asif titled “Meet the new Cursor.”

The headline feature is the Agents Window, a new interface built from scratch that puts agent management at the center and pushes traditional file editing to a secondary role. You can try it right now: Cmd+Shift+P, then type “Agents Window.”

Cursor 3 agents sidebar showing tasks across multiple repositories

Why Cursor Built a New Interface

When Cursor started, the team forked VS Code instead of building a VS Code extension. That gave them control over the full editing surface. With Cursor 3, they went a step further and built the Agents Window from scratch, separate from the VS Code editor underneath.

The reasoning is straightforward. Engineers using Cursor today are juggling individual agent conversations, switching between terminals, windows, and tools, and trying to keep track of what each agent is doing across their codebase. The traditional file-tree-on-the-left layout wasn’t designed for that workflow. The Agents Window is.

The VS Code-based editor still exists. You can switch back to it at any time, or run both interfaces simultaneously. Cursor 3 adds a layer on top; it doesn’t replace what was already there.

What’s in the Agents Window

Multi-Workspace, Multi-Repo

The new interface is inherently multi-workspace. Your sidebar lists agents grouped by repository, so you can monitor work happening across several codebases at once. Both humans and agents can operate across different repos from the same window.

This is a direct response to how teams actually work. If you’re touching a frontend repo, a backend repo, and an infrastructure repo in the same sprint, Cursor 3 shows all of that in one place instead of making you open three separate windows.

Parallel Agent Execution

You can run multiple agents simultaneously, each working on a separate task. Agents appear in the sidebar with status indicators and truncated descriptions. Click into any agent to see its plan, code changes, terminal output, and generated screenshots.

Cloud agents are first-class citizens here. The sidebar surfaces agents kicked off from mobile, web, desktop, Slack, GitHub, and Linear alongside your local agents. Cloud agents generate demos and screenshots so you can verify their work without pulling code locally.

Local-to-Cloud Handoff

This is the feature that addresses a real pain point. You start an agent session locally, realize the task is going to take a while, and want to close your laptop. In Cursor 3, you can move that session to the cloud and let it keep running. When you’re back, pull the session back to your local machine for editing and testing.

The reverse works too. A cloud agent finishes a task overnight, and you pull it local in the morning to review the changes in your full development environment before committing.

Cursor’s own model, Composer 2, powers the default “Auto” mode in the model picker. The blog post describes it as having “high usage limits” for quick iteration. You can still select Claude, GPT, Gemini, or any other supported provider.

Design Mode

A new feature called Design Mode lets you annotate and target UI elements directly in the browser. Toggle it with Cmd+Shift+D, then click any element and describe what you want changed. You can select an area with Shift+drag, add elements to chat with Cmd+L, or add them to the input with Option+click. Point at a button and say “make this bigger” or “turn this red,” and the agent makes the edit.

Improved Diffs and PR Workflow

Cursor 3 includes a new diffs view for reviewing changes. The UI streamlines the path from staging to commit to pull request, with fewer clicks between reading a diff and merging it. The changelog also mentions faster large-file diff rendering with reduced memory consumption.

New Commands

Two notable additions: /worktree creates isolated git worktrees for agent tasks, keeping file conflicts between agents impossible. /best-of-n runs a task across multiple models in parallel and lets you compare the outcomes before picking one.

The Numbers Behind the Bet

Cursor published a separate post called The Third Era of Software Development that frames this launch with internal data:

Agent users now outnumber Tab (autocomplete) users 2 to 1. A year ago, Tab users outnumbered agent users 2.5x.
Agent usage grew over 15x in one year.
35% of pull requests merged at Cursor (the company’s own codebase) are now created by autonomous agents running in cloud VMs.

These numbers explain why Cursor is restructuring its entire product around agents. The usage shift already happened. Cursor 3 is the interface catching up to how people actually use the tool.

Anysphere By the Numbers

Cursor is built by Anysphere, founded in 2022 by four MIT students. The company has scaled at a pace that’s hard to overstate:

$2 billion annualized revenue as of February 2026, doubling from $1B in three months
$29.3 billion valuation from the November 2025 Series D ($2.3B raised, led by Accel and Coatue), with reports of a new round at $50-60 billion
Over 1 million daily active users and 1 million paying customers
67% of Fortune 500 companies use it. Customers include OpenAI, Stripe, Spotify, Midjourney, and Perplexity.

CEO Michael Truell is 25.

What the Community Is Saying

The Hacker News thread (330 points, 270+ comments) reflects a familiar split in the AI coding world.

The loudest concern is loss of control. Developers who liked Cursor as a coding assistant with good autocomplete are watching it become an agent orchestration platform. One commenter put it plainly: they iterate on code 10-15 times before production, checking logging, error handling, edge cases. Delegating that to an autonomous agent doesn’t fit their workflow.

Pricing is another sore spot. One user reported spending $350 on Cursor overage in a single week. Another said they switched to Claude Code Max and now pay a tenth of what they were spending on Cursor with premium models. The usage-based credit system, overhauled in June 2025, gives more flexibility than the old fixed “fast request” allotments, but costs can spike when you’re running multiple agents on frontier models.

On the positive side, several commenters noted that the traditional IDE mode remains available. The Agents Window is additive. You don’t lose the editing environment you already know.

On Reddit (r/cursor_ai), the tone is more polarized. A “Cursor is dead” narrative has been building since early 2026, partly driven by companies like Valon publicly switching to competitors. But daily Cursor users who rely on Composer and background agents are still enthusiastic about the product. The launch of Cursor 3 hasn’t resolved this tension so much as sharpened it.

Where Cursor 3 Sits in the Market

Fortune’s recent profile of Cursor framed the company as being at a crossroads. The core problem: Cursor pays retail rates for external models (Claude, GPT, Gemini) while competing against companies that own their models and can offer them at cost. One investor Fortune quoted said Cursor is “burning $1 to make 90 cents.”

Composer 2 is Anysphere’s answer to that structural disadvantage. By training their own coding model (built on Kimi K2.5 with reinforcement learning), they can offer high-volume agent usage at $0.50/M input tokens instead of the $5+/M they’d pay for Claude Opus or GPT-5.

The competitive landscape has three fronts:

Terminal agents like Claude Code, Codex, and Gemini CLI work outside the editor entirely. Claude Code controls a significant share of the professional developer market, backed by Anthropic’s wholesale model pricing.

IDE-integrated tools like Windsurf and GitHub Copilot compete on the editing experience. Both have added their own agent features in recent months.

Cloud-native builders like Devin, Replit, and Lovable target a different audience entirely, often non-developers or early-stage prototyping.

Cursor 3 tries to hold ground across the first two fronts. The Agents Window competes with terminal agents on orchestration. The underlying VS Code editor competes with IDE tools on editing. Whether a single product can win both battles is the billion-dollar question Anysphere is answering with this launch.

Warp CEO Zach Lloyd put it bluntly in the Fortune piece: the IDE may not be the right form factor for a world where you can produce 10x more code. Truell’s counter-bet is that developers still need a place to review, edit, and verify what agents produce, and that place should be the same tool that launched the agents.

Pricing

Cursor 3 doesn’t change the pricing structure. The Agents Window is included in all existing plans:

Plan	Price	What You Get
Hobby	Free	Limited agent requests and completions
Pro	$20/mo	Extended limits, all models, cloud agents
Pro+	$60/mo	3x usage credits
Ultra	$200/mo	20x usage credits, priority features
Teams	$40/user/mo	SSO, analytics, admin controls
Enterprise	Custom	Pooled usage, SCIM, audit logs

Annual billing saves 20%.

Try It

Update Cursor and type Cmd+Shift+P, then search for “Agents Window.” The traditional IDE is still there whenever you want it.

Truell said in the blog post that Cursor will continue investing in both the agent layer and the IDE “until codebases are self-driving.” Whether that timeline is months or years depends on how fast the models improve and how quickly developers trust agents with production code. Based on the internal stats Cursor shared today, the shift is already well underway.

Sources: