Launching today
Cursor 3
Unified workspace for parallel local/cloud agents and MCPs
209 followers
Unified workspace for parallel local/cloud agents and MCPs
209 followers
Cursor 3 is a unified workspace for building software with agents.
209 followers
209 followers
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
@adithya The local and cloud mix makes sense. That’s usually where things start getting messy. How are teams dealing with that part?
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?
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?
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
Congrats on your launch, Cursor team.
This developer tools race is insane.
You pick a tool, dive into it, and use it until their competitor releases a new version. I'm jumping between Cursor, Claude Code, and Codex.