Shared canvas lists but /api/canvas-frame returns 404 for all of my publishes

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Team Shared Canvases work (teammates’ publishes load fine). Every canvas I publish appears in Shared Canvases / gets a share URL, but the body shows “Canvas Not Found”. Frame request returns 404. Teammates also get 404 on my shares.

Steps to Reproduce

  1. Create/open a tiny canvas → Publish
  2. Open share from dashboard or link
  3. Observe “Canvas Not Found”
  4. DevTools: GET https://cursor.com/api/canvas-frame/canvas-…?theme=dark → 404

Expected Behavior

Canvas should open on browser for me and other teammates.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.17.21
VS Code Extension API: 1.128.0
Commit: 8f2a112cb2845a97b75fd932ea5c470579ca4060
Date: 2026-08-25T01:05:08.089Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @SlavaAtBob, thanks for the detailed report, and this one is on us. It is a known issue we are already tracking, and I have added your report to it!

What is happening: your Cursor account is a member of two teams in your org, and a published canvas is attached to whichever team was active when you signed in to Cursor. Your publishes are currently landing under your secondary team, while the share viewer checks against your main team, so it reports the canvas as not found (for you and your teammates).

To get your shares working: sign out of Cursor, then sign back in. When you are asked to choose a team during sign-in, pick the team your colleagues are on. Then open the canvas and hit Publish again. Re-publishing updates the existing share link in place, so your previously shared URLs should start working right after.

If that feels like too much, a simpler option in the meantime: the canvas is just a file, so you can share the .canvas.tsx file itself (plus its .canvas.data.json sidecar if it has one) and teammates can open it directly in Cursor.

Sorry for the trouble, and let us know if the re-publish does not fix it.

Thank you @Colin for you fast response.
Indeed, logging in with the “master team” worked, but I actually want to use the secondary team and that doesnt work.
I guess I’ll get by for now.
Hope you fix it fast :folded_hands: