
News
Cursor Projects now coordinates a team's agents
Cursor Projects now lets a team and its agents share context and a task board, and sequence work before merge conflicts.
Cursor says Projects is now multiplayer. Introduced in September as a way to direct a fleet of agents through one coordinator, a Project can now include teammates who plan, build, and ship alongside their agents. Multi-agent systems, Cursor writes, have so far served one person. Projects is a multi-agent system built for a whole team.
Cursor calls it the first workspace where software teams work side by side with all of their agents, with shared context, memory, and documents. A shared task board shows who is doing what, what everyone's agents are working on, and the pull request behind each task.
Each teammate still gets a one-to-one chat with their own coordinator and worker agents, and that chat keeps its own local context. Above those chats, a shared layer holds requirements docs, diagrams, tech specs, mockups, and more. Cursor says the layer is built once and grows with the team's work, and that a decision made in one chat is accessible to every agent in the Project. A newly invited teammate gets that context already pre-configured and current, instead of rebuilding context that the post says is still siloed per person.
Cursor says several of its teams now run on-call in a shared Project. When one engineer recently took over a rotation, their coordinator picked up where things stood after checking in first. It already knew which work was in flight, which issues were still unattended, which incidents and notes needed handing off, and which channels, Linear boards, and threads to watch. In-progress work can be handed over directly: the new person's agent takes it on.
That shared layer is also what Cursor says lets agents coordinate across teammates. If an engineer is adding reviews to a product page while a designer is redesigning it, their coordinators spot the overlap and sync, so the reviews are built into the new design rather than refactored later. If one feature reads from a database while a teammate changes the schema, the agents agree on the order of work up front, so neither side hits a merge conflict.
Cursor says the upgrade is rolling out in beta to all users in Cursor, starting today. The post does not state a price or a team-size limit.
Create a Project from the left-hand nav and invite the teammates who share the work. Read Cursor's post for how the shared board, the on-call handoff, and the cross-agent sequencing are described.
Sources
- Projects is now multiplayer cursor.com