Tines The single, secure environment for agents, apps, and automations.
Launching today
Nativ Docs is the collaborative review room for AI-made work. Claude, Codex, and ChatGPT can draft specs, docs, and HTML decks in seconds. But sharing a link only lets people see the work—Nativ lets teams participate in it. • Render Markdown specs & standalone HTML presentations • Highlight exact passages to discuss in the margin • Capture decisions to feed the next prompt or commit • Connect directly to AI workflows via MCP
Hey Product Hunt! 👋
I’m thrilled to launch Nativ Docs. The collaborative review room for AI-made work.
The Problem
We can now generate complete technical specs, strategy docs, and interactive HTML presentations in seconds with ai agents such as Codex and Claude code.
The bottleneck isn’t creation anymore, it’s reviewing:
- Sharing a raw chat link is read-only.
- Pasting Markdown into Slack loses formatting and scatters discussion.
- Moving everything into heavy doc suites strips out code blocks and interactive layouts.
How Nativ Docs Works
1. Bring in the work: Load rendered Markdown or self-contained HTML artifacts (or push them straight from Claude Code / Codex via our MCP server).
2. Review in context: Invite your team to read the rendered artifact.
3. Anchor comments: Highlight exact text to spin up focused discussion threads in the margin.
4. Resolve to decisions: Capture agreed-upon changes so feedback directly improves the next draft or commit.
Try it out
You can try Nativ Docs today with any Markdown spec or HTML artifact. We also built an open MCP server (`@nativdocs/mcp`) so your AI agents can spin up review rooms autonomously.
Sample presentation: https://www.nativdocs.co/s/KzuDX...
Would love to hear how your team currently review AI-generated specs and artifacts?
We'll be here to answer questions and chatting in the comments! 🚀
to answer your question directly - right now my team's "review" step is just pasting the AI's markdown into a Google Doc and leaving suggestion-mode comments, which is exactly the formatting-loss problem you're describing. the part I'm curious about is step 4, resolve to decisions - once comments are marked resolved, does that turn into structured context that gets fed back into Claude Code or Codex for the next generation automatically via the MCP server, or is copying the resolved feedback back into the coding agent still a manual step on our end
Revfx Account Lookalikes
Congrats on the launch ! I have added this as a skill which is very helpful when I am trying to navigate a new code base