Cursor · Cloud Agents · Team Pools
How this setup works: where it runs, how you give it a task, and how you review its changes.
The setup covered here: Enterprise · repository-backed worker · GitHub checkout
Read the six answers below to check whether this setup fits your team. Each “Source” link explains the answer. “Unknown” means the documentation leaves a question open.
- Where commands run
The machine where the agent edits your files and runs builds and tests.
Company-managed worker runs file edits and terminal commands. The team operates the worker infrastructure.
Customer-managed tool execution does not mean offline inference.
Source ↗- Where model requests go
Model hosting is separate from where commands run. A local tool can still use a remote AI model.
Cursor cloud runs inference, planning and the agent loop. The worker sends tool results and needed content to Cursor.
Exact model, provider and inference region are unspecified; needed content leaves the worker.
Source ↗- Where your code lives
The code-hosting service or local Git repository used by this setup.
Repository-backed workers use an accessible Git checkout. This record selects the documented GitHub repository workflow.
Selected scope: a GitHub checkout already accessible to the worker. Other SCM hosts are not established here.
Source ↗- How work starts
How you can give the agent a task.
Select a pool in the Cloud Agents dashboard or direct a request to that pool through the API; team routing settings apply.
The request must target the configured pool; ordinary requests may use Cursor-managed machines.
Source ↗- How you review the result
Where the proposed code changes appear and how you review them.
File edits happen on the worker. Uploaded artifacts can appear in pull requests and the Cursor dashboard.
Artifact upload can be blocked. Automatic PR creation for every worker setup is not established.
Source ↗- What you need to use it
The plan, accounts and permissions you need. This is not a cost estimate.
Enterprise plan, team admin configuration and a service-account API key are required for Team Pool workers. Workers need the CLI and outbound HTTPS.
Enterprise and team admin configuration apply. Region and release stage are not established.
Source ↗