How we set up our cloud agent environment
Cursor’s cloud-agent adoption grew after it treated the dev environment as agent infrastructure: Linux parity, one discoverable CLI, end-to-end testing, and automated repair.
Cursor moved its monorepo onto agent-ready Linux VMs, centralized startup and utilities in an internal CLI, and added end-to-end computer-use testing. Cloud agents went from **roughly 1 in 10 merged PRs in December** to **more than half today**.
Treat the development environment as part of the agent harness. Match cloud and local dependencies, replace fragile command sequences with one discoverable interface, expose verification workflows, and let supervisors own long-running processes.
Cursor moved its monorepo onto agent-ready Linux VMs, centralized startup and utilities in an internal CLI, and added end-to-end computer-use testing. Cloud agents went from **roughly 1 in 10 merged PRs in December** to **more than half today**. Treat the development environment as part of the agent harness. Match cloud and local dependencies, replace fragile command sequences with one discoverable interface, expose verification workflows, and let supervisors own long-running processes. Skills alone only helped at the margins because the underlying commands remained convoluted. Cursor also built **Cursor Cloud MCP** and **Cloud Doctor** to diagnose and repair environment failures, but the adoption figures are internal and do not isolate which change caused the increase.
This makes the development environment a prerequisite for effective cloud-agent skills rather than another supporting detail. Cursor’s internal adoption supports investing in reproducible VMs, discoverable commands, supervised processes, verification, and repair tooling, while the weak marginal benefit from skills narrows skill-centric claims when underlying workflows remain fragile. The adoption increase remains correlational.