Cursor Shared Canvases: Publish an Agent Canvas and Share It With Your Team via URL

Cursor added shared canvases in the Cursor 3.5 changelog, dated May 20, 2026. The feature lets you share a canvas from Cursor with your team: per the Cursor changelog, you generate a link to a live snapshot of a canvas for teammates to open in the browser. Recipients view it read-only in the Cursor Dashboard, so you hand off a working dashboard or report instead of a full chat thread.

Update (August 26, 2026): this page originally dated the release June 4, 2026, from a cursor_ai post on X. Cursor's own changelog dates it May 20, 2026, and that is now the date this page carries. The X post cannot be re-verified because x.com refuses automated fetches, so it no longer backs any claim here. Cursor's canvas documentation has also since spelled out three eligibility conditions this page did not have: free accounts cannot create shares, you must be on a team, and Legacy Privacy Mode blocks sharing. Everything the page said about the sharing mechanics is unchanged and re-verified below.

If you are new to canvases, start with our explainer on when to ask the agent for a UI instead of text. For where canvases fit Cursor's broader agent surface, see Cursor 3.5 automations and the Agents Window.

Key Takeaways

• What shipped: the ability to share a canvas from Cursor with your team via a link.
• The link is a live snapshot of the canvas that teammates open in the browser.
• Recipients view it read-only in the Cursor Dashboard.
• You share the artifact, not the thread. Instead of distributing a full chat conversation, you distribute the canvas itself.
• Availability: shared canvases are available on Pro, Teams, and Enterprise plans. Cursor's canvas documentation adds that free accounts cannot create shares and that you must be on a team, because every share is team-visible.
• Discovery source: the cursor_ai announcement on June 4, 2026; feature claims verified against the Cursor changelog shared-canvases page.

What Shared Canvases Add

A canvas in Cursor is an agent-generated interactive artifact -- a report, dashboard, or custom interface rendered as a durable object rather than more text. Shared canvases add the missing distribution step. Per the Cursor changelog, you can share a canvas with your team by generating a link to a live snapshot of a canvas for teammates to open in the browser.

The key framing from Cursor: instead of distributing full chat threads, you distribute browser-accessible canvas links. A teammate gets the working artifact -- the dashboard or report the agent built -- without needing to scroll the conversation that produced it.

How Sharing Works

The flow is built around a browser link and the Cursor Dashboard:

• You generate a link to a live snapshot of the canvas.
• A teammate opens the link in the browser.
• They view the canvas in the Cursor Dashboard with read-only permissions.

Because recipients are read-only, sharing is a presentation and review surface, not a collaborative-edit surface. The canvas is a snapshot of the agent's output that others can open and read without touching the underlying thread or project.

When to Use a Shared Canvas

A shared canvas is the right surface when the valuable thing is the artifact, not the conversation:

• Status dashboards. The agent assembled a triage or metrics dashboard and you want the team to glance at it without re-running the prompt.
• Reports for review. You generated a report or analysis and a stakeholder needs to read the result, not the chat that produced it.
• Internal mini-tools. A custom interface the agent built that teammates should be able to open and use read-only.

If the goal is to hand off the reasoning or let someone continue the work, the shared canvas is not that -- it is a read-only live snapshot for consumption.

Caveats and Open Questions

• Claims sourced to official material. The release date and every feature mechanic here come from Cursor-owned surfaces: the changelog shared-canvases page and the canvas documentation. Link-expiry behavior is still not documented anywhere we can find, so we do not assert it.
• Read-only by design. Shared canvases are for viewing, not collaborative editing, per the changelog.
• Plan-gated, team-gated, and admin-revocable. Availability is Pro, Teams, and Enterprise; free accounts cannot create shares; a solo paid seat is not enough because shares are team-visible; Legacy Privacy Mode blocks sharing; and an admin can disable it org-wide. Confirm the current pricing page for a contractual answer.

FAQ

See the structured FAQ in the schema header for question-level details: what shared canvases are, how teammates view them, plan availability, and how this differs from a regular canvas.

Sources

• Cursor changelog, "Shared Canvases and /loop Skill", dated May 20, 2026. Source for: the release date, the live-snapshot link, browser viewing, read-only access in the Cursor Dashboard, and Pro/Teams/Enterprise availability. Re-checked August 26, 2026.
• Cursor docs, "Canvases". Source for: the Publish action in the canvas toolbar, the Shared Canvases dashboard listing, the free-account and on-a-team restrictions, the privacy-mode requirement, and the team-settings admin toggle. Checked August 26, 2026.
• A cursor_ai post on X of June 4, 2026 was this page's original discovery pointer and its original date. It is not cited for any claim here: x.com refuses automated fetches, so the post cannot be re-verified, and Cursor's own changelog dates the release fifteen days earlier.