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
Why Your Claude Code UI Output Drifts and How a Structured Spec Fixes It
A developer explains that inconsistent UI output from Claude Code isn't a prompt problem — it's a format problem. Providing exact hex codes, font weights, spacing, screen states, and transitions eliminates drift. They also open-sourced an MCP server that converts screen recordings into structured specs.
Upfront: A Claude Code Plugin That Forces Thinking Before Coding
Upfront is a Claude Code plugin with 20 skills that challenges developers before generating code. It uses three commands: /upfront:feature to push back on vague requirements, /upfront:plan to break work into ~400 LOC phases, and /upfront:build to execute with TDD and review per phase.
Claude Code Lazy-Loads Tool Schemas via ToolSearch to Save Tokens
Claude Code defers tool schema loading by sending only tool names upfront and requiring a ToolSearch call to fetch schemas before use. This architecture cuts token burn significantly.
W2A — an open protocol for agent sensors: giving local agents real-time perception
W2A (World2Agent) is an open protocol standardizing the perception layer for AI agents — self-hostable, TS SDK, Apache 2.0. It lets agents receive real-time signals from sensors without one-off scripts.