Cursor launched Projects in beta on September 10 to coordinate bodies of coding work that last longer than a single agent conversation. Each Project has a coordinator that divides work among coding agents and keeps a shared collection of files, research, and operating instructions. The coordinator manages the work rather than writing code itself.
Projects run on cloud computers by default, allowing work to continue after a developer closes their laptop. A coordinator can start a local agent when a task needs access to the developer's machine. Shared context is synced across those environments, so agents can reuse decisions and testing instructions gathered earlier in the project.
Cursor also added subscriptions that let a Project act on recurring signals, such as a new pull request, CI result, Slack message, or schedule. The company describes using Projects for large migrations and ongoing code maintenance, where a coordinator tracks a sequence of changes rather than an isolated patch.
The feature began a gradual beta rollout, so availability at launch depended on account access.