Cursor Projects is now multiplayer
Cursor Projects now lets teams share agent context and coordinate agent work in one workspace, reducing repeated setup and helping avoid overlapping changes.
Cursor Projects is rolling out in beta as a shared workspace for teammates and their agents. It combines individual chats with **shared requirements, specs, diagrams, and decisions**, plus a task board showing agent work and linked PRs. Teammates' coordinators can also plan around each other's work.
Teams using several coding agents could keep durable project context in the shared layer while preserving each person's local chat context. The article describes handoffs and agents coordinating changes to overlapping product and database work.
Cursor Projects is rolling out in beta as a shared workspace for teammates and their agents. It combines individual chats with **shared requirements, specs, diagrams, and decisions**, plus a task board showing agent work and linked PRs. Teammates' coordinators can also plan around each other's work. Teams using several coding agents could keep durable project context in the shared layer while preserving each person's local chat context. The article describes handoffs and agents coordinating changes to overlapping product and database work. The material gives examples from Cursor teams, including on-call handoff, but does not report measured effects on delivery time or merge conflicts. Availability is described as a beta rollout to Cursor users.
This adds a team-facing shared layer to Cursor Projects: teammates can maintain common requirements and decisions, see agent work and linked PRs, and coordinate changes across overlapping work. It makes shared project context and task visibility concrete, while the examples remain unmeasured and the feature is still in beta.