Cursor has introduced Builds for its Cloud Agents, enabling agents to start from pre-built and verified development environments. This feature prepares the Cloud Agent environment in the background, ensuring that each agent begins from a pre-built machine with repositories, tools, and dependencies already in place.
New environments utilize Builds by default. For existing environments, users can enable Builds through a setup agent that proposes configuration updates or by modifying the .cursor/environment.json file.
Key Points
- Builds are bootable snapshots of prepared Cloud Agent environments, created ahead of agent runs.
- Cursor maintains pre-warmed copies of active Builds, eliminating repository cloning and dependency installation from the agent startup path.
- If a new Build fails, agents continue to use the last successful Build, preventing broken dependency updates or install commands from affecting active environments.
- Builds preserve disk state but do not retain running processes, shell exports, or in-memory caches.
- Builds can access team and environment secrets for private package registries and artifact stores, but user secrets are added only when an agent starts.
- Every agent run records the Build it originated from, providing provenance for comparing environment behavior.
- A Build is triggered on a schedule, when an environment version is saved, by a manual request, or at an agent's request.
Context
According to Cursor, Builds are designed to make Cloud Agent starts faster and more reliable. The system ensures that agents always start from the latest successful Build, and it provides observability by allowing users to inspect Build logs and commits, and trace which Build each agent utilized.
Why It Matters
This feature enhances the efficiency and stability of development workflows by ensuring that Cloud Agents launch with all necessary components pre-configured. Builders can expect quicker agent startup times and a more consistent development environment, reducing time spent on setup and debugging environment-related issues.
What To Do
- Open the Environments section in the Cloud Agents dashboard.
- Select an environment and navigate to its Builds tab.
- Choose to run the setup agent to inspect the environment and propose changes, or select Enable Builds to activate the feature with the current configuration.
- Confirm that the first Build succeeds before deploying it for agent runs.
Keep Exploring
/studio?pack=foundation /techniques/system-user-separation /techniques/ptcf /techniques/output-schema /techniques/constraints /techniques/role-objective /techniques/multishot /techniques/xml-delimiting /techniques/ask-before-inventing /techniques/multimodal-grounding /techniques/direct-blocks-**grok** /atlas/claude-family /atlas/gpt-family /atlas/**grok**-family /atlas/**gemini**-family /atlas/llama-open /atlas/image-models