Super Sale WeekClaude Skills — 20% OFF
News

Cursor Projects Goes Multiplayer: What's New, Shared Context, and Alternatives (2026)

Powerdrill Bloom·
Cursor Projects Goes Multiplayer: What's New, Shared Context, and Alternatives (2026)

Cursor Projects became multiplayer on November 10, 2026. Teammates can now join one Project and work alongside each other's AI agents, with a shared task board and shared context. The update is rolling out in beta to all Cursor users. Projects first launched for single users in September.

This guide covers what changed, how the shared context works, who can use it, and what it costs. It ends with alternatives, including tools for teams whose work ends in a report rather than a pull request. Details come from Cursor's own pages, read on November 11, 2026.

What Cursor announced on November 10

Cursor's post opens with the core change. It says "Invite your teammates into a Project, and you can plan, build and ship together."

The post frames it as a gap in the market. It says "Multi-agent systems have so far served one person. Projects is a multi-agent system built for a whole team."

Three things are new:

  • A shared workspace. Teammates and their agents work in one Project, with a shared task board.
  • A shared context system. Requirements, specs, and other documents live in one layer every agent can read.
  • Agent-to-agent communication. Teammates' agents can coordinate with each other while they work.

The update is in beta. Cursor says it is "rolling out in beta to all users in Cursor starting today."

A quick recap: what Cursor Projects is

Cursor introduced Projects on September 10, 2026. It is a way to run large engineering work through one coordinator agent.

You talk to the coordinator, and it sends the actual coding to other agents. The September post says "The coordinator doesn't write code itself but directs other agents that do." Because it delegates, Cursor says it "is never blocked and is always responsive to direction."

The September launch named three core capabilities:

  1. Cloud by default. "A Project runs on its own computer, so closing your laptop doesn't stop it."
  2. Shared context. Each Project keeps a set of files that sync across the machines its agents use.
  3. Subscriptions. The coordinator can watch a Slack channel, run on a schedule, or follow your pull requests.

Cursor describes the scale plainly. A Project "delegates tasks to thousands of subagents" and "maintains context over months of work."

The September post described three patterns from Cursor's own engineers:

  • Feature work. Agents research the system first and record what they learn. The coordinator then plans and sends agents to build and test parts in parallel.
  • Migrations. Cursor used Projects to adopt new frameworks and replace styling systems "across hundreds of PRs." Engineers review closely at first, then less as fixes hold up.
  • Gardening. Ongoing work such as code quality. One design-system Project "is on track to touch 20 to 100 PRs a day."

Cursor also shared one result from internal use. It said "new users merge 30% more PRs while users who primarily use Projects merge six times as many." That figure comes from Cursor itself, not an outside study.

Until this update, though, a Project served one person. Cursor's November post says "agent context is siloed per person." The multiplayer update targets that gap.

The shared task board

The first thing a team sees in a multiplayer Project is the task board. Cursor says it "shows who's doing what, what everyone's agents are working on, and the PR behind each task."

That solves a real problem with agents. When five engineers each run their own agents, nobody can see the whole picture. A shared board gives "humans and agents alike a unified, up-to-date view."

For a team lead, the board works like a sprint view that updates itself. Each task shows its owner, the agent working on it, and the pull request it produced.

Picture a four-person team shipping a checkout redesign. One engineer owns the payment flow, one owns the cart, a designer owns the new layout, and a lead reviews. Before, each person ran agents in a private chat. The lead learned what changed only when pull requests arrived.

In a shared Project, the lead opens one board. It shows the cart task in review, the payment task blocked on an API change, and the layout task waiting on design tokens. The lead can step in where work is stuck, instead of asking for status in Slack.

How shared context works now

Before this update, context lived in each person's chat. Cursor's post names the cost: "new team members have to build and maintain context before putting agents to work."

Multiplayer Cursor Projects add a shared layer on top of personal chats. Each teammate still gets a one-to-one chat with their coordinator. But the Project also holds "requirements docs, diagrams, tech specs, mockups, and more" for everyone.

Decisions travel too. The post says "A decision made in one chat is accessible to every agent in the Project."

Cursor's on-call example shows why this matters. Its teams run on-call rotations in a shared Project. When one engineer took over from another, the coordinator already knew which issues were open and which notes needed handing off. Cursor adds that "In-progress work can even be handed over directly."

Agents that talk to each other

The third change is the most new. Agents in a Project can now coordinate across teammates. Cursor says this "lets teammates' agents plan around and unblock each other in real time, just as people do."

The post gives two examples:

Situation What the agents do
An engineer adds reviews to a product page while a designer redesigns it The coordinators spot the overlap early and sync up
One feature reads from a database while a teammate changes its schema The agents agree on the order of work up front

In both cases, the goal is to avoid rework. Cursor says the second case means "neither of you hits a merge conflict at the end."

Who can use it, and how to start

Cursor says multiplayer Projects are rolling out in beta to all users. To get started, "create a Project from the left-hand nav, then invite your teammates to join."

Projects run in the cloud by default, per the September post. That matters when you check your plan, since cloud work is plan-dependent on Cursor's pricing page.

The update is built for software teams. Every example in both posts involves code, pull requests, schemas, or design systems. The posts do not describe uses outside engineering.

What it costs

Cursor's pricing page does not list Projects by name. It does list plans and which ones include cloud agents. Cursor's pricing page now covers Cursor and Grok together.

Plan Price on Cursor's pricing page Cloud agents and automations
Free $0/month Not included
Plus $8/month Not included; only Grok models on this plan
Premium $30/month Included
Super $100/month Included
Ultra $200/month Included
Teams $30+/user/month Included
Enterprise Custom Included

Because Projects run in the cloud, Premium is the lowest plan that lists cloud agents. Cursor's pricing page does not list a separate price for Projects. For an earlier Cursor launch that also depends on cloud agents, see our guide to Cursor Live Apps.

Current limitations

A few limits follow from the posts themselves:

  • Beta. Multiplayer Projects are in beta, and features may change.
  • Software work only. Cursor's examples are all engineering tasks.
  • Plan questions. The pricing page does not name Projects, so check cloud agent access on your plan.
  • Team habits. A shared board helps only if the team keeps tasks in it.

Teams should also decide early who owns the shared context. A requirements doc that nobody updates will mislead every agent that reads it.

Security teams may have questions too. A shared Project means more people, and more agents, can read the same documents. Cursor's post does not cover permission settings inside a Project, so check the docs or ask Cursor before adding sensitive specs.

What this means for teams using AI agents

The bigger trend is clear. Agent tools are moving from one person and one chat to shared spaces for whole teams. Cursor is one of several vendors making that move within the same week.

For engineering leads, three questions decide whether the update helps:

  1. Do several engineers already run agents on the same codebase? If yes, the shared board alone saves coordination time.
  2. Do you lose context when people hand off work? Shared context and direct handover target exactly that.
  3. Do your agents step on each other's changes? Agent-to-agent coordination aims to catch overlaps early.

Teams with one engineer and occasional agent use will see less benefit.

Teams that do try it can prepare in a few steps:

  • Start with one shared Project. An on-call rotation or a migration is a good first test, since both involve handoffs.
  • Seed the shared context. Add the requirements doc, the architecture diagram, and the coding rules before inviting others.
  • Name an owner for context. One person keeps the shared documents current, so agents do not act on old decisions.
  • Review the board in standups. If the team checks the board daily, people keep tasks in it.
  • Check plan access first. Confirm every invited teammate has a plan that includes cloud agents.

After two or three weeks, the team can judge the update on real work. Fewer status questions and fewer merge conflicts are the signs to look for. If neither changes, the shared Project may not suit that team's way of working yet.

Alternatives to Cursor Projects

Other tools launched similar team features in the same week. Each comes from its vendor's own post.

Option What it offers Launched
Amp spaces One agent that spawns and coordinates other agents for a team November 6, 2026
OpenClaw Multiplayer Several people working with the same agent and context November 5, 2026
Powerdrill Bloom Reports, slides, and sheets from your data, for non-engineering work Available now

Amp spaces. Amp describes a space as "a conversation with a single agent whose job is to spawn and coordinate agents for you." Its team used spaces to build features, run a launch, and do security reviews.

OpenClaw Multiplayer. OpenClaw lets two people work with one agent at the same time. It coordinates requests "through a shared queue," so people can see when the agent is busy.

Where Powerdrill Bloom fits

Cursor Projects is for code. Many teams around engineering need something else: a status report, a launch review deck, or a metrics summary from exported data. Powerdrill Bloom handles that work without a coding setup.

You upload a spreadsheet or report export and describe the output in natural language. The AI Report Generator says "Simply upload your data file, and let the AI do the rest." The Excel to PPT page turns Excel, CSV, or PDF files into slides.

For sharing, the Chat sharing page lets you send a conversation to colleagues by link or email.

The pricing page lists a Free plan at $0.00 and Pro at $13.27/mo.

Try Powerdrill Bloom with this sprint's export and ask for the update deck.

Frequently asked questions

What is Cursor Projects?

Cursor Projects is a way to run large engineering work through one coordinator agent. The coordinator directs other agents, keeps shared context, and can act on Slack messages, schedules, or pull requests.

When did Cursor Projects become multiplayer?

Cursor announced multiplayer Projects on November 10, 2026. It is rolling out in beta to all Cursor users.

How do I invite teammates to a Cursor Project?

Cursor says to create a Project from the left-hand nav, then invite your teammates to join.

How much does Cursor Projects cost?

Cursor's pricing page does not list Projects by name. Projects run in the cloud, and cloud agents are listed from the Premium plan at $30/month.

What is the difference between Cursor Projects and Amp spaces?

Both coordinate many agents for a team. Cursor Projects adds a shared task board and agent-to-agent coordination. Amp spaces center on one agent that spawns and organizes threads for you.

Sources: Cursor, Cursor Projects is now multiplayer · Cursor, Introducing Projects · Cursor pricing · Amp, Spaces · OpenClaw, Shattering Silos with OpenClaw Multiplayer.