Cursor adds team workspaces where coding agents can coordinate across teammates

Cursor wants coding agents to catch conflicting plans before teammates finish the code. On November 10, 2026, it began rolling out multiplayer Projects in beta to all users, giving teams shared context and communication between their agents. The announcement illustrates how that coordination should work, rather than measuring how often it succeeds.

Projects arrived in September as a way for one engineer to direct several agents through a coordinator—an agent that organizes the work. The multiplayer update extends that arrangement across teammates. People can invite colleagues into the same Project to plan and build alongside their respective agents, rather than keeping the workspace centered on one person.

Separate conversations, shared decisions

Multiplayer does not replace each teammate’s individual agent conversations with one group chat. Each person retains one-to-one chats with their coordinator and worker agents, with local context for those interactions. Projects adds a team-wide information layer above them, so separate conversations can draw on a common understanding of the project.

That shared context holds requirements documents, diagrams, technical specifications and mockups. Cursor says the layer is built once and grows with the team’s work. A decision made in one chat becomes accessible to every agent in the Project; newly invited teammates receive context that is already configured and up to date.

A shared task board supplies the work-status view. It shows who is doing what, what their agents are working on, and the pull request associated with each task. A pull request is a proposed code change submitted for review. The board gives both people and agents visibility into work underway.

Coordinating before the collision

The more ambitious addition is communication between different teammates’ agents. Cursor says their coordinators can plan around one another and unblock work in real time. Its two examples describe different problems: people changing the same interface, and one person’s work depending on another person’s database change.

• Overlapping design work: An engineer adds reviews to a product page while a designer redesigns it. Cursor describes their coordinators spotting the overlap and aligning the work so the reviews fit the new design without later refactoring.
• Dependent database work: One teammate builds a feature that reads from a database while another changes its schema—the database’s structure. Cursor says the agents can agree on the order of work upfront to avoid a merge conflict at the end.

An on-call handoff inside Cursor

Cursor also describes an internal use beyond coordinating simultaneous code changes. Several of its teams run on-call rotations in a shared Project. In one recent handoff, the company says, the incoming engineer’s coordinator checked in first, then picked up with knowledge of work in flight, unattended issues, incidents and notes.

The coordinator also knew which channels, Linear boards and threads to monitor. Cursor says unfinished work can be handed directly to the incoming person’s agent. That is a company-described handoff, not a reliability test, but it gives a concrete account of shared context carrying work between people rather than requiring a fresh setup.

To start, users create a Project from Cursor’s left-hand navigation and invite teammates. The company says the beta rollout covers all Cursor users.