Cursor Makes Projects Multiplayer, 61 Days After Launch

Cursor says its Projects feature is now multiplayer: teammates can be invited into a Project and work alongside each other’s agents, according to a Cursor blog post dated November 10. The company says it is “rolling out in beta to all users in Cursor starting today”.

By our arithmetic, that is 61 days after Cursor introduced Projects on September 10 as a way for one engineer to direct a fleet of agents through a single coordinator.

Business Pill · Bundle Moat Explained

An evergreen Business Engineer explainer on why buyers keep the bundle. It teaches the general idea only and does not discuss Cursor’s update.

What Cursor Says Changed

Cursor writes that “Multi-agent systems have so far served one person” and that “Projects is a multi-agent system built for a whole team”.

Each teammate still gets a one-to-one chat with a coordinator and worker agents, Cursor says. On top of that, it describes a shared context system that “holds requirements docs, diagrams, tech specs, mockups, and more”, and a shared task board that shows “who’s doing what, what everyone’s agents are working on, and the PR behind each task”.

The post also describes agent-to-agent communication across teammates: “This lets teammates’ agents plan around and unblock each other in real time, just as people do”. Its example is an engineer adding reviews to a product page while a designer redesigns it, with the two coordinators spotting the overlap and syncing early.

Cursor says several of its own teams run on-call rotations in a shared Project, and that when one engineer took over a rotation, “the new person’s agent simply takes it on” for in-progress work.

What Was Posted on X

Cursor announced on X on 10 November that its agents can now coordinate with teammates’ agents, saying Projects has been rebuilt for multiplayer so every teammate and their agents can work together in one unified workspace. The same change is described in Cursor’s blog post of the same day.

TestingCatalog wrote at 00:36 UTC on 11 November that Cursor’s multiplayer mode is built on top of Projects and said it seems like a day-one answer to Google‘s Antigravity /swarm feature; that is the poster’s reading, and Cursor’s blog post is dated 10 November. The post also said Claude and Perplexity are working on similar multiplayer features; that is the poster’s claim and the post gives no source for it.

Where Projects Started

The September post described Projects as a feature that “delegates tasks to thousands of subagents” and runs on its own cloud computer. Cursor said then that “new users merge 30% more PRs while users who primarily use Projects merge six times as many”, figures from its own internal use.

Cursor has a corporate link to SpaceX: our October coverage noted its owner Anysphere joining SpaceX’s orbit, and our Grok Build piece cites Ars Technica describing Cursor as the coding company SpaceXSI recently acquired.

The Same Day as Google’s /swarm

Cursor’s post is dated November 10, the same day Google added a /swarm command to Antigravity for running agents in parallel, which we covered that evening. TestingCatalog wrote on X that Cursor’s update “Seems like a day-one answer to the Antigravity/swarm feature” and that “Claude and Perplexity are also working on similar multiplayer features”; that last claim is TestingCatalog’s, and its post gives no source for it.

Our earlier coverage of agent-team research is in Ten AI Agent Teams of 10 Score 27% Above 100 Solo Agents.

The Structural Read

As we read it, the update moves Cursor from agents that serve one engineer to agents that coordinate across a team, the shift Cursor itself describes when it writes that multi-agent systems have so far served one person.

Three Implications

FOR ENGINEERING TEAMS Cursor says each teammate keeps a one-to-one chat with a coordinator while a shared context system and task board sit on top.

FOR ON-CALL WORK Cursor says several of its own teams run on-call rotations in a shared Project and hand in-progress work to the next person’s agent.

FOR READING THE TIMELINE By our arithmetic, multiplayer arrived 61 days after Projects launched, and the post gives no price or seat limits.

What Is Not Established

Cursor’s post gives no price for multiplayer Projects, no seat or agent limits per Project and no usage figures. The productivity figures are from Cursor’s own September post and are not independently verified. The 61-day figure is our arithmetic on Cursor’s two blog dates.

The Bottom Line

Cursor says Projects is now multiplayer, letting a team and its agents share one workspace, context and task board, rolling out in beta to all users from November 10. By our arithmetic that came 61 days after Projects launched.