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.
forgotpwd16•1h ago
jannesblobel•1h ago
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.