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
OpenClaw Skill 'Waiting Tips' Shows Learning Tips During AI Response Wait Times
The 'Waiting Tips' skill for OpenClaw sends a random learning tip immediately when a user sends a message, filling the 5-10 second wait time for AI responses with useful content. It includes 75 bilingual tips in five categories and works across multiple messaging platforms.
Architect CLI: Open-source tool for orchestrating headless AI coding agents in CI/CD
Architect is an open-source CLI tool designed for autonomous AI coding agents in CI/CD pipelines, featuring the Ralph Loop for test-retry cycles, deterministic guardrails, YAML pipeline definitions, and support for multiple LLMs via LiteLLM.
OCTO-VEC: Open-source virtual software company with 24 AI agents
OCTO-VEC is an open-source TypeScript/SQLite project that simulates a software company with 9 default AI agents and 15 hirable specialists. It includes automated security scanning, per-agent git identities, and supports 22+ LLM providers.
TideSurf: DOM compression tool reduces web agent token usage 30x, speeds TTFT 12x
TideSurf v0.3 converts rendered DOM to markdown-like compressed format, reducing token consumption by 32x on GitHub pages versus raw DOM while adding 18 interactive tools for LLM agents.