Reading
Cursor's Canvases Can't Leave Your Team. That's the Catch.
Cursor Cloud Agents now build shareable canvases, but the link only works for your team. Here's what changed on October 16 and who can share.
Prices last read 2026-10-17
Short answer
No. A published Cursor canvas link opens read-only, and only for members of your own team.In its October 16, 2026 changelog, Cursor says Cloud Agents can now build interactive canvases and share them by link. The canvas docs say only members of your team can open a share. To publish one you have to be on a team, on an eligible paid plan, and using a privacy mode that allows data storage. A team admin can also switch sharing off for the whole organization. The same update added a beta Environments API and raised environments to up to 300 repositories.Source: Cursor changelog: Cloud agent canvases and environments · 2026-10-17; Cursor Docs: Canvas · 2026-10-17
What shipped on October 16
Cursor's changelog bundles three changes. First, cloud agents can build interactive canvases while they work, and you can send a finished canvas to your team as a link. Second, a new Environments API, which Cursor labels beta, lets you create and manage cloud agent environments in code. Third, environments now hold up to 300 repositories, and Cursor says large environments load 5x faster. That speed figure is Cursor's own claim. We haven't seen independent benchmarks of it, and we didn't measure it ourselves.
Source: Cursor changelog: Cloud agent canvases and environments · 2026-10-17
Cursor's docs describe a canvas as an interactive view that sits next to the chat. It can hold sections, stats and tables, and you can reopen it, edit it, and rerun it later with fresh data. A share is a live snapshot, so teammates can see the result without rerunning the agent.
Source: Cursor Docs: Canvas · 2026-10-17
The sharing rules, plainly
Anyone on your team can open the link in the browser with read-only access.
Cursor Docs: Canvas (sharing section), read 2026-10-17Source: Cursor Docs: Canvas · 2026-10-17
That sentence answers the headline question. A share link works only inside your team: teammates can view the canvas but can't edit it, and the docs say only team members can open a share at all. There's no public or client-facing link. If you need to show a canvas to a contractor or customer, sharing it isn't the way to do it. Use your own normal process for sharing work outside the company instead.
Source: Cursor Docs: Canvas · 2026-10-17
Before you hit Publish, check these
- You're on a team. The docs say sharing requires team membership, and people on an individual paid plan who also belong to a team can share.
- Your plan is eligible. Free accounts can't create shares. The docs list Premium and higher, Teams, Enterprise, and legacy Pro, Pro+ and Ultra.
- Your privacy mode allows data storage. The docs say Legacy Privacy Mode blocks sharing.
- Your admin hasn't turned it off. Team admins can disable shared canvases for the whole organization under Shared Canvases in team settings.
Source: Cursor Docs: Canvas · 2026-10-17
- PublishClick Publish in the canvas toolbar. This creates the share, or refreshes it if one already exists.
- Copy and sendCopy the link from the toolbar and send it to teammates. They open it in a browser with read-only access.
- Manage your sharesThe Shared Canvases page on the dashboard lists the canvases you've published. From there you can reopen, copy or delete them. It doesn't show your teammates' shares, so ask them for their links.
Source: Cursor Docs: Canvas · 2026-10-17
The Environments API and the 300-repo ceiling
The API reference puts environments under the Cloud Agents API v1, which Cursor calls a public beta that may change before general availability. You can create an environment (POST /v1/environments) with a name, a list of repositories and an environment.json configuration. You can also list, get, update and permanently delete environments, view their configuration history, inspect builds, and manage secrets. Creation takes a maximum of 300 repositories, and the update endpoint changes only the name and configuration, not the repository list. Each environment holds at most 1,000 secrets. If Cursor can't reach a repository through your source control integration, the request fails with a 400 repository_access error.
Source: Cursor Docs: Cloud Agents API endpoints · 2026-10-17; Cursor changelog: Cloud agent canvases and environments · 2026-10-17
Who should care
Platform teams that keep agent environments as code get the most from this update. Because the API is beta, pin it down in your own scripts and expect changes, since Cursor says the endpoints may change before general availability. Individual developers on Free plans can build canvases, but they can't share them.
Source: Cursor Docs: Cloud Agents API endpoints · 2026-10-17; Cursor Docs: Canvas · 2026-10-17
The take: right call, wrong headline
Canvases are the flashy part of this update, but the Environments API is what matters. Keeping read-only, team-only links is a sensible default for a tool that works on private code, and admins will be glad of the off switch. Still, anyone hoping for a Notion-style public link will be disappointed: canvases are for internal dashboards, not client reports. The real upgrade is being able to script and version environments across hundreds of repos instead of clicking through a dashboard. Whether those environments really load 5x faster is something to check on your own monorepo, not something to take from a changelog.
Optional: compare Cursor plan listings from a third-party seller. This is a seller listing, not official Cursor access and not an endorsement.. That link carries our partner code Sk52g, which is how a purchase is attributed to this site. Promotion code UPD3S.
Sources (all read 2026-10-17)