My team uses Claude Code daily, and the sessions have become some of the most useful artifacts we produce. But they're trapped in ~/.claude/projects/ on whichever laptop they happened on. There's no good way to hand a colleague "the session where I untangled the migration" so they can claude --resume it and keep going from where I left off. Enter ccgs: Share Claude Code sessions through an orphan branch (@ccgs/) in your existing repo's remote
-
Session files carry the author's absolute paths. On pull, ccgs rewrites the working dir back to your path so resume actually works — surgically editing only the structural cwd field, not a blind find-and-replace that would happily corrupt the transcript.
-
Everything goes through git plumbing (hash-object/commit-tree/update-ref) against a throwaway index. It never touches your working tree, index, or current branch, and it's fine with a dirty tree. It will not git checkout something behind your back.
To try it without installing: npx claude-git-sessions. This also incidentally allows you to move a directory and carry the claude code transcripts with it (just push first, then move the directory, then pull)
IMPORTANT CAVEAT: Unless you have a very good security hygiene, your Claude Code sessions are likely full of sensitive information such as environment secrets. By . Use with caution and avoid using on public repositories. Branches used by ccgs are prefixed by @ccgs/ so you can easily filter them out.
This project was written by and with Claude Code. This Show HN was not.
(Reposted with URL fixed)
Comments URL: [https://news.ycombinator.com/item?id=48426297](https://news.ycombinator.com/item?id=48426297)
Points: 1