On November 10, Cursor rebuilt Projects for multiplayer. You can invite teammates into a Project, and everyone plans, builds, and ships in one workspace alongside their coordinator and worker agents. A new shared context layer holds requirements docs, diagrams, tech specs, and mockups, so a decision made in one chat is visible to every agent in the Project. A shared task board shows who is doing what, what each agent is working on, and the PR behind each task. Agents belonging to different teammates can also talk to each other: they share plans before starting, flag conflicts while working, and unblock each other. The beta is rolling out to all Cursor users starting today.
Key Takeaways
- ✓Timeline: Projects first launched on September 10 (one person directing thousands of subagents) and became team multiplayer on November 10; the beta is rolling out to all users today
- ✓Shared context: requirements docs, diagrams, tech specs, and mockups live in one place, so a decision made once is visible to every agent; new teammates join with context already set up
- ✓Agent-to-agent: coordinators belonging to different teammates share plans up front and flag conflicts mid-work, for example agreeing on order when one person changes a schema another feature reads, avoiding late merge conflicts
- ✓Shared task board: shows people, agents, and PRs together; Cursor already runs on-call rotations in a shared Project, and the incoming engineer's agent can take over in-flight work directly
- ✓Impact figures: at the September launch Cursor said new users merge 30% more PRs and heavy Projects users merge 6x as many (vendor figures); no new figures were published for multiplayer
Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Background and Industry Pain Points
Over the past year coding agents went from one chat per person to one person directing a fleet of agents, but context stayed siloed per person. Each person's agents only knew their own chats, new teammates had to rebuild context from scratch, and two people's agents editing the same code often found the conflict only at merge time. Projects, launched on September 10, solved scaling for one person; the multiplayer version targets team collaboration.
Architecture Highlights and Mechanisms
Each teammate still has a one-to-one chat with their coordinator and worker agents, with local context. On top of that sits a shared team context layer holding requirements docs, diagrams, tech specs, and mockups, which grows with the team's work. A shared task board links people, agents, and PRs. The key piece is agent-to-agent communication across teammates: coordinators spot overlapping tasks and agree on the order of work up front, for example building new product reviews straight into a page redesign.
Benchmarks and Measured Results
Cursor has not published figures for multiplayer mode. For reference, at the September Projects launch Cursor said new users merge 30% more PRs and users who mainly use Projects merge six times as many (vendor figures). Cursor also described an internal on-call handoff where the incoming engineer's coordinator already knew the in-flight work, unattended issues, and channels to watch.
Developer Adoption and Getting Started
The beta is rolling out to all users starting today: create a Project from the left-hand nav, then invite teammates. Start by putting requirements docs and tech specs into the shared context, then trial a mid-sized feature that several people build in parallel and watch whether agents flag conflicts early. It is most worth trying for schema changes and cross-module refactors.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.