Threaded comments and version history — like Google Docs, but on HTML. Charts stay live. Diagrams stay native. And agents can work through the MCP surface without losing the human thread context.
You wrote something good. Then you flattened it so the team could comment on it.
You sketch the diagram in Excalidraw. Or Figma. Or hand-roll the SVG.
Export as PNG. Drag it into Google Docs. Write the prose around the picture.
Reviewers comment beside the image, because there is no way to comment inside it.
The thread is now about a picture that no longer exists. Repeat from step 1.
I think the value prop is that you get to write docs that include HTML. You're able to be much more expressive in ways that the agent can explain stuff. You don't have to make Excalidraw, then snapshot the picture to copy and paste back into Google Docs. My team writes a lot of slop docs that only live on our local computers.
Half the time the doc never even leaves the laptop. Google Docs flattens it. Linear can't render it. Vercel will publish it but won't let your team comment on it. So the work just… sits there.
HTML is the most expressive document medium your team has. It's the one your agent already writes in, and the one that holds charts, diagrams, animations, and embedded demos without flattening any of it.
Rich Doc takes any HTML and gives it the collaboration most teams expect from
Google Docs — a live URL, threaded comments, resolved-and-reopened threads, version
history. Comments anchor to text or to whole visual elements (img,
svg, canvas). When the agent or author republishes,
every open thread carries forward.
There is no editor to learn. You publish HTML — the format your agent already produces.
Your agents can call Rich Doc through MCP to publish revisions, fetch latest versions, and keep threaded review in place.
Anchor a thread on a paragraph, on the <svg> of a diagram,
or on the <canvas> of a Chart.js dashboard. Reviewers point
at the thing they mean.
When the document changes, comment threads move with it. Open conversations carry forward to the new version — nothing gets stranded on a draft no one is looking at anymore.
Publish HTML. Discuss inside it. Revise — and let the open threads come with you.
Send any HTML document and get back a live URL to share with your team.
Teammates open the URL and thread comments on text, charts, or diagrams. Replies appear live for anyone watching.
Edit the document yourself or hand it to your agent. Open threads carry forward to the new version — nothing gets stranded on an old draft.
Your agent doesn't write Markdown that approximates a chart. It writes Chart.js that is the chart. It draws SVG diagrams. It builds an interactive demo and explains it. Flattening any of that loses the part worth reviewing.
Reviewers anchor a thread on the <canvas> — or on the bar that spiked.
Anchor on a node, an edge, or the whole <svg>. The shape stays the shape.
Animations and interactive demos stay interactive. Reviewers anchor on the part that matters — and your team works in a safely isolated surface.
Charts stay live. Diagrams stay native. Comments anchor to the part of the picture that matters. And every open thread is still there in the next revision.