How do I share what Trae's agent wrote?

Attach Comma's MCP server in Trae's MCP settings and add a project rule saying finished work gets published. The agent writes the HTML, calls the publish tool and replies with a URL that opens in any browser.

Where does the standing rule live?

In Trae's project rules for the workspace, which apply to every conversation in that project. Put the publish instruction there once instead of restating it per task.

Why not paste the output into the pull request description?

A PR description is a reasonable home for a short summary. It is a poor home for a 3,000-word migration analysis with tables, and it gives reviewers nowhere to comment except at the bottom, detached from the paragraph they mean.

Can the agent update the same report later?

Yes. Keep the report id in the repo and have the agent PATCH it. The URL stays stable while each pass lands as a revision.

What does the reader need?

A browser. No editor, no licence, no repository checkout — which matters because the reader is often a PM, a designer or a reviewer from another team.

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 in Trae's MCP settings with a scoped token, then add a project rule so the behaviour applies to every conversation in the workspace:

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.
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.
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.
Publish private first, then widen — see sharing & access control.
HTML body: 5 MB.
Nothing re-executes. A snapshot is a snapshot; scheduled refreshes are routines.

Try it

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

Attach the MCP server →

Share what Trae's agent produced

Let the agent publish it

Why a report and not a panel

Worth knowing

Try it

Related