Cursor launches multiplayer version of Projects: Your agents can now collaborate with colleagues' agents on work.

Beating AI News Flash: Cursor is upgrading its Projects feature, launched this September, to a multi-user collaborative version called Team Projects. Previously, a single user could manage multiple coding agents via a lead agent to develop features and fix bugs simultaneously. Now, team members can join the same Project: each retains their own lead agent and execution agent, but all share a single task board and project repository. The task board displays who is responsible for what, which tasks agents are handling, and their corresponding GitHub PRs. The repository stores requirement documents, design drafts, technical solutions, and project decisions. A solution agreed upon in a chat by one member is accessible to other members’ agents, eliminating repeated context explanations. Lead agents of different members can also communicate directly. For example, if one member’s agent is modifying database fields and another’s is preparing to develop a feature dependent on those fields, both can exchange plans in advance to agree on modification order, reducing code merging conflicts. Cursor also shared an internal shift handover case: after an engineer’s shift change, the incoming agent already has access to unfinished tasks, pending bugs, and follow-up messages, and ongoing work can be directly handed over to the new agent. In October, a developer complained on the Cursor forum that they could only view their personal agent’s task board and had to ask colleagues individually to check their agents’ work. The new Team Projects version has added these sharing and coordination features. Currently, the multi-user collaboration feature is rolling out gradually, requiring a Cursor team account, a Cloud Agents-supported plan, and version 3.26.13 or later. Each member’s agent usage remains billed separately.