Anysphere, Inc.
The company behind Cursor.
Coding tools included here
Open a product for all six questions about its setup. The answers below cover where it works and what you need to use it.
| Product and setup | What this page covers | Compare |
|---|---|---|
| Cursor · Cloud Agents · Team PoolsEnterprise · repository-backed worker · GitHub checkout | Where it runs, how you start a task, and how you review its work.Customer-managed Team Pool worker with service-account authentication. | See in comparison |
Where the work happens
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 ↗Access conditions
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 ↗