Cursor Projects: Coordinator Agents for Big Work
CursorCursor launched Projects, a new way to tackle larger bodies of work such as a feature, a migration, or an entire app. Each Project is run by a coordinator agent that plans the work, delegates it to cloud-based subagents, and maintains shared context that persists across months of work. Projects also support subscriptions, letting the coordinator watch a Slack channel, follow pull requests, or run on a schedule and take action without being prompted. The feature is available in beta and rolling out to all users starting today.
Key Takeaways
- Cursor introduced Projects, a persistent workspace for large, multi-month efforts like a feature build, a migration, or a full application, distinct from the throwaway nature of a single chat session.
- A coordinator agent sits at the center of every Project and deliberately does not write code itself; it plans, delegates to implementing agents, and returns finished work for review.
- Projects run on dedicated cloud computers, so work continues even after a developer closes their laptop, with local agents spun up only when something needs to be tested on-machine.
- Shared context files sync across every agent a Project touches, so lessons learned by one agent (such as how to test a service) carry forward automatically to every future agent instead of being re-taught each session.
- Subscriptions let a Project act autonomously by watching a Slack channel, following pull requests, or running on a schedule, removing the need for a developer to manually prompt every piece of work.
- According to AlphaSignal's coverage of Cursor's internal usage data, developers who lean on Projects merge roughly six times more pull requests than casual users, with early adopters seeing about a 30% increase.
Sources & Mentions
2 external resources covering this update
Introducing Projects
Cursor launched Projects, a new surface for taking on larger bodies of work such as a feature, a migration, or a full application, rather than a single one-off task. Where a normal Cursor chat resets once a task is done, a Project is designed to persist: it maintains context over months of work, delegates tasks to thousands of subagents, and can perform recurring work without being re-prompted each time. Projects are accessed from the left-hand navigation and are available in beta, rolling out to all users starting today.
A Coordinator Agent, Not a Code Writer
At the center of every Project sits a coordinator agent. Unlike a typical coding agent, the coordinator does not write code itself. Instead, it plans the work, breaks it into tasks, and delegates those tasks to agents that do the actual implementation. Once the work is finished, the coordinator brings it back to the developer to review. Because coordinators create and manage agents on the user's behalf, they can run as many of those agents in parallel as a given piece of work requires, which is what allows a single Project to scale from a small feature up to a job that would previously have needed thousands of separate agent sessions to coordinate manually.
Powered by Cloud Agents
Each Project runs on its own computer in the cloud, so closing a laptop does not stop the work in progress. When a task needs to be verified on the developer's own machine, such as running a local test suite, the coordinator spins up a local agent specifically to handle that step before returning to the cloud-based work.
Shared Context That Grows Over Time
A recurring pain point with AI coding agents is that every new session starts from zero, forcing a developer to re-explain the codebase and their preferences each time. Projects address this with a set of shared context files that sync across every cloud and local machine the Project's agents touch. Agents contribute research, artifacts, and lessons learned about the codebase and the developer's preferred way of working back into that shared context. If one agent works out how to test a particular service, for instance, every agent that runs afterward inherits those instructions automatically. Cursor frames this as a compounding effect: the longer a Project runs, the more effective its coordinator becomes.
Subscriptions: Acting Without a Prompt
Projects can also be configured to act on their own initiative through subscriptions. A developer can tell the coordinator agent to watch a Slack channel, run on a fixed schedule, or follow all of a repository's pull requests, and the coordinator will take action based on whatever signal it detects rather than waiting to be prompted. As one example, connecting a Project to a bug-report Slack channel lets the coordinator start delegating a fix to a subagent the moment a new bug report comes in.
Availability
Projects is in beta and is rolling out to all Cursor users starting September 10, 2026.