
Session Tracker
- 10 repo stars
- Updated July 9, 2026
- maleta/claude-sessions
Tracks and summarizes Claude Code sessions with a web UI and per-project SESSION_SUMMARIES.md
About
session-tracker is a Claude Code skill in the AI & Agent Building category. Tracks and summarizes Claude Code sessions with a web UI and per-project SESSION_SUMMARIES.md
- session-tracker
- AI & Agent Building
- AI-coding skill
Session Tracker by the numbers
- Data as of Jul 10, 2026 (Skillselion catalog sync)
/plugin marketplace add maleta/claude-sessions/plugin install session-tracker@session-trackerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 10 |
|---|---|
| Last updated | July 9, 2026 |
| Repository | maleta/claude-sessions ↗ |
What it does
Tracks and summarizes Claude Code sessions with a web UI and per-project SESSION_SUMMARIES.md
README.md
Claude Session Tracker
Automatically tracks and summarizes Claude Code sessions using Claude Haiku. Provides a web UI for browsing session history and generates per-project SESSION_SUMMARIES.md files for context in future conversations.

Features
- Automatic tracking - Hooks fire on every response and session end
- AI summaries - Claude Haiku generates title, summary, topics, and status
- Per-project summaries -
SESSION_SUMMARIES.mdin each project directory for future session context - Web UI - Search, filter, hide/restore sessions grouped by project
- Resume commands - One-click copy of
claude --resume <id>commands - Session history skill - Claude can read past session context via the plugin skill
Requirements
- Bun 1.0+
- Claude Code CLI (uses your subscription via
claude -p --model haiku- no API credits consumed)
Installation
Add the marketplace and install the plugin:
/plugin marketplace add maleta/claude-sessions
/plugin install session-tracker@claude-session-tracker
That's it. The plugin auto-registers its hooks and provisions the web UI on first run.
How it works
Hooks
- Stop - Fires after each Claude response. Analyzes after 1+ user messages, re-analyzes every 5 additional messages.
- SessionEnd - Fires when a session ends. Consolidates all incremental summaries into a final one.
SESSION_SUMMARIES.md
After each analysis, the hook writes/updates a SESSION_SUMMARIES.md file in the project directory. This file contains:
- Session title and summary from Haiku
- Date, branch, status, message count, topics
- Session ID and resume command
Future Claude sessions can read this file for context on past work (via the plugin's skill).
Web UI
Static HTML file - no server needed, opens directly in the browser:
open ~/.claude/session-tracker/index.html
The web UI is auto-provisioned by the hook on first run. Features: search, project grouping, status badges, hide/restore, copy resume commands.
Configuration
Disable SESSION_SUMMARIES.md for a specific project by adding to <project>/.claude/settings.local.json:
{
"sessionTracker": {
"summaryFile": false
}
}
Data flow
Hook fires (Stop/SessionEnd)
|
v (count messages from transcript)
|
v (check threshold: 1+ messages first time, then every 5 more)
|
v (call Haiku via claude -p for summary)
|
v
~/.claude/session-tracker/sessions-data.js <-- single source of truth
|
v (also written per project)
|
v
<project>/SESSION_SUMMARIES.md <-- per-project context
Uninstall
Disable the plugin in Claude Code settings or remove it from enabledPlugins in ~/.claude/settings.json.
To also remove session data:
rm -rf ~/.claude/session-tracker/
License
MIT