Cursor Projects goes multiplayer, so teammates' agents can coordinate

TL;DR: Cursor's Projects, its tool for directing a fleet of coding agents through one coordinator, is now multiplayer. Teammates can join the same Project, share a task board and a shared context layer, and their coordinator agents can message each other to avoid overlap and merge conflicts. It is rolling out in beta to all Cursor users starting November 10, 2026. Sharing a Project needs a team account and Cursor 3.26.13 or later.

What Cursor announced

On November 10, 2026, Cursor posted on X: "Your agents can now coordinate with your teammates' agents. Projects has been rebuilt for multiplayer" (Cursor on X). Cursor first introduced Projects in September as a way for one engineer to take on large work by directing many agents through a single coordinator. The new version is built for a whole team. In Cursor's words, "Multi-agent systems have so far served one person. Projects is a multi-agent system built for a whole team" (Cursor blog).

What teammates share

Each person who joins a Project keeps their own chat with their own coordinator and worker agents, and that chat runs and bills as them. On top of that, members share two things (Cursor Docs):

• A task board. Everyone works from the same list of tasks, which shows who is doing what, what each agent is working on, and the pull request behind each task.
• Shared context. Requirements docs, diagrams, tech specs and mockups live in one store that every member's agents can read and write. Cursor says a decision made in one chat becomes available to every agent in the Project, and a new teammate joins with that context already in place.

Each person also keeps a private personal store for their own preferences and skills, which a teammate's agents never see.

How the agents talk to each other

When your coordinator needs something from a teammate's work, it messages their coordinator directly. Cursor's blog gives two examples: an engineer adding reviews to a product page while a designer redesigns it, where the coordinators spot the overlap early, and a feature that reads from a database while a teammate changes its schema, where the agents agree on the order of work up front so nobody hits a merge conflict at the end.

Cursor's docs also spell out guardrails for those messages:

• A message from a teammate's agent is labeled as agent input and treated as untrusted, not as a request from the person your agent works for.
• It lands in a side chat, so your own chat isn't interrupted, and your chat gets a note about the exchange on its next turn.
• Side chats only answer. They never share secrets, credentials or tokens, can read but not change the task board, and ask before sharing your personal files or connector data.

Who can use it

Projects are shared inside a Cursor team, and joining takes an invite or the Project's share link. Someone on a personal account or another team can't join. To start, create a Project from the left-hand nav and click Invite at the top of it (Cursor Docs). Cursor's post names no separate price for the multiplayer upgrade.

Why it matters

Most AI coding tools still treat agents as one person's helpers, so context lives in each developer's chat history and has to be rebuilt for every new teammate. Projects moves that context to the team level and lets agents negotiate with each other the way people do in a standup. If it works as described, the payoff is fewer duplicate efforts and fewer late merge conflicts on teams that already lean on agents.