Cursor prebuilds Cloud Agent environments for 3x faster starts
Cursor now prebuilds and warms Cloud Agent environments in the background, a change it says makes agents boot 10x faster and reach first token 3x faster than setting up per session.
Cursor's changelog, dated August 13, says agents previously set up their environment from scratch each session — cloning repos, installing dependencies, running the user's install script — before doing any work. Builds moves that work into the background: Cursor runs a new build of each environment on a regular cadence, and when one succeeds it becomes the base image future agents start from. Cursor also keeps warm copies on hand so the next agent does not wait on provisioning. Internally, the company says environments now boot 10x faster with 3x faster time to first token.
Cursor advises putting anything that can be prepared ahead of time into the install command, leaving the start command for services that must be fresh in the session. If a bad commit or dependency update breaks an environment, the broken build never goes active: agents continue on the last successful build and the user is notified.
Each environment gets a Builds tab in the Cloud Agents dashboard, showing build status, logs, commit SHAs, and which build a given agent run used. Agents can inspect and manage builds through built-in tools. Builds can be triggered manually, debugged by an agent, and refreshed on a configurable staleness threshold.
New environments use Builds automatically. Existing ones require opening the Builds tab and clicking Enable Builds, or running a setup agent first to test the migration and review proposed config changes. Builds are included with Cloud Agents at no additional cost. Cursor did not publish benchmark methodology behind the 10x and 3x figures, which it describes as internal.