HTML Artifact Rendering

Ideas Feature Requests
, , ,
1

Feature request for product/service

Cursor Web

Describe the request

Please add support for rendering HTML artifacts directly inside Cursor Web.

Agent-generated outputs are increasingly things like reports, dashboards, research summaries, status pages, and visualizations. Markdown previews are useful, but HTML is often a much more readable and human-friendly format for reviewing this kind of output.

This would make it easier to:

  • Review agent-generated reports

  • View dashboards and visualizations

  • Share progress updates

  • Build richer outputs without needing external hosting

  • Review results on mobile or in Cursor Web without opening a separate deployment environment

Native HTML rendering would make Cursor Web much better for consuming agent outputs, especially as more workflows involve generating artifacts rather than only editing code.

5

Thanks for the suggestion @Duncan-Haywood! One thing we’re definitely looking to do is bring Canvas support to Cloud Agents!

8

Agree that HTML is the right review format for agent output. While this lands in Cursor, the workflow that works today: have the agent write the report as a self-contained HTML file and push it to a review tool over MCP; whoever needs to review it opens a link and comments on the exact chart or paragraph.

I build markloop.io (disclosure) which works this way -Cursor connects to it over MCP, and reviewers don’t need Cursor or any account.