Cursor Opens Multiplayer Projects Beta for Shared Agent Teams

By Daniel Okafor

Cursor began rolling out multiplayer Projects to all Cursor users in beta on November 10, 2026. The upgrade lets teams invite colleagues into a shared workspace where people and coding agents coordinate tasks, context and handoffs, Cursor said. The update moves Projects beyond its original single-user setup.

What changes in a shared Project?

A shared task board shows what each teammate and agent is working on. It also identifies the pull request behind each task, according to Cursor. Together, those features give the group one current view of active work. The workspace combines shared context, memory and documents, extending collaboration beyond task assignments.

Cursor detailed a two-layer setup for that information. Each teammate keeps a one-to-one chat with their coordinator and worker agents, while the platform keeps local context for those exchanges separate from broader team material. A team-wide layer holds requirements documents, diagrams, technical specifications, mockups and other material. It expands as the Project's work advances.

The Project's full agent fleet can access decisions recorded in one person's chat. Invited teammates receive pre-configured, up-to-date context, Cursor said. That avoids each new member building and maintaining a separate agent setup before work starts. Personal chats remain in place. Knowledge relevant to the wider team stays at the Project level.

How do handoffs work?

Several internal Cursor teams now run on-call rotations inside shared Projects, Cursor said. In a recent handover described by Cursor, the incoming engineer's coordinator checked in and resumed the rotation's current state. The coordinator inherited:

• Work in flight.
• Unattended issues and incidents.
• Notes requiring handoff.
• Channels, Linear boards and threads to monitor.

Unfinished work can transfer directly to the incoming teammate's agent. The shared Project record acts like a live shift log, carrying state into the next handoff rather than requiring a fresh reconstruction of the work. That mechanism matters when on-call rotations change and when projects run for months.

How do agents coordinate?

Agents owned by different teammates can communicate, plan around one another and unblock work in real time within the shared workspace, Cursor said. The company offered two hypothetical examples:

• Coordinators for an engineer adding product-page reviews and a designer redesigning the same page detect the overlap early. They incorporate the reviews directly into the new design.
• Agents supporting a feature that reads a database coordinate with a teammate changing its schema. They agree on the order of work upfront to avoid a later merge conflict.

Cursor said the examples show how shared context can surface dependencies before they turn into rework. The team layer gives agents shared requirements, decisions and current task relationships while leaving each personal chat intact.

What runs beneath the shared workspace?

Multiplayer extends the Projects architecture that Cursor introduced on September 10, 2026. That architecture targeted large bodies of work, including features, migrations and full applications. A coordinator directs coding agents rather than writing code itself. Cursor said delegation keeps the coordinator responsive to user direction.

Projects run on cloud computers by default, so work continues after a user's laptop closes. A coordinator can start a local agent when something must be tested on the user's machine. Project files synchronize across the cloud and local machines used by agents. The sync preserves research, artifacts, knowledge about the codebase and work preferences.

Subscriptions let a coordinator watch a Slack channel, run on a schedule or follow pull requests. The coordinator can fix continuous-integration failures and act when pull requests open or merge. Cursor said the original system maintained context over months, delegated to thousands of subagents and performed recurring work without repeated prompting.

To start, a user creates a Project from the left-hand navigation and invites teammates. The beta focuses on onboarding, handovers and coordination of overlapping work within the shared project record. Cursor said keeping that record current as people and agents contribute is central to the model.

For users, the practical test is whether one maintained record can carry context, dependencies and unfinished work across a team. The beta places that burden inside Cursor's shared workspace rather than in separate prompts and agent setups.