Comma

Share what Manus produced

An autonomous agent that works in its own cloud VM has the report distribution problem in its purest form. The agent researched the market, built the comparison, wrote a genuinely good HTML deliverable — inside a machine you do not have a shell on. What you get back is a file and a share link on the vendor's domain.

That link is fine for showing one person one thing. It is the wrong container for work that has to be reviewed: the access model is theirs, the retention is theirs, the URL says who generated it rather than who owns it, and there is nowhere for a reviewer to write "this number is from last quarter" next to the number.

Republish it to a URL you control

The agent produces a real file. Publishing it is one call:

curl -fsS -X POST https://commareports.com/api/v1/reports \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html deliverable.html \
        --arg title "Competitive landscape — Q3" \
        '{title: $title, html: $html}')"

You get back a report id and a URL. Paste the URL wherever the question was asked. If your Manus session can reach the network directly, hand it a scoped token and it can make that call itself as the last step of the task — the same pattern every other agent uses, see where should my agent post?.

For a one-off, dragging the file into Comma does the same thing without a terminal.

What you get that the vendor link doesn't give you

  • Your access rules. Private, link-only, or restricted to your team, per report — see sharing & access control. And password protection when the reader is outside your org entirely.
  • A comment thread anchored to the content. Reviewers highlight the row and reply there — see commenting on HTML.
  • A revision history. Re-run the task, PATCH the same id, and the link in the email still works while the previous version stays readable.
  • Faithful rendering. Charts, tables and scripts survive, sandboxed — see interactive HTML reports.
  • A URL that outlives the session. Not tied to a workspace, a seat, or a vendor's retention window.

Worth knowing

  • HTML body: 5 MB. A research deliverable with base64 images can exceed that; publish the document and attach the heavy assets.
  • Read it before you widen it. An autonomous agent browsed the open web and wrote whatever it found. Publish private, read, then share.
  • Scope the token. If the agent holds the token, reports:write and nothing else — see scoped tokens for AI agents.
  • Nothing re-executes. A published report is a snapshot; a recurring refresh is a routine.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish your first report →

Related