Cursor cloud agents can now build shareable canvases

Cursor's cloud agents can now hand you a finished dashboard or report, and you can send it to your team as a link. The changelog for Oct 16 says "Cloud agents can now build interactive canvases as part of their work." Cursor posted it on X at 4:33 PM ET.

What changed#

• Canvases from cloud agents. Canvases already ran next to the chat in the Cursor app. Now a cloud agent can make one while it works. "Ask for a dashboard or report while the agent works, then share the finished canvas with your team as a link" (@cursor_ai).
• Environments API, in beta. You can "create and manage cloud agent environments programmatically, including the repos they clone and the environment.json setup they run" (@cursor_ai).
• Bigger, faster environments. The changelog says environments "now support up to 300 repositories" and "Large environments also load 5x faster."

Why it matters#

Our read: a cloud agent that ends with a page a manager can open is easier to act on than a chat log. The API means teams can keep agent environments in code and set them up in scripts, the same way they handle CI.

How to use it#

1. Start a cloud agent and ask for a canvas. Prompt (ours):

When you finish, build a canvas that shows what you changed, the tests you ran and anything that still fails, as stat tiles and a table, so I can share it with my team.

2. Our read, based on Cursor's canvas docs, which say "a card appears at the end of the response": open that card when the cloud agent finishes. To share, "Use Publish from the canvas toolbar to publish or refresh a share, then copy the link" (docs).
3. To script an environment, send POST https://api.cursor.com/v1/environments with owner (personal or team), name, repos and environmentJson (docs). There are also list, get, update, delete and history endpoints.

Good to know#

• A share is a snapshot. The link shows "a live snapshot of the view," read-only, and you refresh it with Publish (docs).
• Not everyone can share. Shares need a paid plan, a team and a privacy mode that allows data storage. "Legacy Privacy Mode blocks it," and admins can switch shared canvases off (docs).
• 300 or 500 repos? Cursor's X post says "up to 500 repos." The changelog and the API docs say "Maximum 300 repositories." Cursor hasn't said which number is right.
• Beta means it can change. The API docs say "APIs may change before general availability."

What to watch#

Whether Cursor settles the 300 vs 500 repo limit, and whether a shared canvas can refresh on its own.