Share what Cascade produced

Cascade will happily spend twenty minutes tracing a performance regression across four services and write you a careful account of what it found. That account then lives in a panel inside your editor, which is roughly the least shareable place a document can be.

Screenshotting it loses the tables. Pasting it into a ticket loses the code blocks. Saving it as a file in the repo means the reader has to clone the repo, which the person who asked usually cannot.

Attach, then make it a rule

Comma is a remote MCP server, so Windsurf needs a URL and a Bearer token — the block is in Windsurf setup, and the token comes from API tokens.

Then write the standing instruction into your workspace rules, so it applies to every Cascade conversation in the project:

When the deliverable is a document rather than a code change — an
investigation, a plan, a benchmark, a risk write-up — publish it to Comma as an
HTML report and reply with the URL. Keep the report id in the project and
update that report on later runs.

The next "why did p99 double" ends with a link you can drop into the incident channel, not with a panel you have to describe to people.

Why a page beats the panel

  • It renders. The flame graph, the before/after table and the aligned diff all survive the trip.
  • No editor required. The people who need the incident write-up are on-call engineers, the support lead and possibly the customer.
  • Comments land on the line. Someone marks the one hypothesis they think is wrong instead of writing "third section, second paragraph" — see commenting on HTML.
  • Cascade can read the replies through the same server and act on them — see letting an agent respond to comments.
  • Context stays small. One URL in the conversation instead of the whole document on every turn — see context budgeting.

Worth knowing

  • reports:write is enough. Don't hand an editor plugin a token that can read the whole account — see scoped tokens.
  • 5 MB of HTML per report.
  • Nothing re-executes. A report is a snapshot; use a routine if it should refresh on its own.

Try it

Free — unlimited reports, unlimited commenters, unlimited revision history.

Set up Windsurf →

Related