Guide

Collect review comments on an HTML or Markdown document and let the agent fix it

Updated 30 October 2026

Publish the document on ashare.net and open it to the reviewers: your company, specific emails, or anyone with a password. They select text and comment, and each thread stays on its text in later versions. Your agent lists the open threads over MCP or the CLI, publishes a fixed version at the same link, replies in each thread and resolves it. To pin comments on a live website with screenshots and a task board, a website feedback tool such as BugHerd or Markup.io fits better.

The review loop

1. Publish and pick the reviewers. The agent calls publish with the HTML or Markdown, then share with the reviewers’ emails, or sets visibility: "company" for everyone on your email domain. A new document is private until then.
2. Reviewers comment. They open the link, sign in with a 6-digit code from their email (or Google or Microsoft), select a sentence and write a comment. Open threads are highlighted in the text, and anyone with access can reply in a thread.
3. You hear about it. ashare.net emails you about new comments, at most one email every 5 minutes per document. A webhook gets them at once. notify: "off" silences one document.
4. The agent reads the threads. list_comments returns the open threads, each with the quoted text and the version it was made on.
5. The agent fixes the document. edit replaces one exact fragment, a typo or a number; update rewrites the whole document. Both take base_version, so a fix never overwrites a version someone published in the meantime.
6. The agent answers. reply says what changed, resolve closes the thread.
7. Reviewers see the change. The agent sends a link like /a/<id>?v=3&diff=2: version 3 with the changes since version 2 marked, added text in green, removed text struck through.

Ask your agent in plain words

With the Claude Code plugin or any agent connected over MCP (Connect your agent), you don’t name the tools:

Publish spec.md for the company and share it with anna@example.com too.
Collect the open comments on the spec, fix what they ask, reply in each thread with what you changed and resolve it.
Send me the link to the diff between the last two versions.

Another agent can pick up the same threads later. Codex publishes the report, Claude Code handles the comments a day after: the document and its threads live on ashare.net, not in one agent’s session.

Comments across versions

A thread is tied to the text it quotes, not to a position on the page. When the new version still has that text, the thread is highlighted there, even if the paragraph moved. When the text is gone, the thread says “Not in v4” and links to the version it was made on. That is how a reviewer checks the fix: the comment on the old wording either moved with the text or points to where it used to be.

Readers pick any version in the header and compare it with an older one. HTML is compared word by word, Markdown line by line. If the history should stay private, hide it: readers then see only the current version and its threads.

Markdown, reports and HTML prototypes

• Markdown. A .md file is shown as a formatted page, and reviewers comment on the rendered text, the way they would in a Google Doc.
• HTML prototypes. Scripts run, so buttons, tabs and charts work. The page loads from a separate host in a sandbox, so its scripts never see the reader’s ashare.net session.
• Sites of several pages. Publish a folder, up to 200 files and 25 MB: pages link to each other, CSS and images load.
• What a comment can attach to. Text. To comment on a chart or a button, select its caption or label.

The same loop from the CLI

For scripts and agents that run shell commands, with a key from ashare.net/me/api:

$ ashare comments <id>
$ ashare edit <id> --old "Q3 revenue: 1.2M" --new "Q3 revenue: 1.4M" --base-version 2
$ ashare reply <id> <thread> "Fixed in v3: the number now comes from the October export"
$ ashare resolve <id> <thread>

ashare comments <id> --all adds resolved threads; ashare reopen opens one again. See CLI and MCP tools.

When a website feedback tool fits better

ashare.net reviews documents that an agent wrote and will fix. Tools built for website feedback do other jobs well.

A dash means we did not find it on the tool’s own site on 30 October 2026.

• BugHerd works on a live website. Clients point at a page element and comment, without an account. Every comment comes with a screenshot and the browser, operating system and screen resolution, and becomes a task on a Kanban board, which its integrations send on to Jira, Linear, GitHub, Trello or Asana. Pick it for QA on a site in production or staging.
• Markup.io takes over 30 file types, websites, images, PDFs and videos among them. Reviewers drop pins anywhere on the content and guests never sign up. Pick it for design files, video and mixed creative work.

Pick ashare.net when the document is a report, a spec or a prototype your agent wrote; when it must stay closed to everyone except your company or named people; and when you want the agent, not a person, to read the comments and publish the fix. On ashare.net a reviewer signs in with an email code before commenting, so each comment has a real author.

Related

• How to share an HTML report or dashboard with a client
• How to share a Markdown file as a link
• ashare.net as a display.dev alternative: where each one is ahead
• Claude Code HTML instead of Markdown: write it, open it, share it