How to share Claude Code output with your team

Claude Code writes a lot worth keeping: a summary of the refactor it just finished, a postmortem for last night's failing build, a plan for next sprint's migration. Most of it ends up in a terminal scrollback, a Slack message pasted in pieces, or a Markdown file nobody else can open.

This guide shows how to have Claude Code publish that work as a web page your team can read, comment on, and send back for revision, in about five minutes.

What you'll end up with

• A link like offprint.io/@you/build-report-k3n8qz that anyone you send it to can read in a browser. No account, no app.
• Clean formatting: headings, tables, and syntax-highlighted code, with a table of contents for long documents.
• A record of who wrote what. Every revision is stamped with its author ("Set by agent" or "Set by hand") and the client that wrote it, and the full history is one click away.
• A review loop. Teammates leave comments on specific passages, and Claude Code can read them, reply, and publish a revised version.

1. Create an Offprint account

Sign up and claim a handle. Everything you publish lives under offprint.io/@your-handle.

2. Add Offprint to Claude Code

Offprint is a remote MCP server. In your terminal, run:

claude mcp add --transport http offprint https://offprint.io/mcp

Then, inside Claude Code, run /mcp, select offprint, and choose Authenticate. A browser window opens. Sign in, review what Claude Code is asking for (reading and writing your documents), and approve. There's no API key to copy, and you can revoke access at any time under Settings → Connected agents.

To check the connection, ask:

Call whoami on offprint.

Claude Code should reply with your handle.

3. Ask Claude Code to publish

At the end of a piece of work, ask for a write-up. A few prompts that work well:

Summarize what we changed in this session and why, and publish it to Offprint. Give me the link.

Write a postmortem for the CI failure we just fixed: timeline, root cause, the fix, and follow-ups. Publish it to Offprint.

Turn the migration plan we discussed into an Offprint document with a checklist of steps.

Claude Code writes the Markdown, calls publish_document, and replies with two links:

• the readable address, /@your-handle/<slug>
• a permanent short link, /d/<code>, that keeps working even if the document is renamed or moved

Every address ends in a short random suffix, so a document can't be found by guessing its name.

4. Share it

Paste the link anywhere: Slack, email, a pull request description, a ticket. Public documents are unlisted: anyone with the link can read them, and they never show up in search engines.

If the work shouldn't leave your team, ask for it to be private:

Publish this as a private Offprint document.

Private documents open only for you and the collaborators you add. Everyone else sees a "not found" page.

5. Collect feedback and revise

To let teammates comment, add them as collaborators. Open the document's sharing page (add /share to its address) and invite them by handle or email as commenters or editors. To share a whole set of documents at once, share the project from your dashboard instead.

Reviewers select any passage and leave a note in the margin. When the comments are in, go back to Claude Code:

Read the comments on the migration plan, address each one, publish a new revision, and resolve the comments you've handled.

Claude Code uses list_comments to read the feedback, update_document to publish revision 2, and reply_to_comment and resolve_comment to close the loop. Comments stay attached to the right passage as the text changes. Readers see the new revision immediately, and the history shows exactly what changed and who changed it.

Tips

• Keep updating one document. Ask Claude Code to update the existing document rather than publish a new one, so the link and its comments stay in one place.
• Organize as you go. "Put this in the Infra project under postmortems" files it into a project folder, creating the folder if needed.
• Code stays readable. Fenced code blocks are syntax-highlighted, so diffs, configs, and commands come through intact.

Questions

Do readers need an account? No. Anyone with the link to a public document can read it. They only need an account to comment.

Does this work outside Claude Code? Yes. The same server works with Claude Desktop, ChatGPT, Cursor, Windsurf, Zed, Cline, and Continue. See setup for every client.

What does it cost? Public documents are free. Private documents are part of the paid plan. See pricing.