# Share What Trae's Agent Produced — A URL Instead of a Side Panel

Canonical: https://commareports.com/agents/share-trae-output
Published: 2026-09-09

> Trae's builder writes the plan, the review, the analysis into a panel in your editor. Attach the Comma MCP server and it publishes finished work to a link your team can comment on.

# Share what Trae's agent produced

Trae's builder mode is aimed at the tasks that are more than an edit: plan the
refactor, review the module, work out what the migration touches. The result is
a structured document in a side panel, which is the correct place for you to
read it and the wrong place for anyone else.

The gap shows up immediately. The reviewer wants the analysis, not the diff.
The PM wants the plan. Neither of them is opening your editor, and the
alternatives — a screenshot, a paste into chat, a paragraph in the PR
description — each drop a different half of the document.

## Let the agent publish it

Attach Comma's [MCP server](/mcp) in Trae's MCP settings with a
[scoped token](/docs/api-tokens), then add a project rule so the behaviour
applies to every conversation in the workspace:

```md
When you finish a piece of work a human needs to read — a refactor plan, a
module review, a migration analysis — publish it to Comma as an HTML report and
reply with the URL. Do not paste the full document into the chat panel.

The report id is in `.comma-report-id`; update that report on later passes
rather than creating a new one.
```

The pull request then carries a link to a document anyone can open, and the
panel goes back to being your workspace rather than everyone's bottleneck.

## Why a report and not a panel

- **It renders.** Tables, diffs and generated diagrams survive intact — markup
  is stored verbatim and served inside a sandboxed iframe.
- **Readers need nothing.** A browser, and the access setting you chose.
- **Comments anchor to the paragraph.** "Step 3 assumes the read replica is
  caught up" stays on step 3 — see [commenting on HTML](/comment-on-html).
- **The agent can read the replies** over the same MCP server, so review
  feedback becomes the next prompt — see
  [letting an agent respond to comments](/agents/let-an-agent-respond-to-comments).
- **One URL across passes.** Revisions accumulate at the same address, so the
  link in the ticket never goes stale.

## Worth knowing

- **Scope the token down** to `reports:write`, plus `comments:write` only if
  you want replies — see
  [scoped tokens for AI agents](/agents/scoped-tokens-for-ai-agents).
- **Publish private first**, then widen — see
  [sharing & access control](/docs/sharing).
- **HTML body: 5 MB.**
- **Nothing re-executes.** A snapshot is a snapshot; scheduled refreshes are
  [routines](/docs/routines).

## Try it

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

**[Attach the MCP server →](/mcp)**

### Related

- [Share what Cursor produced](/agents/share-cursor-output) ·
  [Share what Windsurf produced](/agents/share-windsurf-output)
- [Where should my agent post?](/agents/where-should-my-agent-post) ·
  [Give an agent feedback](/agents/give-an-agent-feedback)
- [MCP setup for every client](/mcp) · [The API](/docs/api)