What It Does — Automatic GitHub Issue Logging for Every Session
claude-session-tracker solves a fundamental problem: Claude Code sessions disappear when they end. You lose the conversation history, the reasoning behind decisions, and any context that could help future you or your team. This tool automatically creates a GitHub Issue for every Claude Code session and logs every prompt and response as timestamped comments.
Since sessions live as GitHub Issues in your project's ecosystem, you can:
- Search across all past sessions
- Link issues to PRs naturally
- Track session status on a GitHub Projects board
- Maintain permanent, shareable conversation records
Setup — One Command, Zero Configuration
npx claude-session-tracker
That's it. The installer:
- Checks for
ghCLI (GitHub CLI) and guides you through setup if missing - Creates a private GitHub repository for your session issues
- Sets up a GitHub Project with pre-configured status fields (Created, Last Active)
- Installs Claude Code hooks globally
- Tags each issue with the project name as a label
The installer is idempotent—re-running it just reuses your existing configuration without creating duplicates.
Why GitHub Over Other Tools
The creator built integrations for Notion, Linear, and Plane first, but hit two critical issues:
- Poor PR linking: Connecting sessions back to GitHub PRs was never smooth on external platforms
- API rate limits: Since this fires on every prompt and response (essentially creating a timeline), other platforms' rate limits meant silently dropped entries
GitHub's API rate limits are generous enough for individual usage, and having everything in the same ecosystem eliminates context switching.
Key Design Decisions That Matter
No MCP: The creator deliberately avoided making this an MCP server. Why? To avoid consuming context window tokens for session tracking. Everything runs through Claude Code's native hook system instead.
Fully async: All hooks fire asynchronously, meaning zero impact on Claude's response latency. Your coding flow isn't interrupted.
Smart session management:
claude --resumereuses the same GitHub Issue- Auto-closes idle sessions after 30 minutes (configurable)
- Pause/resume functionality for sensitive work
- Auto-updates issue title with the latest prompt for easy scanning
When To Use It — Specific Workflows That Benefit
- Team onboarding: New developers can search past sessions to understand why architectural decisions were made
- Debugging retrospectives: When a bug appears, trace back to the session where related code was written
- Code review context: Link session issues to PRs so reviewers can see the full conversation behind changes
- Personal knowledge base: Build a searchable archive of your problem-solving approaches
Privacy Protection Built In
The system protects your session data if repository or project visibility changes. If you accidentally make the repo public, the tool has safeguards to prevent exposing your conversation history.
What It Doesn't Do (And Why)
This isn't an analytics platform. If you want metrics like "26% of sessions are abandoned" or "skills used in 4% of sessions" (findings from the Rudel analytics tool mentioned in related coverage), you'd need a different solution. This is purely about preservation and searchability.
Getting Started Today
# First, make sure you have GitHub CLI installed
gh auth login
# Then run the installer
npx claude-session-tracker
# Start a Claude Code session as usual
# Watch as it automatically creates and updates a GitHub Issue
Once installed, every Claude Code session you run will be automatically tracked. No additional commands needed, no prompts to remember—just normal Claude Code usage with permanent history.
