← Tuesday, November 10 deck

15Tooling1 source posting

Cursor Rebuilds Projects so Teams and Their Agents Can Work Together

Your agents can now coordinate with your teammates’ agents. Projects has been rebuilt for multiplayer: every teammate and their agents can now work together in one unified workspace.

Video thumbnail of the Cursor app, with a Projects sidebar listing Billing refactor, Onboarding Flow, Auth Migration, and Portal, and a chat titled Exploring API Details

Context

Why it matters

A shared workspace where a team's agents can coordinate would change how groups use Cursor on the same codebase.

Cursor posted that Projects has been rebuilt for multiplayer, so every teammate and their agents can work together in one unified workspace, and that agents can now coordinate with a teammate's agents. Cursor also published a blog post saying the feature is rolling out in beta to all Cursor users starting today.

Deep dive

Cursor posted that agents can now coordinate with a teammate's agents, and that Projects has been rebuilt for multiplayer so every teammate and their agents can work together in one unified workspace.

Cursor's blog post, dated Nov 10 and written by Aryaman Khandelwal, says Projects was introduced in September as a way for one engineer to direct a fleet of agents through a single coordinator, and that today's change makes it a shared workspace for a whole team. According to the blog, each teammate still gets a private chat with their coordinator and worker agents, with its own local context, and Projects adds a shared context layer for requirements docs, diagrams, tech specs, and mockups. A shared task board is described as showing who is doing what, what each person's agents are working on, and the pull request behind each task.

The blog says a decision made in one chat is accessible to every agent in the Project, and that a new teammate can join with that shared context already in place. It also describes agent to agent communication across teammates, with examples of overlapping product work and a database schema change being coordinated before a merge conflict. Cursor said several of its own teams now run on call rotations in a shared Project. The post says multiplayer Projects is rolling out in beta to all users in Cursor starting today, and that a user can create a Project from the left hand nav and invite teammates to join.

What to expect next

The beta rollout will show whether shared context and agent to agent coordination hold up outside Cursor's own teams, especially on messy repos and on call handoffs. Watch for docs on permissions, how private chats stay private, and whether merge conflicts actually fall. If the feature spreads, the next signal will be teams running a single Project as the main place their agents work, not only as a demo workspace.