- [new] Builds for Cloud Agents — Cursor prepares ready-to-use copies of your dev environment in the background (repos cloned, dependencies installed, install script run) so agents boot into a warm environment instead of setting up from scratch each session. Builds are included with Cloud Agents at no additional cost.
- [new] Faster starts — Successful builds become the baseline for future agent sessions; warm copies are kept ready. Reported improvements include much faster environment boot and faster time to first token. Use the install command for work that can be prepared ahead of time; keep the start command for services that must be fresh per session.
- [new] More resilient runs — If a bad commit or dependency update breaks the environment, agents keep using the last successful build. The broken build stays inactive, you get notified, and agents can continue while you debug.
- [new] Build history and debugging — Each environment has a Builds tab in the Cloud Agents dashboard (status, logs, commit SHAs, which build each run used). Agents can inspect and manage builds via built-in tools. You can trigger builds manually, debug failing builds with an agent, and control refresh via a configurable staleness threshold.
- [new] Getting started — New environments use Builds automatically. For existing environments, enable Builds from the Builds tab in the Cloud Agents dashboard (or run the setup agent first to review migration/config changes).
Availability
Desktop track versions are unchanged in this interval (latest 3.16.13, stable 3.15.19). The published notes center on Cloud Agents / Builds (dashboard and agent-side), not a new desktop IDE track bump.
Upgrade notes
- Existing Cloud Agent environments: open the environment in the Cloud Agents dashboard → Builds → Enable Builds (or run the setup agent first to validate migration and any proposed config changes).
- Prefer putting preparable setup in the install command; keep start limited to session-fresh services.