Show HN: A CLI tool that stores Claude Code chats in your Git repo (opens in new tab)

(github.com)

4 pointsjannesblobel2mo ago2 comments

The idea is simple: when working with AI coding assistants, the reasoning behind decisions often disappears once the session ends. Prompts, iterative refinements, and the AI’s explanations, in other words, the context behind why code changes were made is lost.

This CLI tool preserves that context in Git, making Claude code conversations transparent, continuable later, stored alongside code, and shareable with your team via a Git host.

You can test it here: https://github.com/Legit-Control/monorepo/tree/main/examples...

Curious how you handle shareability and persistence of AI conversations, or any ideas for making conversation history more useful and easily shareable.

2 comments

forgotpwd162mo ago

Cool concept. (Legit project overall too.) Any chance it expands beyond Claude, e.g. Codex, OpenCode? Also, unless misunderstood those commits happen in currently working branch? If yes, an option to have the code/sessions mix in alternative (not working) branch will be nice too, as not every project would want to fill history with sessions.

jannesblobelOP2mo ago

Thanks, glad you like the Legit.

On expanding beyond Claude: there’s no concrete plan right now since we built this around Claude, but we’re very open to it. If you have a preferred CLI (e.g., Codex, OpenCode, or something else), feel free to open an issue in the repo. Or just describe your use case here and I will do it :)

Regarding branches: the tool does not pollute your working branch. Each session lives on a separate “session” branch that contains all prompts and operations. Your normal working branch stays clean.

When you end a session, you’re prompted to either:

merge the code changes into your working branch, or

discard them.

If the video or README didn’t make this clear enough, I’d appreciate the feedback I’ll update the docs accordingly.

j / k navigate · click thread line to collapse