Skip to content
Bookmarkit
All news
Cursor|Product··Abhishek Kapoor

Cursor Projects is a coordinator for work that outlives a chat. The laptop can close.

On 10 September 2026 Cursor launched Projects: a coordinator that keeps shared context for months, runs cloud agents by default, and can watch Slack, schedules, and pull requests. Cursor-reported productivity multiples stay labeled as vendor numbers.

A dark grid of nodes used as the Cursor Projects cover
Summarize this page with AI

Alexi Robbins and Fredrika Lindh introduced Projects on 10 September 2026. Cursor says a Project is for a feature, a migration, or a full app: work that should outlive one chat. The coordinator does not write the code. It directs other agents. Cloud is the default, so closing the laptop does not stop the job. A changelog entry sits next to the post. The feature is in beta and rolling out to all users from the left-hand nav.

That is a different product from inline completion. It is also a different product from a single Devin worker. Put it on the same sheet as OpenAI’s Agents API and the September coding-agents shortlist.

Coordinator, shared context, subscriptions

  • Coordinator: chats with you, delegates to subagents, stays responsive because it does not implement the diff itself.
  • Cloud by default, local when needed: the Project has its own computer. A local agent runs only when something must execute on your machine.
  • Shared context: files that sync across the cloud and local machines the agents use. Cursor says agents add research, artifacts, and how you prefer the work done.
  • Subscriptions: the coordinator can watch Slack, run on a schedule, or follow pull requests and CI.

Cursor says it used Projects internally for months: migrations of a few hundred pull requests, design-system consistency, and shipping Projects itself. One internal design-system example is “on track to touch 20 to 100 PRs a day.” That is Cursor describing its own team, not a customer study.

Feature, migration, gardening

The post names three patterns. Feature work starts with research into shared context, then a plan, then parallel implementation. Migrations apply one agreed approach across many pull requests, with review getting lighter if the early diffs hold. Gardening is the work that never ends: quality, regressions, lint. A subscription can start that work without a new prompt.

Projects versus Devin, Copilot, and Agents API

  • Cursor Projects: coordinator inside Cursor, cloud computer, shared files, Slack and PR subscriptions. Origin (native git) is a separate surface. See Cursor Origin.
  • Devin / Devin Desktop: a worker and a desktop. If your comparison tab still says Windsurf, read the rename.
  • GitHub Copilot: inline and agent sessions with enterprise permissions. It does not ship this coordinator object.
  • OpenAI Codex via Agents API: a public session API with US-only residency and no ZDR. You bring the environment.

What to verify in a trial

  1. Pick one migration or one recurring job that already failed in a normal Cursor chat. Do not demo a greenfield toy.
  2. Close the laptop after kickoff. Confirm the cloud agents continue and that you can steer the coordinator later.
  3. Read the shared context files. Check that a second engineer sees the same state.
  4. Attach Slack or PR subscriptions on a non-production repo first. Watch what text leaves the building.
  5. Interrupt a subagent. Confirm the coordinator resumes without a full re-brief.
  6. Write down who can start a Project, who can approve its PRs, and where the logs go.

Open the Cursor profile, keep Devin and Copilot on the same shortlist, and save the list. If the trial only proves a faster first commit, you bought a chat with extra chrome. If it finishes a migration you were going to staff by hand, the coordinator earned the seat.