Cursor launches multiplayer collaborative version Team Projects, gradually opening it up

AT A GLANCE

According to Dongcha Beating AI, Cursor has launched Team Projects, allowing team members' Agents to share tasks, project materials, and communicate directly.

Article

Cursor Launches Multiplayer Projects: Your Agent Can Now Discuss Work with Your Colleagues' Agents

Dongcha Beating AI Flash News: Cursor has upgraded Projects, launched this September, into the multiplayer collaboration version Team Projects.

Previously, a single user could direct multiple coding Agents through a supervisor Agent to develop features and fix bugs simultaneously. 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 Agents are working on, and the corresponding GitHub PR. The knowledge base stores requirement documents, design drafts, technical plans, and project decisions. A plan finalized by one person in a chat can also be accessed by other members' Agents, eliminating the need to repeatedly explain the background.

Supervisor Agents of different members can also communicate directly. For example, one person's Agent is modifying database fields, while 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 modifications, reducing conflicts when merging code at the end.

Cursor also shared an internal on-call handover case. After engineers change shifts, the successor's Agent already has knowledge of unfinished tasks, pending incidents, and messages that require continued attention. Ongoing work can also be handed directly over to the new Agent.

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

The multiplayer collaboration features are currently being rolled out gradually and require a Cursor team account, a plan that supports Cloud Agents, and version 3.26.13 or newer. Agent usage for each member is still billed separately.

Original link: https://m.theblockbeats.info/flash/376777

Key points

Reports say that Cursor has upgraded Projects, launched this September, into the multi-user collaborative version Team Projects.
Team members can join the same Project, each retaining their supervisor Agent and execution Agent, and sharing the task board and project repository.
The shared kanban board displays member task assignments, Agent tasks, and the corresponding GitHub PRs; the repository stores requirement documents, design drafts, technical solutions, and project decisions.
Supervisor Agents of different members can communicate directly, exchange plans, and agree on the order of modifications.
Cursor shared an internal on-call handover case, saying that the successor's Agent can grasp unfinished tasks, pending failures, and messages that need attention, and take over work in progress.
Reports indicate that the multiplayer collaboration feature is being rolled out gradually, requiring a Cursor team account, a plan that supports Cloud Agents, and version 3.26.13 or newer; each member's Agent usage is still billed separately.

AI-assisted interpretation

The following is analysis, separate from reported facts. Verify important claims independently.

This change extends the multi-agent working style used by individuals to teams: everyone still directs their own agents, but everyone can see shared tasks and materials, and agents can also coordinate with each other in advance. The original text uses database field modifications as an example to explain that the relevant agents can first discuss the order of changes, rather than only discovering conflicts when merging code.

Why it matters to readers

Sharing task statuses and project decisions helps reduce the need to repeatedly explain background information; having Agents exchange plans in advance also supports cross-member collaboration and work handovers. The actual effectiveness still needs to be verified.

You can think of it as equipping the team's Agent with a shared task board and resource library. To use it, you must first verify the team account, plan, and software version; multi-user sharing does not mean that usage is billed on a consolidated basis.

Risks and unknowns

The current evidence is a media paraphrase, and no official Cursor announcement has been provided for verification.
Features are still being rolled out gradually, and the original text does not state when all eligible accounts will have access.
The original text does not provide specific usage prices, nor does it quantify the effects of reducing code conflicts or improving handover efficiency.
The original text does not specify the details of permission and privacy controls for shared materials and Agent communication.

Cursor launches multiplayer collaborative version Team Projects, gradually opening it up

Article

AI-assisted interpretation

Why it matters to readers

Risks and unknowns

Related Developments

Related concepts

Keep following

Security Center