Draft - Capture AI chats into your knowledge base
by•
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;
Replies
Draft
Hey guys 👋
I built Draft because I kept losing my AI conversations.
Why
I use multiple AI chatbots everyday: ChatGPT for brainstorming, Claude for coding, Gemini for video analysis, Kimi for Chinese OCR and other specialized tools when they are better at one narrow task.
That workflow is powerful but messy. Useful answers end up scattered across chat histories, tabs, screenshots, bookmarks, and broken copy-pastes.
What
Draft is an privacy-first, local workspace that manages your AI chats. It turns useful AI conversations into editable, searchable notes in your own knowledge base. Instead of leaving a great answer buried in a chat thread, Draft helps you save it, clean it, and reuse it later.
How
visit Draft and install Draft Extension.
click extension on the AI chat window.
chat history is sent as MHTML blob to your Draft workspace, saved in local browser storage.
edit, search, listen, and share when you choose.
You can try Draft without creating a general account. The app is in Beta and free to use.
Feedback
I would love your honest feedback:
How do you currently save useful AI conversations?
Which AI platform should Draft support best first?
What would make this workflow worth paying for?
Draft
@lakshminath_dondeti Hi Lakshminath, glad we share the same taste and vision in the AI era.
Yes. Would be great to understand more on your needs. Currently, chats are stored locally in your browser untill you choose to share it. A thumb-up feature on the shared page is an great idea.
Please share the detail of your workflow via in-app feedback channel or connect on X, and we’ll prioritize them to better support your use case.
@lakshminath_dondeti @toliuweijing Good idea thumbs up/down could be a simple but powerful signal for what's worth saving.
Draft
@jaydon_calhoun @lakshminath_dondeti
Thank you for seconding this idea from Lakshminath.
Now I get it more clearly: using the thumbs up/down signals that already exist in many AI platforms could be a simple yet powerful way to decide what is worth saving.
Instead of capturing an entire conversation, Draft could use those feedback signals to help filter the chat that matter most. That fits really well with the product: a lightweight way to turn useful AI conversations into clean, reusable knowledge.
I'm always impressed by those small, elegant interaction that could make the product feel much smarter and more lovable.
Thanks again for the thoughtful suggestion. I can't wait to ship it.
mailX by mailwarm
Do you support auto capture from multiple chat apps, or is it more manual copy and save?
Draft
@thamibenjelloun Hi Thami, nice to meet you.
It is auto capture. Open AI chat window -> One click on Draft extension -> AI conversationis saved. That's it. Watch 30s Video tutorial
Auto-capture supports Chrome the best. Manual copy-paste should work for all browsers. Because Draft is WYSISYG markdown editor.
Let me know what is missing via in-app feedback. We prioritize support for early adaptors. :)
Scade.pro
Draft
@maria_anosova Hi Maria, thanks much for your kind words. Really appreciate your honest feedback, what you like, what is missing.
First, looks like you guys are on the right track - congrats! Is IndexedDB on the roadmap? How brittle is the auto-capture when ChatGPT ships another DOM rewrite? That seems like the real maintenance tax of scrape-based extensions
Draft
@artstavenka1 Hi Art, thanks for the support. And great question!
Yes. AI chats are captured as TipTap JSON blocks, saved to browser local storage(IndexdDB).
Great observation. Here are the tradeoffs we found.
The parser is customized with fixed rules per AI's DOM. Breakage can happen, but the cost is low. Codex can ship the fix with testing in 10mins. We plan to monitor the breakage and proactively shorten the time-to-fix by deploying automated capture tests.
The parser delievers true user values. For example, math formulas, togglable headers are not universial consistent. My research show only Draft can deliver the perfect content elegantly. Neither Notion nor Obsidian deliever this promise.
I would love to share this video, because Draft supports AI math formulas:
Youtube: How to Fix Your Kid’s Math Mistakes with Custom AI Worksheets (1m)
The maintenance tax is real, but I'm surprised on the positive value it brings to the table.
Let me know if you have any questions.
Browser local storage means one machine wipe and the knowledge base is gone. Worth being loud about that before people start relying on it. Congrats on the launch!
Draft
@jared_salois Hi Jared, thanks much for your comment and support.
You’re absolutely right: local-first products need to be very clear about data safety.
We do have local auto backup/restore as a safety measure supported by Chrome. The app prompts new users to configure it on the landing page. If dismissed, user can find the entry in "Settings -> Data Safety".
We are also exploring Bring-Your-Own-Storage, such as user's Google Drive. So users can keep the privacy-first local editor experience while having stronger backup and recovery.
Really appreciate you calling this out. Data safety is something we want to keep improving openly.
Let me know if you have any question / suggestions.
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!
Really useful idea — I lose so much value from long Claude/ChatGPT sessions that I never revisit. Does it capture from multiple AI tools or just one?
Draft
@rich_nashawaty Hi Rich, thanks for the comment and support. Glad this resonates with you.
Draft supports capturing AI conversations from multiple platforms. The workflow is
Open AI chat window -> One click on Draft extension -> AI conversationis saved.
Here is 30s video tutorial. It supports popular AI platforms, e.g. ChatGPT, Gemini, DeepSeek, etc.
Let me know if you have any question or bug report.
@toliuweijing That's a slick workflow — one click to capture is exactly how it should work. Just watched the tutorial, impressive how clean the UX is. Will definitely be putting this to use across ChatGPT and Claude sessions. Thanks for building it!
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.
Call me stupid but, I'm unable to see the use-case. If someone needs to store knowledge, go for Obsidian. Random AI chats being used as knowledge usually increase noise, especially when the AI is allowed to capture information.
Draft
@aakashh242 Hi Aakash, thanks for your comment and support.
That’s a fair question. We admire Obsidian too, especially for people who already have adapted Obsidian's knowledge management habit.
We’re exploring Draft in a different lense:
Loveable UX as Notion, AI-native as Obsidian.
This launch is our first step toward testing that direction with the market. One concrete difference is capturing AI conversations with rich, platform-specific content.
Quick demo: Youtube: How to Fix Your Kid’s Math Mistakes with Custom AI Worksheets (1m)
In that use case, the AI content contains math formulas. Draft’s custom parser is built to handle platform-specific formats so the saved conversation can render cleanly for printing and reuse later. This is where general tools like Notion or Obsidian often struggle to deliver the promise due to fragmentation.
The goal isn’t to replace Obsidian for power users. It’s to streamline AI knowledge capture simple enough for everyday people, with a UX closer to Notion, and the local data that preserves the details people actually want to reuse and feed to AI agents later.