Cursor launches Projects, persistent coordinator agents for features, migrations, and recurring work

Introducing Projects

On September 10, 2026, Cursor launched Projects—a product layer for larger bodies of work such as a feature, a migration, or a full app. According to Cursor, a Project maintains context over months of work, delegates tasks to thousands of subagents, and performs recurring work without being prompted.

Cursor positions Projects as the concrete implementation of its “third era” vision for fleets of agents taking on entire bodies of work. By moving up a level of abstraction, Projects is meant to free developers from managing individual agents and let them direct the work itself. The company says it has used Projects internally for months, including migrations of a few hundred PRs, design-system consistency, and shipping Projects itself. Cursor reports that new users merge 30% more PRs, while users who primarily use Projects merge six times as many.

Projects are available in beta and rolling out to all users. You start one from the left-hand nav, describe what you want built, and the coordinator takes it from there. Cursor’s changelog entry mirrors the same launch details.

One coordinator, many implementers

You oversee a Project by chatting with its coordinator agent. Cursor is explicit that the coordinator does not write code itself; it plans the work, directs other agents that implement it, and brings finished work back for you to check. Because it delegates rather than executes, Cursor says the coordinator is never blocked and stays responsive to direction. Coordinators create and manage agents on your behalf, running as many in parallel as the work needs.

That design is distinct from Cursor’s earlier self-hosted machines story: Projects is about a persistent coordinator and shared project context, with cloud execution as the default compute surface rather than only bringing your own worker pool.

Cloud by default, shared context, subscriptions

Cursor describes three core capabilities:

Cloud by default, local when needed

A Project runs on its own computer in the cloud, so closing your laptop does not stop it. That setup can run more subagents in parallel than a laptop alone. When something needs testing on your machine, the coordinator can spin up a local agent there.

Shared context

Each Project maintains a set of files that sync across every cloud and local machine its agents use. Agents add research and artifacts, plus what they learn about the codebase and how you prefer work done. If one agent figures out how to test a service, later agents can reuse those instructions. Cursor says this context grows with the Project and makes the coordinator more effective over time.

Subscriptions

The coordinator can watch a Slack channel, run on a schedule, or follow your PRs, including fixing CI and acting when PRs open or merge. Cursor’s changelog adds that pointing Slack at a bug-report channel lets the Project start delegating each time a bug comes in—so recurring work can proceed without waiting for a fresh prompt.

How Cursor uses Projects

Cursor highlights three patterns:

• Feature work. Agents research the system into shared context; the coordinator plans and sends agents to implement and test parts in parallel; local agents can run when the feature is ready to try; after ship, the same Project can monitor logs and bug reports with original context.
• Migrations. Useful for work that is easy to start and hard to finish—Cursor cites adopting frameworks and replacing styling systems across hundreds of PRs—with the coordinator applying a safe approach incrementally while review intensity decreases over time.
• Gardening. Ongoing quality and regression work via PR follow, Slack bug reports, or schedules. One internal design-system Project is described as scanning new PRs, extracting components, and adding lint rules when the same mistake appears twice.

Cursor says Projects work best on work that will outlive a single chat: multi-PR features, migrations, or jobs you want handled while you are away.

Source: Introducing Projects (Cursor, September 10, 2026); also Cursor Projects changelog