Cursor launches Projects to coordinate persistent coding agents

• Projects turns a substantial feature, migration, or app into a persistent coordinator thread that directs subagents, Cursor's announcement says.
• Project state includes synced plans, demos, and other artifacts shared by agents and devices, according to Cursor's shared-artifacts post.
• Slack reports, schedules, pull requests, and CI failures can become triggers for work through subscriptions, Cursor's automation post says.
• Projects entered beta on September 10 and began rolling out that day, per Cursor's availability update.

Cursor's launch post says the coordinator itself does not write code, leaving execution to workers. A Project runs on its own cloud computer after the laptop closes, while the changelog says the coordinator can spin up a local agent for machine-bound testing.

The persistent chat acts as a control plane for a body of work. Cursor's launch post describes this loop:

• Coordinator: turns the request into a plan and delegates tasks.
• Subagents: research, implement, and test parts of the plan in parallel.
• Review: the coordinator collects completed work for the developer to check.

Cursor says delegation keeps the coordinator responsive while workers run, and lets it create as many concurrent agents as the work needs.

The memory layer is a set of Project files synchronized across every cloud and local machine used by its agents. Cursor says in its product post that the files can accumulate:

• Research about the system.
• Generated artifacts, including plans and demos.
• Codebase knowledge, work preferences, and testing instructions.

An agent that discovers how to test a service can leave those instructions for later agents. The shared state grows across tasks instead of being rebuilt for each new chat.

Subscriptions give the coordinator event-driven work sources. The official description lists three trigger paths:

• Watch a Slack channel for bug reports.
• Run on a schedule.
• Follow pull requests, including fixing CI when PRs open or merge.

Cursor calls the ongoing-maintenance pattern “gardening.” Its post says a design-system Project is on track to touch 20 to 100 PRs a day, scanning new PRs for components and adding a lint rule after seeing the same mistake twice.

Cursor says it has used Projects for several months on migrations spanning a few hundred PRs, design-system maintenance, and the Projects feature itself. The company's launch post reports that new users merge 30% more PRs, while users who primarily use Projects merge six times as many.

The post does not give a cohort definition, sample size, comparison period, or PR-quality measure for either figure.

Projects is in beta, rolling out to all users from the left-hand navigation, according to Cursor's release post. In an early workflow report, altryne said in a post about their podcast workflow that Projects “DIE” on them one minute before they needed to ship.