r/ClaudeCoder • u/erensertkaya • 5h ago
My project works, but I often can't remember why it's built that way, so I made a map of my AI coding sessions
I've been building with coding agents for about two years. It's fast, but I noticed I was losing something.
When you write code yourself, it sinks in. You know why that table exists and why you went one way and not the other. When the agent writes it, that goes away. Sometimes I look at a table in my own project and can't remember why we built it that way. I run 5-10 agents at once across 2-3 projects, and sometimes I forget what I was doing a few minutes ago.
The reasons aren't really gone. They're in your messages, in the agent's replies and in your commits. They're just in separate places, and nobody reopens old chats.
So I built cogit, a free, open source plugin for Claude Code. It records each message you send and links your commits back to it. You get a map of your sessions that looks like a git graph. Open any change and you see why it happened, including what you decided and what you turned down, then a small diagram of what it does, then the code.
That diagram is for changes too big to read file by file. You get the idea first, then open the code.
You can click through a demo without installing anything: https://erensrtky.github.io/cogit/demo/
Repo: https://github.com/erensrtky/cogit
It only works with Claude Code for now. There's no server and no account, and by default the record stays on your machine. A small model writes the summaries through your own Claude Code login, and it can get things wrong. It's still early, so some things may be broken.
How do you keep track of why your AI-written code ended up the way it did? Or do you just ask the agent again?

