ToolNavs Find Useful AI Tools
Submit Sign in
Back to AI Q&A
How to Invite Teammates to Code Together in Cursor Projects

How to Invite Teammates to Code Together in Cursor Projects

AI Q&A • Admin • • 9 views

Inviting teammates to a Cursor Project is straightforward: click Invite at the top of the Project, search for teammates by name or email, and send the invitation. Once they accept, they join with their own coordinator and worker agents. In its official announcement on November 10, 2026, Cursor said Projects is now multiplayer: a team can plan, build, and ship together in one Project alongside each member's agents, sharing context, memory, documents, and a task board. It is rolling out in beta to all users.

Confirm Team Membership Before Inviting

Projects are shared inside a Cursor team: only members of the same team can join, and people on personal accounts or other teams cannot accept a valid invitation. Before sending one, confirm the person is already on your team; if not, add them to the team from the Cursor dashboard first. Invitees also need access to the repository behind the Project: someone without repository access will be blocked even after accepting. Three kinds of Projects cannot accept new members yet: those with legacy Privacy Mode enabled, those running on a self-hosted machine, and those that have been archived. A team admin can also turn Projects off entirely from the dashboard, after which the team cannot create new Projects.

What Happens After a Teammate Accepts

When a teammate clicks Accept Invite on the Project's invite card, they immediately get their own chat with their own coordinator and worker agents, and usage is billed to their own account rather than mixed into yours. New members do not need to set up the environment again: the shared context is already configured, with requirements documents, diagrams, technical specs, and mockups ready to pick up. The task board shows what people and agents are each working on, and which pull request belongs to each task, so handovers no longer need a verbal rundown. Coordinators also message each other: they can spot overlapping designs between two features in advance, or notice that one feature needs to read a table a teammate is refactoring, and agree on an order of work before any code is written.

Three Rules for the Shared Context

First, manage shared documents like code: record who changed what and why. If edits take effect without review, you have given every agent an unreviewed back door. Second, sensitive content is not shared across people by default: an agent asks before sharing private files or connector data, and when in doubt, refuse first. Third, assign ownership before work starts: write on the task board who owns each piece, so two agents never edit the same place at the same time and collide at merge time. For the full launch wording, see our Cursor Projects goes multiplayer. To tighten what a coding agent is allowed to do, see the OpenAI deep dive into the Codex sandbox and its three modes.

Recommended Tools

More