Tag: cloud-agents

Four ways to run Cursor Self-Hosted Machines workers for Cloud Agents, compared on isolation, pickup latency, session limits, per-session cost, and where the team service-account key ends up. Vercel Sandbox is the default pick, AWS Lambda MicroVMs if agents must reach your VPC.

Use Cursor's /goal command to keep a cloud agent working toward one finish line across many turns. Covers writing a verifiable objective, pinning a Custom Mode playbook, pairing it with /loop and subscriptions, the CLI's durable goals, and how to stop a goal that ignores Stop.

Cursor's Self-Hosted Machines, shipped September 2, 2026, move Cloud Agent tool calls onto hardware you own while inference stays in Cursor's cloud. The agent worker CLI, My Machines vs Team Pools, the three outbound hosts, and the data that still leaves your network.

Cursor shipped Builds for Cloud Agents on August 13, 2026: a bootable filesystem snapshot of an already prepared machine. Cursor reports 3x faster time to first token. The lever you control is the install vs start split in .cursor/environment.json.

Pick Copilot coding agent when the work starts and ends on GitHub and you want issue-to-PR with native branch protection. Pick Cursor cloud agents when you want a live, editor-attached VM, multi-repo tasks, and to take over the run by hand. Full feature matrix, the 59-minute cap, the Actions-approval gotcha, and June 2026 billing for both.

Commit .cursor/mcp.json for the IDE, register shared servers under Dashboard > Integrations & MCP for cloud agents, and keep secrets out of git with ${env:...}. The full two-surface setup for Cursor 3.11 (July 2026), including why the repo file alone does not reach cloud agents.

Step-by-step guide to the Cursor in Jira integration (launched May 19, 2026): install the Marketplace app, assign a ticket to @Cursor, wire repository access and automation rules, and read the PR the cloud agent links back.

Cursor 3.4 (May 13, 2026) lets one cloud agent environment include multiple repositories, adds Dockerfile build secrets, layer-cached rebuilds that run 70% faster, and an agent-led setup step that validates credentials before the first run.