# Cursor Cloud Agents

[Cursor](https://cursor.com) Cloud Agents are natively supported on Namespace Devboxes. When you start a new agent session, Namespace provisions a fresh Devbox for it. Cursor's agent loop, including inference and planning, continues to run in Cursor's cloud, while terminal commands, file edits, git operations, and repository access happen on the Devbox.

## Getting Started

### Requirements

Before you start you need the following pieces:

* [Namespace account](https://cloud.namespace.so)
* Cursor account on the [Enterprise plan](https://cursor.com/enterprise)

###

Open the [Cloud Agents dashboard](https://cursor.com/dashboard/cloud-agents) in Cursor, and enable the following:

* **Team Pools**
* **GitHub token minting**

###

In the Cursor dashboard, open [**Settings** > **API Keys** > **Service Accounts**](https://cursor.com/dashboard/api), and press **New Service Account**. Enter a name, and optionally a description, then press **Create**.

Copy the generated key.

###

**Repository Access** needs to be set to **All repositories from team's connected Git providers**.

Pool workers authenticate with a Cursor [service account](https://cursor.com/docs/account/enterprise/service-accounts) API key. Personal, team, and organization API keys cannot start pool workers.

###

Next, create a Devbox blueprint, which defines the environment that Cursor Cloud Agents run in.

Navigate to the [Devbox Blueprints](https://cloud.namespace.so/workspace/devboxes/blueprints) page, press the **+ New Blueprint** button, select **Cursor** and press **Configure**.

Configure the following:

* `Name` - the name of your blueprint, which only appears in the Devbox list, not in the Cursor UI
* `Cursor` - press **Configure** in the Cursor tile, fill in the following, and press **Save**:
  * `Service token` - the service account key you created in the previous step
  * `Pool name` - the name of the worker pool
* `Operating system` - pick between Linux or macOS, along with the image or macOS version
* `Instance size` - to select the vCPUs and RAM your tasks need

Once everything is in place, press **Create Blueprint**.

###

The **Pool name** appears in the Cursor UI under **Remote Machines** once the blueprint is saved.

See [blueprint configuration](/content/docs/devbox/blueprint.md#additional-configuration/index.html) for more configuration options.

[Guide: Create a Cursor Cloud Agents blueprint](https://app.guideflow.com/embed/ok8v58mfxp)

###

And now, you can run a Cursor Cloud Agent on a Devbox.

Start a [New Chat](https://cursor.com/agents), expand the menu next to the  icon, and select your Devbox **Pool name** from the list of **Remote Machines**.

Select the repository you want to work on, and give your agent a task, like:

```text
What is the operating system you are running on?
```

## How it works

**A**  
**B**  
**Devbox A**  
**Devbox B**  
**A**  
**B**

Every Cursor Cloud Agent session connects to its own isolated Namespace Devbox while the Namespace control plane launches and manages the environments.

Cursor handles orchestration: the agent loop, planning, context management, and inference all run in Cursor's cloud.

Namespace handles execution: shell commands, file edits, repository access, builds, and test runs all happen on a Devbox.

When the session ends, the worker exits and Namespace tears the Devbox down, so each session gets a clean environment and nothing is left running afterwards.