# Cursor's cloud agents get multi-repo environments By Steven Van · 2026-05-13 Environments come with rollback, audit logs and secret scoping, and 70% faster cache-hit builds via a Dockerfile-based setup. Cloud agents in [Cursor]() can now run inside multi-repo development environments: one environment holding all the repositories an agent needs, reused across sessions. Cursor can configure the environment itself, inspecting repos to work out dependencies and toolchain, or teams can define it via an improved Dockerfile-based setup that supports build secrets scoped to the build step and layer caching that makes cache-hit builds run 70% faster. Each environment now has its own version history with rollback (restrictable to admins), an audit log of every change, and egress and secret scoping at the environment level, so a permissive environment and a locked-down one can coexist, and secrets in one aren't reachable from another. If an environment's configuration fails, Cursor falls back to a base image with warnings rather than stopping the agent. The [announcement]() cites Decagon, Amplitude, BILT and Snyk as users of multi-repo environments. [![]()]() ![Cursor]() Cursor AI code editor built on VS Code — agents that edit across your codebase, run in the cloud, review pull requests, and now host your repos. [View Cursor →]() [Original source]() [Read Cursor's cloud agents get multi-repo environments on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/cursor-cloud-agent-development-environments