session-tracker

name	session-tracker
description	Use when the user asks about past sessions, session history, what was worked on previously, previous conversations, or wants context from prior Claude Code sessions in this project. Also use when the user wants to resume a past session or review what happened in earlier chats.

Session Tracker

Overview

Projects tracked by Claude Session Tracker contain a SESSION_SUMMARIES.md file with summaries of past Claude Code sessions. This file is auto-generated by the session-tracker hook after every 4+ user messages.

When to Use

When the user asks about previous work, past sessions, or wants context on what has been done:

1. Read SESSION_SUMMARIES.md from the project root (current working directory)
2. Parse the session entries (delimited by HTML comment markers)
3. Present relevant sessions based on the user's query
4. Each entry contains: title, date, branch, status, topics, session ID, and summary

If SESSION_SUMMARIES.md does not exist, inform the user that no session history is available for this project yet. Note: this file can be disabled per project via sessionTracker.summaryFile: false in .claude/settings.local.json.

Session Entry Format

Each session is wrapped in HTML comments:

<!-- session:UUID -->
### Title

- **Date**: YYYY-MM-DD HH:MM
- **Branch**: `branch-name`
- **Status**: completed | in-progress | exploring | debugging
- **Messages**: N
- **Topics**: topic1, topic2, topic3
- **Session ID**: `full-uuid`
- **Resume**: `claude --resume full-uuid`

Summary text here.
<!-- /session:UUID -->

Resume Sessions

Users can resume any past session with:

claude --resume <session-id>

Provide the full resume command when suggesting a session to continue.

Web UI

A full browsable session history is available at:

open ~/.claude/session-tracker/index.html