Cloud Agents Start 3x Faster with Builds

Summary

Cursor’s Cloud Agents now use Builds, ready-to-use copies of a development environment prepared in the background. These environments include cloned repositories, installed dependencies, and completed install commands, allowing agents to start without repeating setup each session. Cursor refreshes environments regularly, keeps warm copies, and activates only successful builds; internally, environments boot 10x faster and time to first token is 3x faster. If a commit or dependency update breaks a build, the last successful build remains active, while users receive a notification and can debug in the background. Builds can be inspected in the Cloud Agents dashboard, where logs, commit SHAs, statuses, and agent run associations are available, with tools for agents to inspect or manage them.

Takeaways

1. 1

   Builds prepare cloned repositories, dependencies, and install-script work ahead of an agent session, while the start command remains for session-fresh services.

2. 2

   A failed build does not replace the active environment: agents continue using the last successful build, and the failure is reported for background debugging.

3. 3

   The Builds tab shows status, logs, commit SHAs, and the build used by each agent run; agents can also inspect and manage builds with built-in tools.

FAQ