What changed
Cursor launched Cloud Agent Builds: background-prepared bootable snapshots containing repositories, dependencies, and completed install steps. New environments use Builds automatically, while existing environments can test and enable them from the Cloud Agents dashboard.
Why it matters
Moving clone and dependency work out of the agent startup path can reduce startup failures and latency, while recorded build commits and logs improve reproducibility when agent runs diverge.
What to do
Move repeatable dependency and compilation work into an idempotent `install` command, keep fresh services in `start` or `terminals`, and test the first Build before enabling it. Review the active commit, staleness threshold, logs, and secret scope for each production environment.
Caveat
Cursor's ten-times-faster boot and three-times-faster time-to-first-token figures are internal and workload-dependent. Builds preserve disk state only, may start from a stale successful commit, and can access team and environment secrets during preparation.