Skip to main content
Cursor 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:
1

Configure Cursor Cloud Agents

Open the Cloud Agents dashboard in Cursor, and enable the following:
  • Team Pools
  • GitHub token minting
The above Cursor settings are team admin controls, so if you are not an admin on your Cursor team, ask one to enable them.
2

Create a Cursor service account token

In the Cursor dashboard, open Settings > API Keys > Service Accounts, 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 API key. Personal, team, and organization API keys cannot start pool workers.
3

Create Devbox blueprint

Next, create a Devbox blueprint, which defines the environment that Cursor Cloud Agents run in.Navigate to the Devbox 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 for more configuration options.
4

Running the agent

And now, you can run a Cursor Cloud Agent on a Devbox.Start a New Chat, 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:
Agent Prompt

​
How it works

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.
Last modified on September 1, 2026