Guide

Share HTML reports from Codex, Cursor, Gemini CLI, ChatGPT and CI

Updated 30 October 2026

Connect your agent to the ashare.net MCP server at https://ashare.net/mcp and ask it to publish the file. It gets back a link and sets who opens it: everyone at your company, specific people by email, or anyone with a password. Readers sign in with a code sent to their email and comment on the text; the same agent, or another one, reads the comments and fixes the document. Scripts and CI use the CLI or the GitHub Action with an API key.

Connect your agent

Most clients sign in through the browser, so there is no key to copy.

OpenCode, VS Code with Copilot, Windsurf and stdio-only clients: Connect your agent.

Choose who opens it

A new document is private: only you open it. Then tell the agent who else gets in, in plain words:

• Your company. “Share it with the company” opens it to everyone who signs in with an email on your company domain.
• Specific people. “Share it with marta@agency.com” adds up to 100 emails; each one gets a letter with the link.
• A password. “Make it public with a password, expiring in 7 days” lets in anyone who has both the link and the password, until the date.

Someone else who opens the link sees “You don’t have access” and can ask you in. You approve or deny the request from the email or through the agent. For private and company documents you also see who opened it and when.

Publish without a person in the loop

claude -p and the Agent SDK. Create a key at ashare.net/me/api and pass it as a header:

claude mcp add -s user --transport http ashare https://ashare.net/mcp --header "Authorization: Bearer $ASHARE_API_KEY"

Scripts. The CLI reads the key from ASHARE_API_KEY. A folder goes up as a small site: pages link to each other, CSS, scripts and images load.

$ npx ashare-cli publish report.html --title "Nightly benchmark"
$ npx ashare-cli comments <id>

GitHub Actions. Publish the report on every pull request and post the link in a comment. The next push updates the same document and the same comment. See GitHub Action.

permissions:
  contents: read
  pull-requests: write
steps:
  - uses: Magir/ashare-action@v1
    with:
      file: report.html
      api-key: ${{ secrets.ASHARE_API_KEY }}
      visibility: company

The review loop is the same for every agent

1. The agent publishes and sets who opens the link.
2. Readers sign in with a code from their email, select text and comment.
3. The agent lists the open threads, edits the document, replies and resolves them.
4. Each fix is a new version at the same link, and readers can compare any two versions.

Agents can hand a document to each other: Codex publishes the report, Claude Code picks up the comments a day later. The document and its threads live on ashare.net, not in one agent’s session.

Related

• Claude Code HTML instead of Markdown: write it, open it, share it
• How to publish an HTML report from GitHub Actions and share it
• How to save HTML from ChatGPT, open it and share it