Projects in Cursor Agent

A Project takes on work that is too big for one chat: a feature, a migration or a full app. You direct it by talking to its coordinator agent, and the coordinator plans the work, hands it to agents that write the code, and returns the finished work for you to check. Projects sit in the left-hand nav of the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition. and run on Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition..

The docs describe three things a Project does over time: it maintains context over months of work, it delegates tasks to many agents in parallel, and it performs recurring work without being prompted. Projects is documented alongside the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition., Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition., Subagents, Automations and the Slack integration, which the docs list as related pages.

The coordinator never writes code itself. The docs tie that directly to responsiveness: because it delegates rather than executes, it stays responsive to your direction while the work goes on. It also runs as many agents in parallel as the job needs, so one conversation with the coordinator can sit on top of a lot of simultaneous activity.

You are not locked out of the layer underneath. Any agent the coordinator starts can be opened, so you can read what it is doing or talk to it yourself instead of relaying everything through the coordinator.

Each Project is listed under the Projects section of the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition. sidebar, and opening it shows a chat with its coordinator. The model you pick when you create the Project is the one the coordinator uses.

Projects is available on every plan that includes Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition., and unavailable where Cloud Agents are not part of the plan. One privacy setting rules it out as well. The table lays out the cases the docs name.

Both exclusions come from the same dependency. A Project runs on Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition., so a plan without them cannot have one. Privacy Mode (Legacy)A Cursor data setting that blocks Grok Bot because the product requires cloud data storage. Press Enter for the full definition. is excluded for a related reason: Cloud Agents store code in the cloud while they run, and Projects inherit that.

The docs list three blockers: a plan without Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition., an Enterprise Cursor version older than 3.21.9, and Privacy Mode (Legacy)A Cursor data setting that blocks Grok Bot because the product requires cloud data storage. Press Enter for the full definition..

You create a Project from the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition. in four short steps. The steps are below.

1. 1In the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition. sidebar, find the Projects section and click New Project.
2. 2Choose an icon and enter a name. An empty name becomes New Project.
3. 3Under Workspace, pick the repository. Under Model, pick the model the coordinator uses.
4. 4Click Create Project. It opens as a chat with the coordinator.

The repository list is not your local checkouts. Projects run in the cloud, so the menu shows the repositories available to your cloud agents, and if GitHub is not connected yet it offers Connect GitHub. The model choice applies to the coordinator, which is a different job from the agents it starts, since the coordinator plans and delegates rather than writes code.

After that you describe what you want built and the coordinator takes it from there. Cursor's guidance on what to point at is that Projects work best on work that outlives a single chat: a feature with several PRs, a migration, or a job you want handled while you are away.

A Project runs on its own computer in the cloud by default, and it keeps a set of shared files that persist across all of its agents. Those two facts explain most of how it behaves over a long job.

Cloud by default means closing your laptop does not stop the work, and it also lets a Project run more agents in parallel than a laptop could support. When something has to be tested on your own machine, the coordinator starts a local agent to run it there.

Each Project maintains files that sync across every cloud and local machine its agents use. Agents add research and artifacts to them, along with what they learn about the codebase and how you prefer work to be done.

The docs say the shared context grows with the Project, which makes the coordinator more effective over time. The docs describe a Project maintaining context over months of work.

A subscription tells the coordinator to act on a signal without waiting for your prompt. You ask for one in chat, and the coordinator creates it. You can tell it to watch a Slack channel, run on a schedule or follow your pull requests.

The docs give a concrete example. Connect Slack, point the coordinator at a bug-report channel, and it delegates a fix each time a bug comes in.

Once the coordinator has at least one subscription, a Listening pill appears above the chat input. Click it and you see every event the Project listens for: a message posted in a channel, PR activity in a repository, CI runs on a branch, or a schedule such as every day at 8:00 AM. You remove a subscription from that same list when you no longer need it.

The Listening list shows every event the Project listens for, and it is where you remove one.