Cursor Adds Multiplayer to Projects in Beta on November 10; Docs Say Teammates' Coordinators Message Each Other and Treat Messages as Untrusted Input

Overview

Cursor said on November 10, 2026 that Projects, the feature it launched in September, has had a multiplayer mode added. In its announcement, Cursor writes that “Projects gets a major upgrade: it’s now multiplayer” and that the mode is “rolling out in beta to all users in Cursor starting today”. Cursor’s documentation adds that one member’s coordinator agent can message another member’s coordinator, and that the receiving agent treats the text “as untrusted input to weigh”. The New Stack reported on November 12 that Google previewed a different coordination feature, /swarm in Antigravity, on the same day.

What Cursor announced

Cursor’s launch post for Projects is dated September 10, 2026. Per the November post, which is bylined Aryaman Khandelwal, each teammate “still gets their own one-to-one chat with their coordinator and worker agents”. On top of that, Projects adds “a shared context system that holds requirements docs, diagrams, tech specs, mockups, and more”. The post also describes a shared task board showing “who’s doing what, what everyone’s agents are working on, and the PR behind each task”. Cursor’s post summarises the change as: “Multi-agent systems have so far served one person. Projects is a multi-agent system built for a whole team.”

Cursor gives an example of the agent-to-agent messaging. If a feature reads from a database while a teammate is changing the schema, Cursor writes, “your agents agree on the order of work up front”. The one report of actual use in the post is Cursor’s own on-call rotations, which it says several of its teams now run in a shared Project; the post gives no figures for outcomes.

What the documentation says

Cursor’s Projects documentation fills in the mechanics:

• Requirements. “Sharing a Project needs a team account and Cursor 3.26.13 or later.”
• Who works where. Each person who joins gets their own chat with their own coordinator and workers, and “Their chat runs and bills as them.” Members share the task board and the Project’s shared context, which the page describes as “one Agent Store that every member’s agents read and write”.
• Messaging. A coordinator that needs something from a teammate’s work “messages their coordinator directly”. The docs say the receiving agent is told which teammate’s agent sent the message, treats the text “as untrusted input to weigh, not as a request from the person it works for”, and “asks before sharing that person’s personal files or connector data”.
• Side chats. A teammate’s message goes to a side chat forked from the recipient’s chat. The docs say the side chat can only answer, “never shares secrets, credentials, or tokens”, can read the task board but not change it, and cannot ask the user questions, request access, connect source control or manage routines.
• Joining. Projects are shared within a Cursor team by invitation; someone on a personal account or another team cannot join. The docs list three cases where joining is not available: Privacy Mode (Legacy), a Project that runs on a self-hosted machine, and an archived Project.

Availability: the post and the docs use different wording

The November post says the mode is “rolling out in beta to all users in Cursor”. The New Stack says it is “in beta now for users on a team account”. The documentation page does not use the word “beta” (the Herald read its Markdown text on November 14); it states the team-account and version conditions above. The same docs page also says Projects in general “isn’t available on Free, Plus, or the legacy Hobby plan”, and that Enterprise teams need Cursor 3.21.9 or later for Projects. Cursor’s September launch post used similar wording, “available in beta and rolling out to all users starting today”. None of the cited sources says how many teams have access. The Herald reads the difference as a general statement in the post and conditions in the docs, not as a contradiction, but no source explains it.

Reaction and a gap The New Stack notes

The New Stack reports that “some in the community raised concerns” that letting teammates’ agents talk “could spread one agent’s mistakes across the whole team, especially if each person’s agents follow different rules, and that an agent could request information it shouldn’t have access to”. It adds that Khandelwal, whom it describes as a Cursor product manager, responded that multiplayer Projects lets teams define shared rules and skills for everyone in a project.

The same report says the Projects documentation “doesn’t say whether admins can set different rules for those exchanges based on a teammate’s role”. The Herald’s own search of that one docs page for administrator or role settings found none, which is a statement about that page only; Cursor may document such controls elsewhere.

How Google’s /swarm differs

According to The New Stack, Google rolled out Gemini 4 Carbon in Antigravity on November 10 “alongside a preview” of Swarm, which “lets a developer hand one assignment to a coordinator that then splits it among worker agents and assigns a verifier to check their changes”. The outlet frames the difference as scope: Swarm serves one developer’s agents, while multiplayer Projects lets coordinators “talk across” assignments from different teammates.

Antigravity’s Swarm documentation says workers “coordinate on one shared message board” and, in the Herald’s paraphrase, do not message each other privately. It says the command is available on Google AI Pro and Google AI Ultra plans, that Swarm is in preview, and that “a swarm uses quota much faster than a single conversation”. The Herald’s own comparison of the two docs pages is that Cursor describes messages passing between coordinators and landing in a side chat on the recipient’s side, while Antigravity describes posts on a board that members can read. Neither the Cursor November post nor the Antigravity page gives outcome figures, and the Herald did not test either product.

The Herald’s earlier article on Antigravity’s Orchestrator says Google’s Antigravity models page points to subagents, Swarm, Boost or Teamwork for parallel work. An earlier Analysis of orchestration layers covers reports from October 30 to November 5, 2026 and does not mention Cursor.