Share what Zed's agent produced
Zed is fast, and the agent panel is right there next to the code, which is exactly why people use it for the long questions — trace this call path, explain what this service actually guarantees, compare these two designs.
Then the answer is in a thread in an editor. The design review is on Thursday and the two people who most need to read it do not have the repo open.
Add Comma as a context server
Zed's context servers are MCP servers, so Comma slots in as one more entry in your settings with the endpoint and a Bearer token from API tokens. The shape is the same one described in MCP setup.
Then tell the agent where finished work goes, in the rules the project already carries:
When you produce a document rather than an edit — a design comparison, an
investigation, a walkthrough — publish it to Comma as an HTML report and reply
with the URL only.
The design-review case
This is the one that pays for itself. A design comparison written in an agent thread is invisible; the same comparison published is something you paste into the calendar invite, and everyone arrives having read it and having left their objection anchored to the specific trade-off they object to — see commenting on HTML.
Why a page
- It renders, in a sandboxed iframe, tables and diagrams intact.
- Readers need no editor. Not Zed, not a checkout, not a licence.
- A stable URL across revisions. Update the same report and the invite link still works.
- The agent can read the objections back and revise — see letting an agent respond to comments.
Worth knowing
reports:writeonly — see scoped tokens.- 5 MB per report body.
- Snapshots, not live views. Nothing re-executes on open.
Try it
Free — unlimited reports, commenters and revisions.