Cursor Docs

Cloud Agents — Self-Hosted Machines

• Rewrote /docs/cloud-agent/self-hosted as Self-Hosted Machines: run Cloud Agent tool execution on hardware you manage while Cursor runs the agent loop, inference, and planning; covers when to use it vs managed Cloud Agents (strict network, custom hardware/GPUs/Macs, custom images).
• Updated /docs/cloud-agent to point teams who want tool execution on their own hardware to Self-Hosted Machines.
• Clarified on /docs/cloud-agent/self-hosted-guides/choose-runtime that Self-Hosted Machines runs tool calls via My Machines or Pools, with next steps for managed setup, My Machines, and Pools.
• On /docs/cloud-agent/api/endpoints, noted that legacy private-workers endpoint paths refer to Self-Hosted Machines workers.
• On /docs/cloud-agent/self-hosted-guides/cloud-run, renamed references from the fleet management API to the Cloud Agents API for worker-pool autoscaling.

Cloud Agents — My Machines

• Documented registering multiple repository roots on one worker by repeating --worker-dir on /docs/cloud-agent/self-hosted-guides/my-machines, plus troubleshooting when a machine doesn’t appear in the picker.
• Framed My Machines as the personal Self-Hosted Machines configuration; aligned computer-use wording on /docs/cloud-agent/self-hosted-guides/computer-use.