Cursor: Development Environments for Cloud Agents

Configurable Development Environments for Cloud Agents

Cursor released a comprehensive set of tools for configuring the development environments in which cloud agents operate. The release addresses a fundamental requirement for autonomous agent work: agents need an environment comparable to a developer's local setup — cloned repositories, installed dependencies, internal credentials, and access to build systems. Without this, cloud agents could not reliably take engineering tasks from start to finish.

Multi-Repo Environment Support

One of the most significant additions is native multi-repo environment support. Previously, agents were effectively constrained to single-repository contexts. With this release, teams can configure a single environment containing all the repositories an agent needs for its work, and that environment can be reused across sessions.

This matters because most real-world engineering spans multiple codebases. An agent that can only see one repository at a time struggles to reason about inter-service dependencies, make coordinated changes across repos, or test integrations end-to-end. Multi-repo environments remove that constraint, enabling agents to deliver, test, and verify changes that cut across an entire system — not just a single codebase.

Enhanced Dockerfile-Based Configuration

Cursor enhanced its Dockerfile-based environment configuration with two notable upgrades.

Build Secrets

Teams can now include build secrets in their Dockerfiles, enabling secure access to private package registries without those credentials leaking into the running agent's environment. Build secrets are scoped strictly to the build step — they are not passed through to the agent sandbox at runtime.

Faster Layer Caching

Layer caching was significantly optimized. When only part of a Dockerfile changes, only the updated layers rebuild. Cursor reports that cached builds now complete approximately 70% faster, which meaningfully reduces the iteration time when tuning or updating environment configurations.

Agent-Led Environment Setup

Cursor can now participate in setting up and maintaining these environments interactively. When configuring a new environment, Cursor asks clarifying questions, flags missing credentials, and validates that the setup is correct before agents begin work.

If an environment configuration fails entirely, Cursor defaults to a base image and surfaces clear warnings — ensuring cloud agents can keep running rather than stopping immediately. This graceful degradation reduces the risk of a misconfigured Dockerfile blocking all agent activity.

Environment Governance and Security Controls

The release introduces a full governance layer for development environments, targeting teams with security or compliance requirements.

Version History and Rollback

Every development environment now maintains a full version history. Teams can review previous configurations and roll back to them if needed. Admins can restrict rollback permissions so that only authorized users can revert environment definitions.

Audit Logging

An audit log captures every action team members take on environments — providing security teams with complete visibility into who changed what and when.

Scoped Secrets and Egress Controls

Secrets and egress controls can now be scoped at the individual environment level. Secrets configured for one environment are not accessible from any other. Similarly, outbound network access can be configured per environment — one environment might allow broad egress, while another is locked down to a specific allowlist. This prevents cross-environment data leakage and enables tighter security postures for sensitive workloads.

Bug Fixes and Reliability Improvements

Alongside the major environment features, Cursor shipped several reliability improvements:

• The active environment version is always displayed, so agents and users know exactly which configuration is in use.
• Environment defaults are applied gracefully rather than blocking agent execution when configuration is incomplete or invalid.