Coding agents · Access note

Cursor cloud canvases: sharing and environment limits

A shared canvas is a team view. Paid-plan eligibility, privacy settings and repository access still apply.

Edited by Clinton FeyisitanAnnounced Published

Review scope: The 16 October announcement and two Cursor documentation pages read on 17 October. Sharing, repository access, API behavior and load speed were not tested.

What changed on 16 October?

Cursor’s announcement adds interactive canvases to cloud-agent work and introduces a beta Environments API for managing saved cloud environments. Environments now support up to 300 repositories.

Who can open a shared canvas?

The sharing documentation describes a browser link that gives team members a read-only snapshot. Sharing requires an eligible paid plan: Premium and higher, Teams, Enterprise, or legacy Pro, Pro+ and Ultra. Free accounts cannot publish shares.

You must belong to a team, including when using an eligible individual subscription. The privacy setting must permit data storage; Legacy Privacy Mode prevents sharing. Administrators can disable shared canvases for the organization. A canvas link is therefore not evidence of anonymous public access.

What the environment limit means

The Create an Environment API documentation describes personal or team ownership and a maximum of 300 repositories. A repository the source-control integration cannot reach produces a repository-access error. The limit does not grant access to a repository or establish the cost of running agents.

Use this in your evaluation

The Cursor profile and Cursor/Copilot guide retain their dated evaluations. The coding task worksheet provides a place to record your own bounded result. This documentation check does not establish a new winner, price or performance result.

Source scope

Official documentation read 17 October 2026. Dated claim receipts. This source note records availability and feature boundaries; prices, comparative quality and live workflow results were not verified.