Cursor 3 shipped April 2, 2026, and it is not a feature update. It is a category change. Where Cursor 2.x bolted AI assistance onto a VS Code fork, Cursor 3 treats agents as the primary interface: the keyboard shortcut, the file tree, and the terminal are supporting actors for an orchestration layer managing multiple AI agents running in parallel across local machines, cloud infrastructure, worktrees, and SSH sessions. The company hit $2B ARR and a $50B valuation on the back of autocomplete and tab completion. With Cursor 3, the bet is that parallel agent management is the next productivity multiplier for professional developers.
The TCC editorial fixture (200 queued agent pairs, 14-task scorecard) measures the same gap the launch-week threads converged on: parallelism is real and the workflow wins are real, but per-task quality scores are flat against Cursor 2.9. Both conclusions hold. This review covers what changed, what the numbers say, and who the upgrade actually serves.
What actually changed in Cursor 3
The Agents Window
The Agents Window (Cmd+Shift+A on macOS, Ctrl+Shift+A on Windows/Linux) is the new nerve center. It replaces the chat panel with a persistent workspace showing every agent currently running: its status, what it is working on, and where it is running (local, cloud, worktree, SSH). Each agent displays as a card, expandable to see the current action. You can pause, intervene, redirect, or terminate any agent from this view without switching contexts.
In the TCC fixture, the primary behavioral change compared to Cursor 2.x is that queuing a second Composer run in the same workspace no longer cancels the first. In Cursor 2.x, this killed the first run on a small but meaningful fraction of queued pairs. In Cursor 3, it did not happen once across 200 queued pairs. That is the documented behavior change, and it is real.
Current limitation: the Agents Window does not support branching agent history. To see what path an agent took to reach its current state, you scroll through the full chat log. A decision tree view is not shipped yet.
Parallel agent execution
Cursor 3 can manage multiple independent coding tasks simultaneously, each in its own worktree, environment, or remote session. A local agent can handle a feature branch while a cloud agent runs a database migration against staging. Both report back to the Agents Window, and you can intervene in either without stopping the other.
The worktree integration is the architectural choice that makes this work. Git worktrees let you check out multiple branches simultaneously in separate directories; Cursor 3 wraps this so agents operate in isolated directories without stepping on each other. Before spawning a second agent, run git worktree add ../feature-branch feature/your-branch. Cursor 3 will detect the worktree and offer to run the new agent in that isolated directory.
Warning: the default configuration does not enforce worktree isolation. If you spawn parallel agents without setting up worktrees first, multiple agents can fight over the same working directory. The onboarding flow does not make this clear enough; set up worktrees before the agents, not after.
Cost warning: parallel agents multiply context costs. Three agents understanding a codebase simultaneously can triple the compute bill. Cursor 3 does not yet expose granular per-agent cost tracking. Watch usage closely during initial rollout.
The /best-of-n command
The /best-of-n command runs the same task across multiple AI models simultaneously to compare results. This is useful for tasks where you want to sample outputs from, for example, Composer 2, Claude Opus 4.7, and GPT-5.5 before committing to one direction. It is an explicit multi-model parallel run, not multi-agent on the same model.
Cloud agent handoff
Start a long-running agent task locally, close your laptop, and the task continues running in Cursor’s cloud infrastructure. When you reconnect, full context is restored and results are waiting. For tasks like large-scale refactors, dependency migrations, or test suite generation across a monorepo, this is a meaningful unlock: the work continues while you sleep.
Availability note: cloud handoff is only available on Business and Enterprise plans. Pro users get 50 cloud hours per month, which sounds generous but can evaporate quickly on long autonomous tasks. Cursor has not been fully transparent about how cloud agent compute maps to subscription pricing. Test cloud handoff with a low-stakes task first to validate your account’s configuration before relying on it for critical work.
Data governance note: when an agent continues running in Cursor’s cloud after your laptop closes, code is leaving your machine. Cursor’s privacy policy covers data handling broadly but does not specifically address the cloud agent execution context. Enterprise teams should ask explicit questions about data retention and compliance frameworks before enabling cloud handoff.
Multi-repository support
Cursor 3 can work across multiple codebases simultaneously within a single workspace. Any agent you spawn has access to all indexed codebases. This is the feature that matters most for microservices teams, monorepos with separate packages, or any architecture where a feature change touches multiple repositories simultaneously. An agent working on an API contract change can have context across the frontend, backend, and shared library repos at once.
Indexing large repositories takes time. A 500K+ LOC monorepo takes meaningful time to index, and re-indexing on branch switches can feel sluggish. Add repositories one at a time and let Cursor index each fully before adding another. The Pro plan supports up to 3 repositories; Business and Enterprise support unlimited.
Integrated browser
Agents can open and interact with locally-running web applications via an embedded Chromium view with a controlled automation API. This enables QA workflows, data extraction, and UI testing as part of the agent loop without a separate automation framework. Current limitation: the browser integration does not handle complex authentication flows well. If your local app uses session management, OAuth, or cookie-based auth, agents can lose session state mid-task and fail silently.
Design Mode
Developers can annotate UI elements directly in the integrated browser and instruct agents to modify specific components rather than describing changes in text. Instead of writing “change the button in the top-right nav to blue and move it below the logo,” you click the button in the browser view and issue the instruction against the selected element. This closes the gap between visual intent and textual instruction for UI work.
Plugin marketplace
The plugin marketplace shipped with approximately 40 plugins from Cursor’s partner ecosystem. Most useful at launch are integrations with Jira, Linear, and GitHub Issues that let agents create tickets, update statuses, and comment on PRs as part of their workflow. Plugin quality is variable. There is no sandboxing of plugin permissions at launch: a poorly-written plugin can affect agent behavior across your entire workspace. Review plugins before installation; do not install unverified plugins in a high-stakes environment.
Benchmark performance
Cursor 3’s underlying coding intelligence draws from Cursor Composer 2 (built on Kimi K2.5) and frontier models selectable via the model dropdown. Cursor has not published a dedicated Cursor 3 benchmark suite.
| Benchmark | Cursor 3 (Composer 2) | Claude Code (Opus 4.7) | GitHub Copilot (GPT-5.4) |
|---|---|---|---|
| SWE-bench Pro | 74.1% | 76.3% | 71.8% |
| HumanEval | 91.2% | 92.1% | 90.7% |
| TCC refactor score | 8.1 | n/a (CLI) | n/a |
| TCC RAG score | 7.9 | n/a | n/a |
| Autocomplete latency | 30-45ms | n/a | 43-50ms |
Refactor score on the TCC 14-task suite: 8.1 on Cursor 3, 8.1 on Cursor 2.9. The parallelism is a workflow win, not a per-task quality win. RAG score stayed flat at 7.9 out of 12 on the 1,400-chunk fixture. The chunker setting is still not exposed in the UI; bumping to 768/128 requires editing settings.json. Tab autocomplete acceptance rate moved from 31% to 44% on TypeScript per Cursor’s published numbers; on Python it is roughly flat. That is a Composer 2 underlying-model change, not a parallel-agent story.
Pricing
| Plan | Price | Agents Window | Cloud Execution | Multi-Repo |
|---|---|---|---|---|
| Free | $0/mo | 1 local agent, basic tab | No | No |
| Pro | $20/mo | Unlimited local agents | 50 hrs/mo | Up to 3 repos |
| Business | $40/user/mo | Full fleet management | Unlimited | Unlimited |
| Enterprise | Custom | Full fleet + SSO + audit logs | Unlimited + private cloud | Unlimited + private repos |
At $20/month, Cursor 3 Pro is competitively priced for individual developers who regularly run parallel agent workflows. The Business tier at $40/user/month is where the math gets harder versus GitHub Copilot Business at $19/user/month. The premium is real and only justified if parallel agents and cloud execution are a core part of your team’s workflow, not an occasional use case.
How Cursor 3 compares
| Feature | Cursor 3 | Claude Code | GitHub Copilot | OpenAI Codex |
|---|---|---|---|---|
| Interface | Full IDE (VS Code fork) | CLI tool | IDE extension | Web + API |
| Parallel agents | Native, GUI managed | Manual (multiple terminals) | Single agent only | API-level only |
| Multi-repo | Native (Pro: up to 3) | Via separate sessions | Limited | Single repo |
| Cloud execution | Built-in (Pro+) | External API compute | GitHub Actions only | Native cloud |
| Integrated browser | Yes (local sites) | Via computer use | No | No |
| SWE-bench Pro | 74.1% | 76.3% | 71.8% | 69.4% |
| Starting price | Free / $20 Pro | ~API usage | Free / $10 Individual | $25/mo Pro |
Claude Code beats Cursor 3 on raw model performance. GitHub Copilot beats it on price. OpenAI Codex beats it for pure cloud-based workflows. But none of them offer managed multi-agent orchestration inside an IDE. That is a real differentiation. The question is whether your workflow needs it.
The Composer 2 attribution context
You cannot evaluate Cursor 3 honestly for enterprise deployment without knowing this history. When Cursor Composer 2 launched in March 2026, the community discovered through response pattern analysis that the underlying model was Moonshot AI’s Kimi K2.5. Cursor had not disclosed the Kimi dependency at launch. The backlash was significant. Cursor subsequently acknowledged the Kimi K2.5 foundation in the model selection UI, but there has been no formal public statement addressing the original non-disclosure.
Cursor 3 does not resolve this. The launch announcement did not address it. For a company at $50B valuation selling to enterprise customers who care about AI supply chain transparency, this is a credibility gap. If you are running an enterprise evaluation, ask Cursor explicitly about their model sourcing practices before routing proprietary code through their infrastructure.
Who should use Cursor 3
Use Cursor 3 if: you build across multiple services or repositories and constantly context-switch between codebases. You run long autonomous tasks without wanting to babysit them. You are already a Cursor user and the upgrade path is obvious. You need agents that interact with locally-running web apps as part of their workflow. You want to run parallel workstreams on different features simultaneously.
Look elsewhere if: you are a solo developer on a single-repo project where the orchestration overhead is unnecessary cost. You prefer a CLI-first workflow (Claude Code delivers stronger raw model performance). You are budget-constrained and comparing to Copilot Individual at $10/month. You work in a high-security environment where code leaving your machine on cloud agent handoff is a concern without an Enterprise private cloud contract.
Getting started
- Install and migrate settings. Download Cursor 3 from cursor.com. Upgrading from 2.x migrates settings, extensions, and keybindings automatically. Verify AI model selection post-upgrade: Settings > AI > Models. Note that
.cursorrulesfiles are deprecated; migrate to.cursor/rules/*.mdc. This trips up most 2.x users on upgrade. - Open the Agents Window. Use Cmd+Shift+A (macOS) or Ctrl+Shift+A (Windows/Linux). Before spawning agents, learn the status indicators: green = running, yellow = waiting for input, red = failed, gray = queued.
- Set up worktrees before running parallel agents. In your repo:
git worktree add ../feature-branch feature/your-branch. Cursor 3 will detect the worktree and offer to run the new agent in that isolated directory. This prevents agents from conflicting on the same working directory. - Add multi-repo context carefully. Go to Settings > Workspace > Repositories. Add one additional repo at a time. Let Cursor index it fully (watch the status bar) before adding more or querying across repos.
- Test cloud handoff with a low-stakes task first. Spawn an agent on a small task (write unit tests for a utility function), close your lid for 5 minutes, reopen. Verify the task continued and results are intact before relying on cloud handoff for critical work.
The implication
Parallel agents change how work is sequenced, not how good the work gets. A team already shipping one PR a day with Cursor 2.x can ship two now without context-switching. A team where a single PR per day was slow because the model itself was the bottleneck does not see help here. The numbers that move that bottleneck are model scores, not IDE features. See the Claude Opus 4.7 review for where the model-side bar moved in April 2026, and the case against autonomous agents for why a human at the merge boundary still matters even with parallel orchestration.
FAQ
What is the Cursor 3 Agents Window?
The Agents Window is a persistent panel showing every AI agent currently running in your workspace: local agents, cloud agents, agents in worktrees, and agents over SSH. Each agent displays as a card with status, current action, and location. You can pause, redirect, intervene in, or terminate any agent from this unified view. Open it with Cmd+Shift+A (macOS) or Ctrl+Shift+A (Windows/Linux).
How many parallel agents can I run in Cursor 3?
Up to 8 agents simultaneously. Pro plan gets unlimited local agents with 50 cloud hours/month. Business and Enterprise get unlimited local and cloud agents. The practical ceiling is your machine’s RAM; each agent running a background task peaks the memory footprint meaningfully (the background agent completing a 63k-line TypeScript rename peaks at 2.4 GB, up from 1.6 GB on Cursor 2.9).
Is Cursor 3 better than GitHub Copilot?
For parallel agent workflows and multi-repository work, Cursor 3 is significantly better. Copilot has a single-agent model and no native parallel execution. Copilot is cheaper ($10/month individual vs $20/month Cursor 3 Pro) and has a deeper VS Code extension ecosystem. For autocomplete and single-task AI assistance, Copilot remains competitive. The value proposition for Cursor 3 is specifically the orchestration layer.
Is Cursor 3 better than Claude Code?
Claude Code has a stronger underlying model (76.3% SWE-bench Pro vs Cursor 3’s 74.1%). Claude Code is a CLI tool with no native agent orchestration GUI, no parallel agent management, and no integrated browser. Cursor 3 wins on workflow management and multi-agent capabilities. Claude Code wins on raw model performance and is better for terminal-first developers.
What was the Cursor Composer 2 Kimi K2.5 controversy?
When Composer 2 launched in March 2026, the community found through response pattern analysis that the underlying model was Moonshot AI’s Kimi K2.5. Cursor had not disclosed this at launch. After community pressure, Cursor acknowledged the Kimi K2.5 foundation in the model selection UI but issued no formal public statement about the original non-disclosure. This history is context for enterprise teams evaluating cloud execution transparency.
How does cloud agent handoff work?
Start an agent task locally, close your laptop, and the task continues running in Cursor’s cloud infrastructure. When you reconnect, full context and results are waiting. Available on Pro (50 hours/month) and unlimited on Business/Enterprise. Only use cloud handoff after verifying your account’s configuration on a low-stakes test task first.
Does Cursor 3 support multiple repositories?
Yes. Pro supports up to 3 repos simultaneously; Business and Enterprise support unlimited. Once added, agents have access to all indexed codebases simultaneously. Index one additional repository at a time and wait for full indexing before adding the next.
What the threads are saying
The most-upvoted Hacker News thread on the Cursor 3 launch converged on “this is the first Cursor release in three quarters where the IDE polish caught up with the model polish.” r/cursor flagged the .cursorrules migration tripping people up on upgrade; the fix is in the official Cursor docs, which now point to .cursor/rules/*.mdc as the supported path. The Cursor 3 release post also documents the indexer speedup (2x cold start) and the disk trade (1.6x index size). The community has noticed the token costs multiply with parallel agents; cost tracking at the per-agent level is the most-requested missing feature.
One-line takeaway
Parallel agents change sequencing, not task quality. If the bottleneck was scheduling, the cost just dropped. If the bottleneck was correctness, the Cursor 3 + Composer 2 model review and the bare-model benchmarks are still the place to look. See also the Cursor 3 shortcuts cheatsheet for the settings that matter and the case against autonomous agents for why the human gate at merge still matters.