Last updated: November 11, 2026
Cursor Projects multiplayer lets a whole team share one Project. Each teammate keeps their own coordinator and worker agents, billed to them, while everyone shares a task board and a shared context store. Coordinators can message each other directly. It rolled out in beta on November 10, 2026, and needs a team account and Cursor 3.26.13 or later.
Contents
- What changed on November 10
- Plans and requirements
- How to share a Project with teammates
- How coordinators message each other
- Shared context and your personal store
- Workflows and setup tips
- Limitations
- Frequently asked questions
This guide covers what the multiplayer update adds, who can use it, and how to set it up. It draws on Cursor’s multiplayer announcement, the Projects documentation and the Projects help article.
What changed on November 10
Cursor introduced Projects on September 10, 2026 as a way to direct many agents through one coordinator. The coordinator plans and delegates but does not write code itself. Until now, a Project served one person.
The November 10 announcement makes Projects multiplayer. Cursor calls it “a multi-agent system built for a whole team.” The update is rolling out in beta to all users.
| Feature | Single-user Projects (September) | Multiplayer Projects (November) |
|---|---|---|
| Who works in it | One person and their agents | Invited teammates, each with their own coordinator and workers |
| Task tracking | Used by one person | One shared task list and board for all members |
| Shared context | Files synced across your agents | One Agent Store (Context) that every member’s agents read and write |
| Agent communication | Not available across people | Coordinators message teammates’ coordinators directly |
| Billing | One person’s usage | Each member’s chat runs and bills as that member |
| Requirements | A plan with Cloud Agents | Also a team account and Cursor 3.26.13 or later |
Cursor gives an on-call example. When an engineer took over a rotation, their coordinator already knew what work was in flight and which incidents needed handing off. In-progress work can be handed over directly to the new person’s agent.
Plans and requirements
According to the documentation, Projects runs on Cloud Agents. It is available on Premium and higher, Teams, Enterprise and legacy paid plans. Enterprise teams need Cursor 3.21.9 or later. It is not available on Free, Plus or the legacy Hobby plan.
Sharing adds three more conditions: a team account, Cursor 3.26.13 or later, and access to the Project’s repository for each person who joins. For plan prices, see our answer on how much Cursor Teams costs.
How to share a Project with teammates
- Update Cursor to version 3.26.13 or later.
- In the Agents Window, open the Projects section in the sidebar and click New Project. Pick an icon, name, repository (Workspace) and coordinator model, then click Create Project.
- At the top of the Project, click Invite. After the first invite, this becomes a row of faces.
- Under “Invite teammates to this project,” search by name or email and send the invite. You can also use Copy link to share the Project link.
- Your teammate clicks Accept Invite on the invite card and gets their own chat in the Project.
- To revoke old links, the owner can choose Reset Share Link. The owner can remove a member with Remove, and anyone can leave with Leave Project from the sidebar menu.
The owner and anyone who has joined can invite others. Only people in the Project can copy its link.
How coordinators message each other
When your coordinator needs something from a teammate’s work, it messages their coordinator directly. Cursor’s announcement gives two cases: an engineer and a designer working on the same page, and a feature that depends on a schema a teammate is changing. In both, the coordinators agree on the order of work early to avoid refactors and merge conflicts.
The documentation sets rules for these messages:
- The receiving agent is told which teammate’s agent sent the message and treats it as untrusted input, not as a request from its own user.
- It asks before sharing that person’s personal files or connector data.
- The message goes to a side chat called “Chat with {name}’s agent,” so your main chat is not interrupted. Your chat gets a note about the exchange on its next turn.
- Side chats only answer. They never share secrets, credentials or tokens, can read but not change the task board, and cannot request access or manage routines.
Shared context and your personal store
| Store | Path | Who reads and writes it |
|---|---|---|
| Project store (Context) | /cursor/stores/self | Every member’s agents |
| Personal user store | /cursor/stores/user | Only your own agents |
Your personal store holds preferences and skills that follow you between Projects. When a teammate joins, your coordinator can offer to copy preferences about this Project into the Project’s rules. It copies only what you approve.
Workflows and setup tips
Cursor’s help article describes the Project store files: preferences.md for standing rules, notes.md for tracking work, and workflows/ and principles/ folders for procedures and non-negotiables. In a shared Project, these become team conventions every agent follows.
- Seed rules first. Cursor publishes a sample preferences.md. It recommends one worker per pull request or workstream, cloud workers on their own VM, and naming workers by job in two or three words.
- Keep kickoffs short. State the goal, constraints and what “done” means, and point to workflow files.
- Use subscriptions for shared duties. A coordinator can watch a Slack channel, run on a schedule or follow pull requests. A Listening pill above the chat input lists active subscriptions.
- Add existing chats. Drag a top-level Cloud Agent chat onto a Project row, or choose Add to Project.
Related reading: Cursor Cloud Agents guide, Cursor voice chat guide, which can switch between workers in a Project, and Cursor Agent SDK guide. For a different approach to agent teams, see our Google Antigravity /swarm guide.
Limitations
- Multiplayer Projects is a beta and is still rolling out.
- People on personal accounts or other teams cannot join.
- Joining is unavailable with Privacy Mode (Legacy), on a Project running on a self-hosted machine, or on an archived Project.
- Each member’s usage is billed to that member, so a busy shared Project can raise usage across the team.
- Cursor has not published a member limit per Project on these pages.
Frequently asked questions
What is Cursor Projects multiplayer?
It is a beta update, announced November 10, 2026, that lets several people on the same Cursor team work in one Project. Each person gets their own coordinator and worker agents, while everyone shares the Project’s task board and its shared context store.
Which Cursor plans can use multiplayer Projects?
Projects needs a plan that includes Cloud Agents: Premium and higher, Teams, Enterprise and legacy paid plans. It is not available on Free, Plus or the legacy Hobby plan. Sharing a Project also needs a team account and Cursor 3.26.13 or later.
Who pays for a teammate’s agents in a shared Project?
Cursor’s documentation says each member’s chat runs and bills as that member. Inviting a teammate does not move their agent usage onto your account.
Can someone outside my Cursor team join a Project?
No. Projects are shared within a Cursor team and joining takes an invite or the Project link. People on a personal account or on another team cannot join, and every member needs access to the Project’s repository.
Can a teammate’s agent see my personal files or secrets?
Not by default. Your preferences and skills live in a personal store at /cursor/stores/user that teammates’ agents never see. Messages from a teammate’s coordinator are treated as untrusted input, and the side chat that answers them never shares secrets, credentials or tokens.
Sources
- Cursor Projects is now multiplayer, Cursor blog (November 10, 2026)
- Projects, Cursor documentation
- What is a Cursor Project?, Cursor help
- Introducing Projects, Cursor blog (September 10, 2026)