Cursor 3 is a unified workspace for building software with agents — faster, cleaner, and built from scratch around how engineers actually work with AI today.
All agents in one place: local and cloud agents in a single sidebar, including ones kicked off from mobile, web, Slack, GitHub, and Linear
Parallel agents: run multiple agents across different repos simultaneously, with demos and screenshots to verify cloud agent output
Local ↔ cloud handoff: move agent sessions between environments instantly — push to cloud to keep running while offline, or pull local to test and iterate
Diffs and PRs: review changes, stage, commit, and manage PRs from a cleaner diffs view
Integrated browser: agents can open, navigate, and prompt against local websites directly
Cursor Marketplace: browse and install plugins that extend agents with MCPs, skills, subagents, and more
Full IDE depth: view files and go-to-definition with full LSP support, anytime
@adithya The local and cloud mix makes sense. That’s usually where things start getting messy. How are teams dealing with that part?
Report
@adithya Congrats! How's the handoff holding up in real multi-repo sprints, like handing a backend agent off to frontend while offline?
Report
Parallel local/cloud agents in a unified workspace is the right direction - context switching between Claude Code, a cloud runner, and your local terminal is where a lot of time disappears right now. The MCP piece is interesting too. How does Cursor 3 handle agent conflicts when two parallel agents try to touch the same file or resource at the same time?
Report
Curious what actually changed from Cursor 2 to 3. Is it mostly the agent stuff or did they rebuild other parts too?
Report
They rebuild the whole IDE, now it looks like Antigravity.
Report
Parallel agents is what I've been waiting for. Right now I'm bouncing between Claude Code in terminal and Cursor for UI stuff and the context switching kills the flow. If this actually lets me run local and cloud agents side by side in one workspace, that changes how I build. How's the MCP setup? Plug and play or does it need a lot of config?
Report
Parallel local/cloud agents in one workspace is the right direction - context switching between Claude Code, a cloud runner, and local terminal is where a lot of time disappears right now. How does Cursor 3 handle agent conflicts when two parallel agents try to touch the same file at the same time?
curious about the MCP integration piece - are you supporting custom protocol handlers or just the standard anthropic ones? we've been building some healthcare-specific MCPs and the tooling around that ecosystem still feels pretty early
The parallel agent workspace is the feature I have been waiting for. Running multiple agents side by side without them colliding on file changes has been a real pain point in every other tool I have tried. Curious how the MCP support works in practice. Does each agent get its own MCP server connection, or do they share a single pool?
Cursor
Claude Code
Indie.Deals
Cursor 3 is a unified workspace for building software with agents — faster, cleaner, and built from scratch around how engineers actually work with AI today.
All agents in one place: local and cloud agents in a single sidebar, including ones kicked off from mobile, web, Slack, GitHub, and Linear
Parallel agents: run multiple agents across different repos simultaneously, with demos and screenshots to verify cloud agent output
Local ↔ cloud handoff: move agent sessions between environments instantly — push to cloud to keep running while offline, or pull local to test and iterate
Diffs and PRs: review changes, stage, commit, and manage PRs from a cleaner diffs view
Integrated browser: agents can open, navigate, and prompt against local websites directly
Cursor Marketplace: browse and install plugins that extend agents with MCPs, skills, subagents, and more
Full IDE depth: view files and go-to-definition with full LSP support, anytime
SellerClaw
@adithya The local and cloud mix makes sense. That’s usually where things start getting messy. How are teams dealing with that part?
@adithya Congrats! How's the handoff holding up in real multi-repo sprints, like handing a backend agent off to frontend while offline?
Parallel local/cloud agents in a unified workspace is the right direction - context switching between Claude Code, a cloud runner, and your local terminal is where a lot of time disappears right now. The MCP piece is interesting too. How does Cursor 3 handle agent conflicts when two parallel agents try to touch the same file or resource at the same time?
They rebuild the whole IDE, now it looks like Antigravity.
Parallel agents is what I've been waiting for. Right now I'm bouncing between Claude Code in terminal and Cursor for UI stuff and the context switching kills the flow. If this actually lets me run local and cloud agents side by side in one workspace, that changes how I build. How's the MCP setup? Plug and play or does it need a lot of config?
Parallel local/cloud agents in one workspace is the right direction - context switching between Claude Code, a cloud runner, and local terminal is where a lot of time disappears right now. How does Cursor 3 handle agent conflicts when two parallel agents try to touch the same file at the same time?
Open Wearables
curious about the MCP integration piece - are you supporting custom protocol handlers or just the standard anthropic ones? we've been building some healthcare-specific MCPs and the tooling around that ecosystem still feels pretty early
Nex
The parallel agent workspace is the feature I have been waiting for. Running multiple agents side by side without them colliding on file changes has been a real pain point in every other tool I have tried. Curious how the MCP support works in practice. Does each agent get its own MCP server connection, or do they share a single pool?