Claude Session Tracker: Auto-Save Claude Code Sessions to GitHub Issues
A developer has released claude-session-tracker, a tool that automatically saves Claude Code sessions to GitHub Issues to preserve conversation history that would otherwise be lost when sessions end.
How It Works
The tool creates one GitHub Issue per Claude Code session, automatically linked to a GitHub Projects board. Every prompt and response gets logged as issue comments with timestamps. The issue title auto-updates with the latest prompt for easy scanning.
Installation and Setup
Install with: npx claude-session-tracker
The installer handles everything: creates a private repository, sets up a Projects board with status fields, and installs Claude Code hooks globally. It requires the GitHub CLI (gh) - if missing, the installer detects this and walks you through setup. The installer is idempotent, so re-running just reuses existing config without creating duplicates.
Key Features
- Creates an issue per session, linked to your Projects board
- Logs every prompt/response with timestamps
- Auto-updates issue title with latest prompt for easy scanning
claude --resumereuses the same issue- Auto-closes idle sessions (30 minute default)
- Pause/resume functionality for sensitive work
Design Decisions
The tool doesn't use MCP (Model Context Protocol) to avoid consuming context window tokens for session tracking. Everything runs through Claude Code's native hook system. All hooks fire asynchronously with zero impact on Claude's response latency.
Why GitHub Over Other Platforms
The developer initially built integrations for Notion, Linear, and Plane but encountered two main issues: linking sessions back to PRs was never smooth, and API rate limits meant silently dropped entries since the tool fires on every single prompt and response. GitHub's API rate limits are generous enough that a single user's session traffic won't come close to hitting them.
This type of tool is useful for developers who want to maintain searchable history of their Claude Code sessions and trace back why specific decisions were made in PRs, since the session lives as a GitHub Issue in the same ecosystem where you can cross-reference PRs naturally.
📖 Read the full source: r/ClaudeAI
👀 See Also
Nelson v2.2.3 Released: Multi-Agent Coordination for Claude Code, Plus a Discrete-Event Simulation Benchmark
Nelson v2.2.3 ships a multi-agent coordination skill for Claude Code using a naval metaphor. A 13-configuration benchmark shows opus-4-7 with thinking dominates; skill choice is a smaller delta.
OpenClaw skill reduces accessibility tree tokens from 600K to 1.3K for ad-heavy sites
A developer built an OpenClaw skill that uses ML-based element ranking to prune accessibility trees, cutting slickdeals.com from ~598K tokens to ~1.3K tokens by keeping only the top ~50 actionable elements.
Crag: Open-source tool generates unified AI agent rules from project configs
Crag is an open-source compiler that analyzes project configurations and generates a single governance.md file, then compiles it into multiple AI agent rule files to prevent configuration drift across tools like Claude Code, Cursor, and Copilot.
Claude Growth Skill: Structured B2B SaaS Growth Playbooks for AI Coding Agents
A developer built a Claude Growth Skill containing 6 battle-tested playbooks based on 5 SaaS case studies, $90M ARR partnerships, and 1,800 user interviews. It structures B2B SaaS growth work from PMF validation to channel ecosystem and sales.