# Share What Augment Produced — Codebase Analysis With an Address

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

> Augment reads the whole repo and writes the impact analysis, the dependency map, the refactor plan into an editor panel. Publish it to a URL reviewers can open and comment on.

# Share what Augment produced

The value of an agent with the whole repository in context is that it answers
questions nobody could answer from one file: what does this change actually
touch, where is this pattern repeated, what would the refactor cost. Those
answers are long, structural documents — file trees, impact tables, ordered
plans.

And they arrive in an editor panel. The staff engineer who has to approve the
refactor, the team that owns the service you're about to change, the PM who
wants the estimate — none of them are in that panel, and every route out of it
flattens the document.

## Let the agent publish it

Attach Comma's [MCP server](/mcp) with a [scoped token](/docs/api-tokens), then
write the standing rule where your workspace keeps its agent instructions —
`AGENTS.md` at the repo root is the version other tools will also read:

```md
## Publishing analyses

When you produce a whole-repo analysis — an impact assessment, a dependency
map, a refactor plan, a migration estimate — publish it to Comma as an HTML
report and reply with the URL. Do not paste the full document into chat.

The report id is in `.comma-report-id`. Update that report on later passes.
```

The ticket then links to a plan the owning team can read and object to, line by
line, without anyone re-typing it.

## Why a report and not a panel

- **Structure survives.** File trees stay trees, impact tables stay tables. The
  markup is stored verbatim and served in a sandboxed iframe.
- **The reviewer is outside your session** — always, by definition. A URL is
  the only artifact that reaches them at zero cost.
- **Objections anchor to the row.** "You can't move that module, the mobile app
  imports it" stays attached to the module — see
  [commenting on HTML](/comment-on-html).
- **The agent reads the objections** through the same MCP server, so the second
  draft is a prompt away — see
  [letting an agent respond to comments](/agents/let-an-agent-respond-to-comments).
- **Plans change; the link shouldn't.** Revisions at one address let a reviewer
  see what moved since they last looked.

## Worth knowing

- **Publish private first.** A whole-repo analysis quotes your code. Widen the
  access setting deliberately — see [sharing & access control](/docs/sharing).
- **Scope the token down** — see
  [scoped tokens for AI agents](/agents/scoped-tokens-for-ai-agents).
- **HTML body: 5 MB**, which is thousands of rows of file table.
- **Nothing re-executes.** A published report is a snapshot; recurring analysis
  is a [routine](/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 Codex produced](/agents/share-codex-output)
- [Where should my agent post?](/agents/where-should-my-agent-post) ·
  [Context budgeting for AI reports](/agents/context-budgeting-ai-reports)
- [MCP setup for every client](/mcp) · [The API](/docs/api)