Cursor Projects Give a Coordinator Agent a Long-Lived Body of Work

Cursor is introducing Projects, a beta workflow for work that outlives a single chat. Instead of starting a separate conversation for every task, you work with a coordinator agent that keeps the larger effort organized and delegates implementation to other agents. (Cursor on X; Cursor's Projects announcement)

Cursor describes Projects as a way to take on a feature, a migration, or a full app. The coordinator can retain context over months, send agents to research, implement, and test different parts of a plan in parallel, and keep recurring work moving without a new prompt each time. (Cursor's Projects announcement)

A coordinator instead of another coding chat

The coordinator agent is the control layer for a Project. Cursor says it does not write code itself. It creates plans, directs agents that do the implementation, and stays available for feedback while those agents work. (Cursor's Projects announcement)

That separation is designed for larger bodies of work. A Project can begin with agents researching the codebase and recording what they learn. The coordinator then uses that shared context to split a feature into parallel implementation and testing tasks. As the user gives feedback, Cursor says the Project learns the team's architecture and working preferences. (Cursor's Projects announcement)

Projects can also bridge cloud and local execution. Cursor says a Project runs on its own computer by default, so closing a laptop does not stop the work. When something needs to be tested on the user's machine, the coordinator can start a local agent for that step. (Cursor's Projects announcement)

Shared context and artifacts

Each Project maintains files that synchronize across the cloud and local machines used by its agents. Agents can add research, artifacts, codebase notes, and instructions about how the user prefers work to be done. Cursor's example is a testing discovery recorded by one agent and reused by future agents. (Cursor's Projects announcement)

This is different from simply keeping a long transcript. The shared context is intended to accumulate operational knowledge: how a service is tested, what the architecture expects, and which patterns the team prefers. That context gives the coordinator more information to use as the Project grows. (Cursor's Projects announcement)

Subscriptions for recurring work

Cursor says Projects can use Subscriptions to watch a Slack channel, run on a schedule, or follow all of a user's pull requests. The coordinator can act when PRs open or merge, fix CI issues, listen for bug reports, and organize the work so the engineer checks in where attention is needed. (Cursor's Projects announcement)

Cursor uses a design-system Project as an example. It scans new pull requests, extracts components that belong in the design system, and adds a lint rule when it sees the same mistake twice. Cursor says that Project is on track to touch 20 to 100 pull requests a day; that is Cursor's own example, not an independent benchmark. (Cursor's Projects announcement)

Migrations and long-running maintenance

Cursor says Projects are useful for migrations that are easy to start but difficult to finish. The coordinator can apply an agreed approach incrementally across hundreds of pull requests, with closer review early in the migration and less review as the fixes hold up. (Cursor's Projects announcement)

The same Project can continue after a feature ships. Cursor says it can monitor logs, handle bug reports, and use the original decision context when maintaining the feature. That makes the Project a home for a body of work rather than a disposable task session. (Cursor's Projects announcement)

Beta status and what Cursor does not say

Cursor says Projects are in beta and rolling out to all users from the left-hand navigation. The announcement does not state pricing, plan requirements, geographic availability, platform coverage, a limit on the number of Projects, or a limit on the number of agents or subagents. (Cursor's Projects announcement)

Cursor also reports that new users merged 30% more pull requests and users who primarily used Projects merged six times as many. Those are company-reported results from Cursor's own usage, not a controlled external study, so they are best read as directional product evidence rather than a promise of a specific outcome. (Cursor's Projects announcement)

Bottom line

Projects turns Cursor from a collection of agent sessions into a coordinator-led workspace for features, migrations, and ongoing maintenance. The useful shift is not just more subagents: it is the combination of accumulated context, cloud work that continues while a laptop is closed, local testing when needed, and subscriptions that let a Project respond to PRs, Slack, or a schedule. (Cursor's Projects announcement)

Sources

• Cursor on X, “Introducing Projects,” September 10, 2026: https://x.com/cursor_ai/status/2098162488013455784
• Cursor, “Introducing Projects”: https://cursor.com/blog/projects