FluidDocs CLI - Publish interactive docs that answer and report back

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.

Add a comment

Replies

Best

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 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.

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.

Ā being an active MCP user myself, I feel that difference so much as well :)

Not a terminal person at all, is there a way to do this without the command line, or is that the whole point?

,Ā we just launched our CLI today. But we have a full web app that you can try by signing up for a free account at , and you won't need to use the terminal at all. The terminal is just one of the ways to use it.

I send PDFs for basically everything at work and the "same link updates" thing alone would fix so many wrong-version situations. Nice work.

Ā that's one of my favorite parts too. You can try it free at

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.

Ā those are great use cases - would be very happy to give you a demo/help answer any questions at all :)

congrats on the launch. excited to try it out

Ā thanks for the support. Would love to hear your feedback!

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?

FluidDocs is essentially a file system, so for context beyond the document, a user can point the AI Q&A chat to any other document in the file system. That is a feature available out of the box. Additionally, we offer advanced features to be extended to documents/context outside of FluidDocs as well (e.g., Google Drive, OneDrive, etc.). Would be very happy to give you a demo :)