Canvas published links don't auto-sync; not teammate friendly for shared dashboards

Ideas Feature Requests
1

Feature request for product/service

Describe the request

I love the Canvas feature, but it could be more collab friendly-

When a Canvas is published and shared with teammates via a link, they only see the latest version after the owner manually clicks “Sync” in the Published dropdown. There’s no way to automate this - no CLI flag, no API endpoint, no webhook.

This makes Canvas not practical for team dashboards. My use case: I have a live data dashboard that refreshes its data automatically on my machine, but teammates always see a stale version because I have to remember to click Sync every time.

Request: either (1) auto-sync the published link whenever the canvas file changes on disk, or (2) expose a programmatic way to trigger sync (CLI command like cursor canvas sync, or a REST API endpoint) so it can be wired into an automation or cron job.

Operating System (if it applies)

MacOS

7

Thanks for the feedback @Blair_Jiang! We have some plans here, nothing concrete to share yet. Glad you’re finding Canvases useful, hope we can make them even more useful. :slight_smile:

9

+1. I keep a daily-refreshed internal dashboard as a Canvas — the rebuild is fully automated, but the final “Sync” to the published link is still manual. A cursor canvas sync CLI command (or auto-sync on file change) would let me fully automate it via my scheduled job.

10

I would like to be able to automatically publish a canvas as well as have it auto sync. I’m doing incident triage polling different data sources for metrics, etc, and publishing a canvas with updates to findings and status across vendors and services. The local canvas updates without issue, but i’d like it to auto sync after reach run so that my stakeholders are automatically kept up to date with the latest information. Having a central updated source of consolidated information is much better than sending out notifications.

11

Feature request for product/service

Cursor SDK

Describe the request

Feature request for product/service

Cursor IDE — Shared / Published Canvases

Organization

Mosai (healthcare / software engineering org). We use Cursor Enterprise daily for engineering leadership dashboards.

Describe the request

We regenerate Engineering Leader (EL) pod heatmaps every morning on a scheduled job (Windows Task Scheduler → local data fetch → .canvas.tsx rewrite with embedded PNG data URIs). Local canvases are always current. Published share links for engineering leaders stay stale until someone manually opens each canvas and clicks Publish → Sync.

That last mile blocks the value of Shared Canvases for us:

~11 pod × Full + Weekly canvases = many Sync clicks every morning (Weekly daily; Full weekly).

Stakeholders open a stable share URL expecting today’s numbers; without Sync they see yesterday’s snapshot.

There is no documented CLI, REST API, webhook, or Cloud Automation path to refresh an existing published canvas.

Ask (either is enough; both preferred):

Auto-sync — when a published .canvas.tsx changes on disk (or on save), refresh the existing share URL automatically (opt-in per canvas).

Programmatic Sync — e.g. cursor canvas sync and/or a REST endpoint so our morning job can push the snapshot after regen, keeping the same share link.

Nice-to-haves:

Batch Sync for a folder of published canvases.

Cloud Automations / Cloud Agents able to create + publish + re-sync canvases and return a stable URL (for Slack/Teams distribution).

Why this matters for Mosai

Canvases are the right artifact for exec/EL heatmaps (layout + embedded visuals). Without auto or API Sync, we either:

burn engineering time on daily manual Sync, or

abandon published canvases and host PNGs elsewhere (Teams/SharePoint), which loses the Canvas share UX Cursor already built.

Staff previously acknowledged related requests (“we have some plans… nothing concrete yet”). Filing this as an explicit Mosai production use case so product can weigh enterprise dashboard refresh against the current snapshot model.

Operating System (if it applies)

Windows 10/11 (scheduled local regen + Cursor desktop Publish/Sync)

Contact

Mosai / Vishal Kapadia

Operating System (if it applies)

Windows 10/11