Cursor Projects Goes Multiplayer: Teammates and Their Agents Share One Workspace, and Agents Sync Plans and Flag Conflicts With Each Other; Beta Rolling Out to All Users
On November 10, Cursor rebuilt Projects for multiplayer. You can invite teammates into a Project, and everyone plans, builds, and ships in one workspace alongside their coordinator and worker agents. A new shared context layer holds requirements docs, diagrams, tech specs, and mockups, so a decision made in one chat is visible to every agent in the Project. A shared task board shows who is doing what, what each agent is working on, and the PR behind each task. Agents belonging to different teammates can also talk to each other: they share plans before starting, flag conflicts while working, and unblock each other. The beta is rolling out to all Cursor users starting today.

Key Takeaways
- Timeline: Projects first launched on September 10 (one person directing thousands of subagents) and became team multiplayer on November 10; the beta is rolling out to all users today
- Shared context: requirements docs, diagrams, tech specs, and mockups live in one place, so a decision made once is visible to every agent; new teammates join with context already set up
- Agent-to-agent: coordinators belonging to different teammates share plans up front and flag conflicts mid-work, for example agreeing on order when one person changes a schema another feature reads, avoiding late merge conflicts
- Shared task board: shows people, agents, and PRs together; Cursor already runs on-call rotations in a shared Project, and the incoming engineer's agent can take over in-flight work directly
- Impact figures: at the September launch Cursor said new users merge 30% more PRs and heavy Projects users merge 6x as many (vendor figures); no new figures were published for multiplayer







