Cursor adds cloud agent canvases and opens its Environments API in beta

A cloud coding agent that only outputs code gets reviewed by engineers. One that can hand its reviewer a working mock-up gets a wider sign-off list. Cursor has shipped that change, with a changelog entry that also opens its Environments API in beta and raises the ceiling on a single workspace to 300 repositories.

Writing on the Cursor changelog, the Cursor team describes three changes to cloud agents in a single release. All three are additions to the hosted service, so a team already using Cursor's cloud agents sees them with no setup.

What canvases are, in Cursor's words

Cloud agents can now build canvases as part of their work and share the result with a team through a link, Cursor says. The changelog does not state what a canvas can contain beyond that it is interactive, so judge the fit by looking at one before planning any workflow around them. Share links put the review in the hands of whoever holds the link, which is the useful change: a canvas can be opened by somebody who does not have Cursor open or a repository checked out.

Cursor does not state whether the canvas is a static artifact or still reads from the running agent, and does not state what happens to the link when the agent run that produced it ends. Both are worth testing on a real run before putting a canvas in a review workflow.

The Environments API, and a bigger workspace

The Environments API is in beta, Cursor says, and gives programmatic creation and management of the cloud environments agents run in. The team does not state what price tier the beta sits in and does not state a general availability date. A beta behind a changelog line is still a feature that can move or be withdrawn, so treat it as code that will change.

Cursor also says large environments now support up to 300 repositories and that they load five times faster than before. The post names no comparison point for the five times figure and names no measurement method behind it, so it is Cursor's number about its own service. The 300 repository ceiling is the firmer line of the two, because it is a limit rather than a speed-up: a monorepo team that could not fit its working set in a single environment now may be able to.

Cursor's documentation page on cloud agents is the place to read the exact API shape, since the changelog itself does not include endpoints or an example.

Each of the three changes shifts who can review agent work. A canvas pulls in a reviewer who does not read code. The Environments API pulls in a platform team that wants to spin up and tear down environments from its own tooling instead of the Cursor dashboard. And the 300 repository ceiling pulls in a team whose monorepo was over the previous limit. The common thread is the same one Cursor has pulled on through the autumn: moving cloud agents out of the editor and into the places teams already review and ship work.

Source

Cloud Agent Canvases and Environment Improvements, Cursor on the Cursor changelog.