Cursor Projects: A Coordinator Agent for Long-Running Code Work

A coordinator that outlives the chat

Cursor launched Projects on September 10, 2026 for work bigger than a single request: a feature spread across several pull requests, a migration, or a whole app. A Project centres on a coordinator agent that does not write code itself. It keeps context across months of work and hands tasks to subagents, which Cursor says can number in the thousands. [1]

Each Project runs on its own cloud computer, so closing a laptop does not stop it, and starts a local agent when something has to be tested on the user's machine. The coordinator can subscribe to a Slack channel, a schedule, or a repository's pull requests, fixing failing checks and acting when requests open or merge, without being prompted. [1]

Atlas interpretation: This moves the unit of work from a conversation to a standing assignment. Cursor 3 made the editor a place to run agents; Projects makes one of those agents a manager that waits for work to appear. [1][3]

Who got it, and what the numbers show

Projects shipped as a beta rolling out to all users. Cursor's documentation, as retrieved twelve days later, says it is not available on Enterprise plans, and its cloud agent documentation says cloud agents are charged at API pricing for the selected model. Describing several months of using Projects internally, Cursor says new users merge 30 percent more pull requests and those who mainly use it merge six times as many. [1][3][4]

Atlas interpretation: The productivity figures appear to come from Cursor's own staff, with no stated sample or baseline, and people who choose to work mostly through Projects are unlikely to resemble everyone else. They show enthusiasm among adopters inside the company that built it, not a measured effect. Projects arrived less than a month after SpaceX completed its purchase of Cursor. [1][2]