Anyone who has used Claude Code for more than a few days knows the problem: you close a session and the conversation vanishes. Three weeks later, a teammate asks why you restructured the auth module, and you're digging through commit messages trying to reconstruct your reasoning.
A new open-source tool called Claude Session Tracker takes a simple approach to fixing this. Run npx claude-session-tracker and it creates one GitHub Issue per Claude Code session, logging every prompt and response as timestamped comments on that issue. Since GitHub Issues can reference pull requests natively, you get a paper trail connecting the AI conversation to the actual code changes it produced.
The sessions also link to a GitHub Projects board, so you can see all your AI-assisted work in one view and filter by date, project, or contributor.
This solves a real gap. Claude Code's built-in session history is ephemeral. If you're working solo, that's annoying. If you're on a team where multiple people use AI coding assistants, it's a genuine accountability problem. Code review is harder when you can't see the conversation that led to a design decision.
The implementation is lightweight - it hooks into the session lifecycle and pushes to GitHub's API, so there's no separate database or service to run. Everything lives where your code already lives.
One limitation: this only works with Claude Code specifically, not other AI coding tools. And since it stores full conversation logs in GitHub Issues, teams working on proprietary code should check whether their org's policies allow conversation content in issue trackers.
For solo developers and small teams already deep in the GitHub workflow, it's a practical addition. The npx one-liner means you can try it in about 30 seconds.