Draft
Capture AI chats into your knowledge base
154 followers
Capture AI chats into your knowledge base
154 followers
Draft captures valuable answers from ChatGPT, Gemini, DeepSeek, vertical chatbots, then turns them into editable, searchable notes. Preserve formatting, organize insights, listen with text-to-speech, keep your knowledge available offline, and share when you choose. Free to use at Beta;
This is a useful wedge. The thing I’d pressure-test is not just capture, but “why did I save this?” A lot of AI-chat history becomes hard to reuse because the answer is detached from the original job, constraints, and whether it was later proven right.
Tiny metadata like source chatbot, original prompt, user thumbs-up/down, project tag, and “used in final work?” could make Draft feel less like a cleaner archive and more like a learning layer for what’s actually worth carrying forward.
Draft
@jim_jeffers Hi Jim, thanks for the comment and support.
That’s a great point. To be honest, my own knowledge base habit is pretty basic: I save things, then later find them mostly through keyword search. I’m always trying to learn better ways to make knowledge reusable.
We auto-capture source link and date today. The next layer is probably improving reusability both at capture time and during retrieval:
Why would future-me want this?
What problem does it solve?
What would make it easier to reuse next time?
This makes me see how manual properties could bring more value than I expected. Thanks for the feedback. Lots to learn here.
@toliuweijing That sounds like the right split. I’d keep the capture-time properties very lightweight so saving doesn’t become homework: maybe one required “save intent” field with chips like use later, verify, cite, template, follow up.
Then retrieval can do the heavier work: “show me saved answers that became useful in final work” is a much better search than “show me everything I once thought was interesting.”
Draft
@jim_jeffers Great insight! That makes a lot of sense.
I love the “saving shouldn’t become homework” framing. A lightweight save-intent field with chips like use later, verify, cite, etc feels way more practical than forcing users to fill in a full metadata form every time.
This is a delightful touch on the UX. Really appreicate your suggestion. I can't wait to ship this!
The problem this solves is real — I use multiple AI tools daily for deal research, financial modeling, and writing, and useful answers constantly get lost in chat history. A dedicated place to capture and organize those insights is genuinely valuable. One adjacent use case I haven't seen addressed well: capturing insights from audio/podcast content. I run a finance podcast called ModeLoop (https://open.spotify.com/show/0m...) focused on financial modeling and deal structuring, and listeners often tell me they want a way to save and revisit specific points from episodes. If Draft ever adds audio/transcript capture alongside AI chat capture, that would close the loop nicely. Congrats on the launch.
Draft
@samir_asadov Thanks Samir, really appreciate your comment and support.
Totally agree this belongs to a very similar problem: valuable knowledge gets trapped not only in AI chats, but also in long-form audio.
And “summarize this podcast” doesn't address the need here. Users need a handy tool to capture insights with source audio context: transcript snippet, episode link, and ideally the timestamp so they can jump back and relisten later.
Draft is focused on AI chat capture first, but audio/transcript capture is a really interesting adjacent direction. It fits the same goal: turn valuable moments from long conversations into reusable knowledge.
Thanks much for the exciting idea. I will bring it to the team for future planning.
Jim — Draft solves a problem I didn't realize was a problem until I had 200+ useful Claude/ChatGPT conversations stranded across different tabs with no way to pull them back together. Capture + auto-organize is the only way knowledge from AI chats scales. Chrome extension format is the right zero-friction surface for it too. Shipped a "background ops" wedge today on PH, kindred ship-rate. Respect.
Draft
@fidele_maniraruta Hi Fidele, thanks much for your comment and support. Glad this resonates with you.
Our mission is to build loveable products that assists everyday people navigate the AI era. Capturing AI chats is the first product we ship. Let me know if you run into issues or have questions.
And we don't stop. We are iterating on Draft CLI to close the gaps between human and remote AI agent. Draft page is the collaboration canvas. Agent propose, human audit. The product delievers better tranparency and quality outcome. Stay tune.
@toliuweijing Jim — "agent propose, human audit" is the framing most teams miss. Everyone's trying to make agents fully autonomous OR keep humans fully in the loop. The middle layer — agent does the heavy lift, human approves the diff — is where real value compounds.
That's exactly how RoutineOS runs: AI proposes overdue appointments + supply reorders, you approve from the morning briefing. Same wedge philosophy, different vertical (personal life ops vs AI chat capture). Excited to follow Draft CLI's evolution.
If you ever want to swap notes on approval-UX or on-device privacy patterns, ping me anytime.
Draft
@fidele_maniraruta That is great man. Glad that both products share common grounds and are built for the future. Let's connect on X. Definitely happy to learn more and exchange thoughts with RoutineOS. :)
@toliuweijing Jim — caught your PH reply, here for the connect. Excited to swap notes on approval-UX between Draft + RoutineOS. Different verticals, same wedge.
What rhythm works for you — weekly check-ins or ad-hoc swap when something interesting comes up? Either fine on my end.
Scade.pro
Draft
@maria_anosova Hi Maria, thanks much for your kind words. Really appreciate your honest feedback, what you like, what is missing.