Back to browse
GitHub Repository

Auto-save every Claude Code session to GitHub Projects. Never lose Prompt & Context again.

44 starsJavaScript

Auto-Save Claude Code Sessions to GitHub Projects

by ej31·Mar 14, 2026·2 points·0 comments

AI Analysis

●●SolidSolve My ProblemCozy

GitHub Issues beat Notion for session history because they link directly to PRs.

Strengths
  • One-command installer handles repo creation, Projects board, and global hooks automatically
  • GitHub Issues provide native PR linking that Notion and Linear integrations couldn't match
  • Every prompt and response logged with timestamps for full audit trail recovery
Weaknesses
  • Claude Code only — doesn't support Cursor, Continue, or other AI coding assistants
  • GitHub Projects date fields require manual board configuration after install
Target Audience

Developers using Claude Code who need session history and audit trails

Similar To

Claude session exporters · Linear AI integrations · Notion AI trackers

Post Description

I wanted a way to preserve Claude Code sessions. Once a session ends, the conversation is gone — no searchable history, no way to trace back why a decision was made in a specific PR.

The idea is simple: one GitHub Issue per session, automatically linked to a GitHub Projects board. Every prompt and response gets logged as issue comments with timestamps. Since issues can reference PRs, you get full context tracing between conversations and actual code changes.

npx claude-session-tracker

The installer handles everything: creates a private repo, sets up a Projects board with status fields, and installs Claude Code hooks globally. It requires gh CLI — if missing, the installer detects and walks you through setup.

Why GitHub, not Notion/Linear/Plane?

I actually built integrations for all three first. Linking sessions back to PRs was never smooth on any of them, but the real dealbreaker was API rate limits. This fires on every single prompt and response — essentially a timeline — so rate limits meant silently dropped entries. I shipped all three, hit the same wall each time, and ended up ripping them all out. GitHub Issues via the gh CLI against your own repo has no practical rate limit for this workload. (GitLab would be interesting to support eventually.)

Design decisions

No MCP. I didn't want to consume context window tokens for session tracking. Everything runs through Claude Code's native hook system. Fully async. All hooks fire asynchronously — zero impact on Claude's response latency. Idempotent installer. Re-running just reuses existing config. No duplicates.

What it tracks

- 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 --resume` reuses the same issue

- Auto-closes idle sessions (30 min default)

- Pause/resume for sensitive work

Similar Projects

Productivity●●Solid

Tabric – save tab sessions with notes and restore in one click

Snapshots with names, notes, quick-save and a one-click restore are exactly the workflow shortcuts tab-hoarders want. Local-only storage, JSON backup/restore, and draft recovery are thoughtful practical touches, but the space is crowded (Session Buddy, OneTab, Tab Restore) and Tabric doesn't introduce a striking new angle to elevate it above competent alternatives.

Solve My ProblemCozy
atulyaaj
113mo ago
AI/ML●●Solid

Resume Claude Code without replaying your whole session

Saves 100k+ tokens by handoff instead of replaying entire Claude sessions.

Solve My ProblemNiche Gem
sofumel
3518d ago