Cursor Projects is built for coding work that outlives a chat. It gives that work a persistent home and a memory that can live for months.
Released in beta on September 10, Projects gives a piece of software work a persistent home: conversations, plans, files, a cloud environment, and a coordinator that can keep coming back to the same goal. Cursor had already added isolated subagents to Cloud Agents in August. Projects adds a persistent coordinator that does not write code itself: it breaks work into tasks, delegates them to subagents, follows their progress, and assembles the result while keeping the broader Project context. Cursor says a Project can maintain that context across months of work and, when a job calls for it, delegate tasks to thousands of subagents.
That makes the feature more than a bigger agent window. Cursor is treating project context as durable state. Conversations feed shared context, while research, working instructions, artifacts, and other context can live in files shared across the Project. Each Project gets a cloud computer. Cursor also lets teams move Cloud Agent tool execution onto their own machines when they need custom hardware or private-network access.
Projects also plugs Cursor's existing Subscriptions system into that persistent context. Since August, Cloud Agents have been able to react to Slack activity, pull request changes, and schedules. In a Project, those events can wake the same coordinator that retains the broader history of the work, so an automation can resume with more context than a one-shot agent run.
Cursor says new Projects users merge 30% more pull requests, while users who primarily work through Projects merge six times as many. The announcement does not explain the comparison groups or methodology, so those figures show an association with heavy Projects use, not proof that Projects caused the increase.
Projects is rolling out as a beta to all Cursor users. Now comes the hard part: keeping months of accumulated context useful without letting stale assumptions fossilize into project state. If that works, Cursor has something meaningfully different from a longer chat history.
Worth the Spark
The interesting part is not "thousands of agents." It is continuity. A small team or solo builder spends a lot of time re-explaining goals, reopening context, and babysitting one-shot tasks. Projects ties memory, delegation, triggers, and execution to one durable object. That also raises the stakes for permissions and review. If a Slack message or schedule can start real work, the project needs tighter boundaries than a chat tab.