Back to rankings

Cursor Projects Multiplayer: Shared Workspaces for Teams and Their Agents

CursorView original changelog

Cursor made Projects multiplayer, so teammates can plan, build and ship together with their agents in one shared workspace. A shared task board, shared context and memory, and a layer of documents like requirements docs, diagrams, tech specs and mockups keep every person and agent aligned. Agents belonging to different teammates can also coordinate with each other in real time. Multiplayer Projects is rolling out in beta to all Cursor users.

Key Takeaways

  • Projects is now multiplayer, letting teammates plan, build and ship together with their agents in one shared workspace.
  • A shared task board shows who is doing what, what everyone's agents are working on, and the PR behind each task.
  • Context is layered: a private one-to-one chat with each person's coordinator and worker agents, plus a shared layer of requirements docs, diagrams, tech specs and mockups.
  • A decision made in one chat is accessible to every agent in the Project, and new teammates join with context pre-configured and up to date.
  • Agent-to-agent communication lets teammates' agents spot overlapping work and agree on the order of database and schema changes to avoid merge conflicts.
  • Cursor runs on-call rotations in shared Projects internally, with in-progress work handed directly to the incoming person's agent.
  • The feature is rolling out in beta to all Cursor users; create a Project from the left-hand nav and invite teammates.

From a Solo Coordinator to a Team Workspace

Cursor introduced Projects in September as a way for engineers to take on large-scale work by directing a fleet of agents through a single coordinator. With the November 10, 2026 update, Projects gets a major upgrade: it is now multiplayer. Invite teammates into a Project and they can plan, build and ship together, alongside all of their agents. Cursor frames the shift directly: multi-agent systems have so far served one person, and Projects is a multi-agent system built for a whole team.

One Workspace for People and Agents

Cursor describes Projects as the first workspace where software teams work side by side with all of their agents, with shared context, memory and documents. A shared task board shows who is doing what, what everyone's agents are working on, and the PR behind each task, giving humans and agents alike a unified, up-to-date view.

A Unified Context System

Today agent context is siloed per person, and new team members have to build and maintain context before putting agents to work. In a Project, each teammate still gets their own one-to-one chat with their coordinator and worker agents, each with its own local context. On top of that, Projects adds a shared context system holding requirements docs, diagrams, tech specs, mockups and more. The shared layer is built once and grows with the team's work. A decision made in one chat is accessible to every agent in the Project, and when a new teammate is invited, context is pre-configured and up to date, avoiding repetitive setup.

Handing Off Work, Including On-Call

Cursor says it has seen this most clearly in on-call. Several of its own teams now run their on-call rotations in a shared Project. When one of its engineers recently took over a rotation from a teammate, their coordinator picked up right where things stood, after checking in first: it already knew what work was in flight, which issues were still unattended, which incidents and notes needed handing off, and which channels, Linear boards and threads to keep an eye on. In-progress work can even be handed over directly, with the new person's agent simply taking it on.

Agents That Talk to Each Other

A shared workspace and shared context open up agent-to-agent communication between teammates, letting their agents plan around and unblock each other in real time, just as people do. Cursor gives two examples. If an engineer is adding reviews to a product page while a designer is redesigning it, their coordinators spot the overlap early and sync up, so the reviews are built straight into the new design with no refactors later. And if one person's feature reads from a database while a teammate changes the schema, their agents agree on the order of work up front, so neither hits a merge conflict at the end.

Availability

Multiplayer Projects is rolling out in beta to all users in Cursor starting November 10, 2026. To get started, create a Project from the left-hand nav, then invite teammates to join.