Let Cursor Automations share Canvases

Ideas Feature Requests
, ,
1

Feature request for product/service

Cloud Agent (GitHub, Slack, Linear,…)

Describe the request

I want to make a Cursor Automation that evaluates a GitHub PR and posts a comment with a link to its analysis as a Canvas. Cloud Agents don’t currently have the ability to do that.

4

good request, it might actually be covered in another feature request in here, I will try if I can find it so that I’ll send it link in here, in the meantime, upvoted :white_check_mark: !

6

Hey @IsaacAtAsh!

Cloud Agents don’t support Canvases yet. That would be a blocker to letting Automations use them. Hope we can make progress on this soon! Canvases are one of my favorite Cursor features.

9

You can get this working today without waiting for Canvas support: have the automation generate the analysis as a plain HTML file and push it to a doc-hosting tool over MCP, then post that URL in the PR comment.

I build Markloop (disclosure) which works this way: the agent pushes the HTML, you get a stable link, and reviewers can leave anchored comments on the analysis itself. Cursor connects to it over MCP.

11

Feature request for product/service

Cloud Agent (GitHub, Slack, Linear,…)

Describe the request

We want to use Cursor Cloud Automations to generate recurring analytical dashboards (metrics, trends, category breakdowns) and distribute them to stakeholders.

Today there is a gap between what Automations can deliver and what Canvas provides: On desktop, agents can build interactive dashboards as .canvas.tsx using the cursor/canvas SDK. In Cloud Automations, the Canvas runtime/SDK is not available, so agents cannot create or publish Canvas artifacts as part of an automated run.
THe Automation has Slack integration, but it cannot send file attachments. So we sending an HTML report (or screenshot) through Slack directly is not an option. The fallback is storing reports in external object storage (S3/GCS/etc.) and sending a link — extra infrastructure, auth, retention policy, and maintenance we would prefer not to own.

What we need

For Cloud Automations, please support an end-to-end Canvas publishing workflow:

  1. Create/update a .canvas.tsx dashboard from agent output (same cursor/canvas components as desktop).
  2. Publish a new Canvas from an automation run.
  3. Sync/update an existing Canvas when the automation re-runs (same dashboard, refreshed data).
  4. Return a stable shareable URL the automation can post to Slack (or other channels) — no file upload required.

Operating System (if it applies)

MacOS