Cursor ยท Hidden Features

Agents

Hand tasks to Cloud Agents, formerly Background Agents, run several agents at once, and use subagents for noisy or parallel work.

Cursor agents

Three kinds of agent worth separating

Agent in your editor works alongside you. A Cloud Agent, which Cursor used to call a background agent, runs on its own machine and returns a pull request. A subagent is a helper the main agent starts, with its own context window. Telling these apart helps, because they cost, fail and get reviewed differently.

The limit is your environment and your review

Cursor calls environment setup the most important step for Cloud Agents, since an agent that can't run your tests can't check its work. The other limit is you. Every parallel agent produces a diff that someone has to read, so start with a few independent tasks and increase from there.

Frequently asked
What happened to Cursor background agents?

They're now called Cloud Agents. Cursor's help still explains the term, and says each one runs on a dedicated virtual machine and can open a pull request when it finishes.

Which Cursor plans include Cloud Agents?

On The X Subscription, Premium and higher, Teams and Enterprise include them, while Free and Plus don't. Legacy Start, Pro, Pro+ and Ultra plans also include them.

How do I start a Cursor Cloud Agent?

Select Cloud in the dropdown under the Agent input, go to cursor.com/agents, or mention @cursor in Slack, GitHub or Linear. A source control connection is needed first.

How many agents can I run at once in Cursor?

Cursor's docs say you can run as many Cloud Agents as you want in parallel. Each subagent uses its own tokens, though, so five in parallel use roughly five times as many as one.