← Back to the saved comparison

Cursor: the evidence

This page explains the answers in the comparison. Each section gives an answer, its limits, and the vendor documentation behind it.

Configuration: Cloud Agents · Team Pools. Enterprise · repository-backed worker · GitHub checkout.

Customer-managed Team Pool worker with service-account authentication. These answers apply to this setup; other ways of using Cursor may work differently.

AI-Buzz saved these answers on . This is a documentation review; AI-Buzz has not tested this configuration. Check later corrections.

Where commands run

Cursor · Cloud Agents · Team Pools

Company-managed worker runs file edits and terminal commands. The team operates the worker infrastructure.

Limits of this answer: Customer-managed tool execution does not mean offline inference.

The machine where the agent edits your files and runs builds and tests.

Self-Hosted Machines

Why this source is relevant: Team Pools move tools to the customer worker while Cursor supplies the agent loop. Artifact transfer and plan prerequisites are separate.

Short excerpt from the vendor’s documentation:

Your worker performs file edits

Where to read the full passage: How it works; What leaves your network; Requirements

Open the vendor’s current page

Where model requests go

Cursor · Cloud Agents · Team Pools

Cursor cloud runs inference, planning and the agent loop. The worker sends tool results and needed content to Cursor.

Limits of this answer: Exact model, provider and inference region are unspecified; needed content leaves the worker.

Model hosting is separate from where commands run. A local tool can still use a remote AI model.

“LLM” means language model. “Inference” means that model generating a response. “Orchestration” means coordinating the agent’s next steps. The machine editing your files and the service answering model requests can be in different places.

Self-Hosted Machines

Why this source is relevant: Team Pools move tools to the customer worker while Cursor supplies the agent loop. Artifact transfer and plan prerequisites are separate.

Short excerpt from the vendor’s documentation:

Your worker performs file edits

Where to read the full passage: How it works; What leaves your network; Requirements

Open the vendor’s current page

Team Pools

Why this source is relevant: Repository-backed Team Pool routing, registered Git remotes, service account authentication, dashboard and API requests.

Short excerpt from the vendor’s documentation:

A Cursor Enterprise plan

Where to read the full passage: Prerequisites; Pool names; Triggering pool agents

Open the vendor’s current page

Where your code lives

Cursor · Cloud Agents · Team Pools

Repository-backed workers use an accessible Git checkout. This record selects the documented GitHub repository workflow.

Limits of this answer: Selected scope: a GitHub checkout already accessible to the worker. Other SCM hosts are not established here.

The code-hosting service or local Git repository used by this setup.

Team Pools

Why this source is relevant: Repository-backed Team Pool routing, registered Git remotes, service account authentication, dashboard and API requests.

Short excerpt from the vendor’s documentation:

A Cursor Enterprise plan

Where to read the full passage: Prerequisites; Pool names; Triggering pool agents

Open the vendor’s current page

How work starts

Cursor · Cloud Agents · Team Pools

Select a pool in the Cloud Agents dashboard or direct a request to that pool through the API; team routing settings apply.

Limits of this answer: The request must target the configured pool; ordinary requests may use Cursor-managed machines.

How you can give the agent a task.

Team Pools

Why this source is relevant: Repository-backed Team Pool routing, registered Git remotes, service account authentication, dashboard and API requests.

Short excerpt from the vendor’s documentation:

A Cursor Enterprise plan

Where to read the full passage: Prerequisites; Pool names; Triggering pool agents

Open the vendor’s current page

How you review the result

Cursor · Cloud Agents · Team Pools

File edits happen on the worker. Uploaded artifacts can appear in pull requests and the Cursor dashboard.

Limits of this answer: Artifact upload can be blocked. Automatic PR creation for every worker setup is not established.

Where the proposed code changes appear and how you review them.

Self-Hosted Machines

Why this source is relevant: Team Pools move tools to the customer worker while Cursor supplies the agent loop. Artifact transfer and plan prerequisites are separate.

Short excerpt from the vendor’s documentation:

Your worker performs file edits

Where to read the full passage: How it works; What leaves your network; Requirements

Open the vendor’s current page

What you need to use it

Cursor · Cloud Agents · Team Pools

Enterprise plan, team admin configuration and a service-account API key are required for Team Pool workers. Workers need the CLI and outbound HTTPS.

Limits of this answer: Enterprise and team admin configuration apply. Region and release stage are not established.

The plan, accounts and permissions you need. This is not a cost estimate.

Team Pools

Why this source is relevant: Repository-backed Team Pool routing, registered Git remotes, service account authentication, dashboard and API requests.

Short excerpt from the vendor’s documentation:

A Cursor Enterprise plan

Where to read the full passage: Prerequisites; Pool names; Triggering pool agents

Open the vendor’s current page

Self-Hosted Machines

Why this source is relevant: Team Pools move tools to the customer worker while Cursor supplies the agent loop. Artifact transfer and plan prerequisites are separate.

Short excerpt from the vendor’s documentation:

Your worker performs file edits

Where to read the full passage: How it works; What leaves your network; Requirements

Open the vendor’s current page

What this page cannot tell you

These sources describe how this configuration is documented to work. They do not show its success rate on real tasks or establish when a product change happened.

The linked vendor pages may change after retrieval. Where permission to keep a full page is unresolved, we retain a short attributed interpretation and excerpt, with a pointer to the relevant section.

Read the configuration overview · See all coverage and limits · Download the saved answers and sources (2026-09-08.1, JSON)