maleta 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:
- Read
SESSION_SUMMARIES.mdfrom the project root (current working directory) - Parse the session entries (delimited by HTML comment markers)
- Present relevant sessions based on the user's query
- 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