A few weeks ago I spent twenty minutes hunting for a ChatGPT conversation I knew existed.
It was a debugging session. The model and I had traced a race condition in a KV cache layer — and the final write-up was genuinely good: why the bug only fired under concurrent writes, the fix, and a checklist for avoiding that whole class of bug. Three weeks and a hundred chats later, ChatGPT's search couldn't surface it. I re-derived everything from scratch.
That's when it hit me: AI chat is where a growing share of my real engineering work happens — and it's the worst archive I own.
Think about what's sitting in your ChatGPT (or Claude) history right now:
jq
incantation you will absolutely need againIn any other tool, we'd call these documents. We'd file them, tag them, grep them.
In ChatGPT, they're just... chat number 247.
I tried everything before building my own solution, so you don't have to:
The official export. ChatGPT will happily email you a ZIP of your entire history — all of it, at once, as raw HTML and JSON. It's a backup, not a filing system. You can't export the one conversation that matters, and let's be honest: nobody ever greps the ZIP.
Copy-paste. The copy button under each reply grabs Markdown, and Notion converts most of it. But it's one message at a time, your own prompts aren't included, and long tables and code blocks arrive mangled. For a 30-message thread, that's your afternoon.
Share links. A share link is a bookmark, not a copy. The content never enters your workspace, your search can't index it, and the link dies the moment you delete the chat.
Every one of these fails the same test: can I find this answer in 30 seconds, three months from now?
The fix that stuck for me was piping conversations directly into Notion — my system of record — at the moment they prove useful. Full thread, both sides, formatting intact, auto-tagged.
Full disclosure: I couldn't find a tool that did this well, so I built one. It's called Clipno — a Chrome extension that saves a ChatGPT conversation to Notion in one click. Code blocks stay code blocks, tables stay tables, and the same click works for Claude and Gemini. The free plan covers 50 saves a month. If you'd rather compare every approach first (including the manual ones above), I wrote up the full breakdown here: How to save ChatGPT conversations to Notion.
But honestly, the tool matters less than the habit. Whatever your stack is — Notion, Obsidian, a git repo of Markdown files — the principle is the same:
If an AI conversation produced something you'd hate to lose, get it out of the chat app and into your system of record — the same day.
Here's what I think is actually going on: engineering knowledge is quietly moving into AI chat windows, but our filing habits haven't followed. We meticulously organize our repos, wikis and ADRs while our best debugging sessions accumulate in an app with no folders.
The people who close that gap first — who treat AI output as a first-class part of their knowledge base — are going to compound their work in a way the rest of us won't.
How do you handle this today? Do you save your best AI conversations somewhere, or do they just scroll away? Genuinely curious what systems people have landed on. 👇