Cursor launched environments for cloud agents: multi-repo and versioning

Cursor launched new tools for configuring development environments for cloud developer agents. The main problem: an agent that can write code but cannot run tests, call APIs, or perform builds is useless. Cloud agents need environments similar to your laptop — with cloned repositories, installed dependencies, access to APIs and build systems.

Multi-Repository Environments

In large companies, code is spread across dozens of repositories. Microservice architecture requires changing code in multiple places simultaneously — a new API needs to be integrated into three microservices, added to the database, and the frontend updated. Cursor added support for multi-repo environments — now a single agent can see all the repositories it needs simultaneously and understand how changes in one part of the project affect others. This is especially useful for large organizations.

Amplitude uses Cursor Automations in their Slack channels. According to Stephen Chen, Senior Engineering Manager at Amplitude: the agent can figure out the problem, determine which repos it affects, and open a PR with fixes in the right places with full context.

What multi-repo support provides:

• Agent sees connections between different repos and microservices
• Can open PRs with changes in multiple places simultaneously
• Reuses one environment across sessions — doesn't recreate from scratch
• Gets the full project context needed for complex tasks
• Works with tools that require access to multiple repos at once

Docker Configuration and Automatic Building

Cursor improved support for Dockerfile-based configuration for cloud environments. Innovation: build secrets — a secure way to pass private keys for package registries directly in the Dockerfile. These secrets are used only during image build and don't end up in the agent's working environment.

Layer caching accelerated builds by 70% — only changed layers are used. This is critical with frequent environment updates. If you don't want to write a Dockerfile from scratch, Cursor can generate it automatically. The system scans your repos, determines the tools and dependencies needed, and outputs ready configuration for versioning. The feature is currently in private beta, rolling out to Enterprise customers.

Versioning, Audit, and Security

Cursor now better understands the state of the dev environment during work. During setup, the system asks questions, highlights missing credentials, validates configuration. The agent sees which version of the environment it's working in. Reliability has been added: if configuration fails, the agent doesn't crash but switches to a base image with warnings. Each environment has been given version history — you can view changes and roll back to an old version. Admins can restrict rollback to themselves only.

An audit log records every action. Now ingress and secrets accumulate at the level of a specific dev environment. The team can give different access levels to different environments — for example, staging can have access to production APIs, while dev only has access to mock services.

What This Means

Cloud agents are moving out of experimental tool status into production development. Full-featured environments with multi-repo, versioning, and security controls make them capable of serious tasks — from finding and fixing bugs to completely deploying features. For engineering teams, this means that a significant part of routine development can move to the cloud.