Cursor has given its cloud agents a place to work. The AI coding company rolled out development environments on 13 May that let a single configuration hold all the repositories an agent needs, reusable across sessions. The unglamorous part is the point. An agent is only as useful as the environment it runs in.

What shipped

Three changes stand out. Cloud agents now support multi-repo environments, so one setup can span the several codebases a real task touches. Docker builds got a layer-caching upgrade: change the Dockerfile and only the altered layers rebuild, which the company says makes cache-hit builds 70 per cent faster. And build secrets let an agent reach private package registries during a build without those secrets leaking into the running environment.

The quality-of-life bits

Cursor will now interview you as it sets up an environment, asking questions, flagging missing credentials and checking the configuration works before an agent starts. Each environment keeps its own version history, so a team can review changes and roll back. For teams that would rather not write a Dockerfile, Cursor can inspect the repos, work out the dependencies and generate one to edit.

Why it matters

The gap between a coding agent that demos well and one a team trusts on a live codebase is mostly setup: the right repos, the right secrets, a build that does not take ten minutes. Closing that gap is less exciting than a new model, and more decisive for whether agents get used. Cursor is competing with GitHub, Replit and a field of cloud players on exactly this ground, and the winner will be whoever makes the boring parts disappear.