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
Reddit discussion: Identity.md files insufficient for AI employee personality stability without proper model architecture
A Reddit discussion argues that adjusting identity.md files to prevent personality bleed in AI employee teams is ineffective if the underlying model architecture only simulates role separation. The post recommends using Minimax M2.7 backend, which baked boundary awareness into base training through 100+ self-evolution cycles.
InsForge: Open-Source Backend Platform for AI Coding Agents
InsForge is an open-source backend platform (Apache 2.0) that provides AI coding agents with managed database, auth, storage, compute, hosting, and AI gateway, controllable via CLI or MCP.
OpenClaw Budget Guard Plugin Prevents Concurrent Budget Overspend
A new OpenClaw plugin called @runcycles/openclaw-budget-guard solves concurrent budget overspend by implementing atomic balance checks, reservation before execution, and idempotent retries. It requires a Cycles server with Redis and can be installed via bash command.
AI Functions: Runtime Code Generation with Automated Verification
AI Functions is a Python library that lets you define functions with natural language specifications instead of implementation code, executes LLM-generated code at runtime, and validates outputs with post-conditions that trigger automatic retries on failure.