How do I add Comma to Goose?

As an extension. Goose's extensions are MCP servers, and Comma is a remote one, so it takes a URL and a Bearer header — `goose configure` walks through adding it, or you can write it into the config file directly.

Can a Goose recipe always publish its result?

Yes, and that is the point of recipes. Put the publish instruction in the recipe and every run of it ends with a URL, whether a human started it or a scheduler did.

Does this work headless?

Yes. `goose run` executes a recipe non-interactively, so a scheduled job can produce the digest, publish it and print only the link.

Why not have Goose write the file and email it?

Because an emailed file has no comment thread and no stable address. Nobody can reply to paragraph three of an attachment, and next week's attachment does not replace last week's.

What scope should the token have?

`reports:write` for publishing. Add `comments:read` if the agent should act on feedback.

Share what Goose produced

Goose runs on your machine with real tools, which means it does the kind of work whose output matters to people who are not you: it reads the logs, runs the queries, ties the incident together, and writes it up.

That write-up ends in a terminal. The incident review happens tomorrow morning, in a meeting, from a document nobody has.

Publishing is just another extension

Goose's extension model is MCP, so Comma is not a special case — it is one more extension with a URL and a token from API tokens. Run goose configure, add a remote extension, point it at Comma's MCP endpoint. The shape is in MCP setup.

Put it in the recipe

Recipes are where this pays off, because a recipe is the thing that runs when you are not there:

instructions: |
  Investigate the alert, gather the evidence, and write the incident summary.
  Publish the summary to Comma as an HTML report and return only the URL.
  If a report id is already recorded for this incident, update it instead of
  creating a new one.

goose run on a schedule then produces one link per incident, and the link is the same one the follow-up updates. See routines if you would rather Comma own the schedule than cron.

Why a page

It renders. Log excerpts stay monospaced, the timeline stays a table.
The audience is wider than your terminal. Incident reviews involve support, the account team, sometimes the customer.
Comments anchor to the moment in the timeline people disagree about — see commenting on HTML.
Goose can read the replies through the same extension and revise — see letting an agent respond to comments.

Worth knowing

A local agent with real tools deserves a narrow token. reports:write and nothing else — see scoped tokens.
5 MB per report body.
Reports are snapshots. No re-execution, bounded cost.

Try it

Free — unlimited reports, commenters and revisions.

See MCP setup →