Skip to content

Cursor launches multiplayer Projects: your Agent can now confer with your colleague's Agent on work

Nov 11, 18:38

Beating AI News Flash: Cursor upgrades Projects, launched this September, to Team Projects for multi-person collaboration.

Previously, a single user could direct multiple coding Agents through a supervisor Agent to simultaneously develop features and fix bugs. Now, team members can join the same Project. Each person still has their own supervisor Agent and execution Agents, but everyone shares a single task board and a single project knowledge base.

The task board shows who is responsible for what, which tasks the Agents are working on, and the corresponding GitHub PRs. The knowledge base stores requirements documents, design mockups, technical plans, and project decisions. A plan finalized by one person in chat can also be accessed by other members' Agents, eliminating the need to repeatedly brief them on context.

Supervisor Agents of different members can also communicate directly. For example, if one person's Agent is modifying database fields and another person's Agent is preparing to develop features that depend on those fields, the two sides can exchange plans in advance and agree on the order of changes, reducing conflicts when merging code at the end.

Cursor also shared an internal on-call handover case. After an engineer's shift change, the incoming engineer's Agent already has the unfinished tasks, pending incidents, and messages requiring continued attention. Work in progress can also be handed off directly to the new Agent.

In October this year, a developer complained on the Cursor forum that they could only see their personal Agent's task board and had to ask colleagues one by one what their Agents were busy with. The new version of Projects has added these sharing and coordination features.

The multi-person collaboration feature is currently being rolled out gradually and requires a Cursor team account, a plan that supports Cloud Agents, and version 3.26.13 or later. Each member's Agent usage is still billed separately.

Source