
"How I Auto-Capture Coding Sessions From 25+ AI Tools (Architecture Deep Dive)
How many AI conversations did you have this week? 10? 50? 100? How many can you find right now? That's the problem. AI coding tools generate enormous amounts of knowledge — architecture decisions, debugging sessions, implementation discussions — and all of it vanishes when you close the terminal. I built a system that captures every AI conversation automatically. It works with 25+ tools. The entire architecture is a hook, a CLI, and a parser pipeline. Here's how it works. The Problem: Knowledge That Disappears Every AI coding tool stores conversations differently: Claude Code writes JSONL to ~/.claude/projects/ Codex writes JSONL to ~/.codex/sessions/ Cursor stores data in SQLite ChatGPT is accessible only via export Copilot Chat logs to VS Code output channels Some tools give you hooks. Some give you files. Some give you nothing. I needed one system that could ingest all of them, normalize the data, and make it searchable. Not a viewer for each tool's format — a unified knowledge base
Continue reading on Dev.to
Opens in a new tab



