Cursor Adds Team Collaboration and Agent Handoffs to Projects

Cursor announced a multiplayer upgrade to Projects, its system for directing fleets of coding agents, on November 10, 2026, and began rolling it out in beta to all Cursor users. Teams can invite colleagues into a shared workspace where people and agents coordinate tasks, context and handoffs.

The update moves Projects beyond its original single-user setup. A shared task board shows what teammates and their agents are working on and identifies the pull request behind each task, giving people and agents a unified, current view of active work. The workspace also combines shared context, memory and documents, extending collaboration beyond task assignments.

Shared Context Across a Team

Each teammate retains a one-to-one chat with their coordinator and worker agents, with local context for those interactions. A team-wide layer holds requirements documents, diagrams, technical specifications, mockups and other material. It expands with the Project’s work, and decisions recorded in one person’s chat become available to the Project’s full agent fleet.

Cursor says invited teammates receive pre-configured, up-to-date context, avoiding the need for every new member to build and maintain a separate agent setup before starting work. The individual chats remain in place, while knowledge relevant to the wider team is maintained at the Project level.

Cursor reports that several of its internal teams now run on-call rotations in shared Projects. In a recent handover it describes, the incoming engineer’s coordinator checked in and resumed from the rotation’s current state. It had the work in flight, unattended issues, incidents and notes requiring handoff, and the channels, Linear boards and threads to monitor. Unfinished work can also be transferred directly to the incoming teammate’s agent.

Coordinating Agents Across Teammates

Within the shared workspace, agents belonging to different teammates can communicate, plan around one another and unblock work in real time. Cursor gives two hypothetical examples of the coordination this is meant to support.

In one, coordinators for an engineer adding product-page reviews and a designer redesigning that page detect the overlap early, allowing the reviews to be incorporated directly into the new design. In the other, agents supporting a feature that reads a database and a teammate changing its schema agree on the order of work upfront to avoid a later merge conflict. These examples position shared context as a way to address dependencies before they become rework.

The Architecture Behind the Update

Multiplayer extends the Projects architecture introduced on September 10, 2026, for large bodies of work including features, migrations and full applications. A coordinator directs coding agents rather than writing code itself; Cursor says delegation keeps it responsive to user direction. Projects run on cloud computers by default, allowing work to continue after a laptop closes, and the 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 its agents, preserving research, artifacts and knowledge about the codebase and work preferences. Subscriptions let a coordinator watch a Slack channel, run on a schedule or follow pull requests, including fixing continuous-integration failures and acting when pull requests open or merge. Cursor described the original system as maintaining context over months, delegating to thousands of subagents and performing recurring work without repeated prompting.

To start, a user creates a Project from the left-hand navigation and invites teammates. The beta concentrates onboarding, handovers and coordination of overlapping work in the shared project record, making that record’s ability to remain current as people and agents contribute central to the collaboration model.