Cursor Cloud Agents builds dashboard showing build status, timestamps, and debug logs Image: Cursor / cursor.com
by VibecodedThis

Cursor Cloud Agents Now Boot 3x Faster With Builds

Cursor's new Builds feature pre-bakes development environments so cloud agents start instantly instead of spending minutes on setup. Ships as default on August 17.

Share

Cursor shipped Builds for Cloud Agents on August 13, and it fixes one of the more annoying parts of running agents on large repositories: the startup delay.

Previously, every cloud session started from scratch. Boot a machine, clone the repo, run install scripts. On big codebases, that could take several minutes before an agent wrote its first line. Starting August 17, all new and existing Cursor environments will use Builds by default, with no extra cost.

How It Works

Cursor now prepares ready-to-use environment snapshots in the background, running on an hourly cycle. When an agent starts, it forks a live machine from the latest build instead of rebuilding from zero each time. Internally, that drops boot times by 10x. Time to first token (the gap between starting a session and the agent’s first output) improved 3x.

The feature also handles broken environments. If a bad commit or a dependency update breaks an environment, agents continue running from the last successful build while Cursor debugs the issue in the background. Failed builds never become active, so your agent fleet keeps working even when something upstream breaks.

Faire, one of the early testers, said their largest repositories now start in seconds. The company said agents can handle 2,000-plus automated runs per week without manual intervention.

What the Dashboard Adds

The Cloud Agents dashboard got observability to match. You can now see:

  • Build status with timestamps and versioning
  • The exact commit SHA captured in each build
  • Build logs for troubleshooting failures
  • Links between agent runs and the specific build they used

That last piece matters for debugging. If an agent produced unexpected output two days ago, you can trace it back to the specific build it ran on and see exactly what the environment looked like at that moment.

The Timeline

Builds are available now for manual enablement. On August 17, Cursor will turn them on by default for all environments, new and existing, without any configuration needed.

The feature ships at no additional cost.

Sources

Share