FluidDocs CLI turns your prompts into interactive documents that answer questions and report back. You see who opened it, how far they got, and what they asked. Pitch decks, proposals, reports, board updates. One line installs the CLI and one command publishes. Edit later by prompt, and the same link updates. Viewer-side AI-enabled Q&A and analytics come built in.
Hey Product Hunt, we are thrilled to launch the FluidDocs CLI. 🎉
FluidDocs are interactive documents that keep doing their job after you hit send: readers ask them questions and get answers from the document itself, and you see who opened them, how far they got, and what they asked.
The reason we built a CLI is that more than half of the 1,000+ documents created on FluidDocs, were created programmatically, by coding agents working through our MCP, not by a person clicking in the app. Our users' agents were already writing the documents. They needed a first-class way to publish and maintain them.
So now one line installs fld, and from there everything runs in the terminal:
✅ Publish a file, a zip, or a whole directory as an interactive document ✅ Turn on reader Q&A with one command ✅ Pull reader analytics back into the terminal ✅ Edit the live document later, and the same link updates ✅ --json on every command, so your coding agent can run the whole flow unattended
The best way in: install, run fld login, and publish something you already have. Or try the SpaceX S-1 as a FluidDoc at https://share.fluiddocs.ai/spacex-s1 and ask it a question a static document could never answer.
We are taking command and workflow requests all week. Tell us what your publishing flow needs and we will build it.
Really interesting approach to making documents interactive instead of static. The built-in Q&A and engagement analytics could be especially useful for pitches and proposals. How does FluidDocs handle AI-generated answers when viewers ask questions that go beyond the original document?
@nishant_aggarwal When I send someone a doc, do they need an account or an app to ask it questions, or does the link just work in their browser? My clients will not sign up for anything, so this is the whole decision for me.
I'm looking forward to digging in to see how I could use it with the Kithli pitch deck as we prepare to raise a pre-seed round. But, even before that with the Revenue Leakage research project we're running with ASCs.
I send PDFs for basically everything at work and the "same link updates" thing alone would fix so many wrong-version situations. Nice work.
@nishant_aggarwal Not a terminal person at all, is there a way to do this without the command line, or is that the whole point?
One of the cool things about the CLI (vs MCP) is that it's a lot faster, and you get a very readable trace of the commands that the agent executed, then you can use it to build especialized document skills with greater control.
For example a very simple loop that I use when I publish a fluid doc, is to use claudecode + cli to get the questions that the users have asked on the document's QNA chat to improve the document itself.
About FluidDocs CLI on Product Hunt
“Publish interactive docs that answer and report back”
FluidDocs CLI launched on Product Hunt on August 13th, 2026 and earned 124 upvotes and 14 comments, placing #11 on the daily leaderboard. FluidDocs CLI turns your prompts into interactive documents that answer questions and report back. You see who opened it, how far they got, and what they asked. Pitch decks, proposals, reports, board updates. One line installs the CLI and one command publishes. Edit later by prompt, and the same link updates. Viewer-side AI-enabled Q&A and analytics come built in.
FluidDocs CLI was featured in Design Tools (262.1k followers), Productivity (659.3k followers) and Artificial Intelligence (477.1k followers) on Product Hunt. Together, these topics include over 315.4k products, making this a competitive space to launch in.
Who hunted FluidDocs CLI?
FluidDocs CLI was hunted by Nishant Aggarwal. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how FluidDocs CLI stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Nishant Aggarwal
Hey Product Hunt, we are thrilled to launch the FluidDocs CLI. 🎉
FluidDocs are interactive documents that keep doing their job after you hit send: readers ask them questions and get answers from the document itself, and you see who opened them, how far they got, and what they asked.
The reason we built a CLI is that more than half of the 1,000+ documents created on FluidDocs, were created programmatically, by coding agents working through our MCP, not by a person clicking in the app. Our users' agents were already writing the documents. They needed a first-class way to publish and maintain them.
So now one line installs fld, and from there everything runs in the terminal:
✅ Publish a file, a zip, or a whole directory as an interactive document
✅ Turn on reader Q&A with one command
✅ Pull reader analytics back into the terminal
✅ Edit the live document later, and the same link updates
✅ --json on every command, so your coding agent can run the whole flow unattended
The best way in: install, run fld login, and publish something you already have. Or try the SpaceX S-1 as a FluidDoc at https://share.fluiddocs.ai/spacex-s1 and ask it a question a static document could never answer.
We are taking command and workflow requests all week. Tell us what your publishing flow needs and we will build it.