Cursor has made Projects multiplayer. You can now invite teammates into a Project, and everyone plans, builds and ships alongside the same agents. Cursor’s announcement says the beta is rolling out to all Cursor users from November 10.
Projects launched in September as a way for one person to direct many agents through a single coordinator, an agent that splits large work into pieces and hands them to helper agents. Until now, that setup served one person at a time.
One workspace for people and agents
You create a Project from the left navigation and invite teammates. Each person keeps a private one-to-one chat with their own coordinator and worker agents. A shared task board shows who is doing what, what each person’s agents are working on, and the pull request (a proposed code change waiting for review) behind each task.
Coordinators also talk to each other. Cursor’s example: an engineer adds reviews to a product page while a designer redesigns the same page. Their coordinators spot the overlap early and sync up, instead of producing two conflicting versions.
Shared context replaces per-person setup
Cursor says agent context is currently siloed per person, so a new teammate has to build up context before agents are useful. A Project adds a shared layer holding requirements docs, diagrams, tech specs and mockups. A decision made in one person’s chat becomes accessible to every agent in the Project, and a newly invited teammate starts with that context already in place.
Cursor’s on-call example shows the payoff. When an engineer takes over a rotation, their coordinator already knows which work is in flight and which issues are still unattended, and can hand in-progress work over directly.
Because every agent in the Project can read the shared layer, treat it like a document the whole team can see. Keep passwords and private customer details out of the specs and notes you put there.
End of article