By apappascs
Session intelligence for Claude Code: search, analyze, diff, and resume past sessions with a web dashboard
Finds old, empty, or tiny Claude Code session files that are candidates for deletion. Use when the user wants to clean up sessions, free disk space, says "clean up old sessions", or asks about session storage usage.
Delete a Claude Code session file, with optional cleanup of associated task lists and tasks. Warns about orphaned tasks before deleting. Use when the user says "delete session", "remove session", or wants to clean up a specific session.
Show detailed information about a Claude Code session including stats, token usage, models used, tools called, associated tasks, and conversation messages. Use when the user says "show session", "session details", "what happened in session X".
Compares two Claude Code sessions — shows what changed in files, tools used, branches, and topics. Use when the user says "what changed between sessions", "diff sessions", "compare yesterday and today", or wants to understand how work evolved across sessions.
Exports a Claude Code session as a clean, readable markdown transcript. Use when the user wants to export a session, create a transcript, save session history to a file, or says "export this session".
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Session intelligence for Claude Code
Search, analyze, and manage every session across all your projects.
Claude Code writes a JSONL file for every session you run. These files live in ~/.claude/projects/ and contain everything — messages, tool calls, token counts, diffs, tasks. But there's no built-in way to search or analyze them.
This plugin reads those files and gives you 11 skills and a web dashboard to make sense of your session history.
Register the marketplace, then install:
/plugin marketplace add apappascs/claude-code-sessions
/plugin install claude-code-sessions@claude-code-sessions
That's it. No API keys, no config, no runtime dependencies. Most operations are read-only; the delete and cleanup skills can remove session files when explicitly invoked.
Use these directly in Claude Code:
| Command | Description |
|---|---|
/session-list | List all sessions, sorted by recency, size, or duration |
/session-search "query" | Full-text search across every session |
/session-stats | Token usage, model distribution, tool breakdown |
/session-detail | Deep dive into a specific session |
/session-diff | Compare two sessions — files, tools, topics |
/session-timeline | Chronological view of all sessions on a project |
/session-resume | Generate a context recovery prompt from any session |
/session-tasks | Find pending and orphaned tasks across sessions |
/session-export | Export a session as clean markdown |
/session-cleanup | Find empty, tiny, or stale sessions |
/session-delete | Delete sessions and their associated tasks |
A local web UI for browsing sessions visually:
bun run ui
# → http://localhost:3000
4 views:
Session detail — click any session to see its full transcript, tool usage breakdown, token consumption bar, and task lists. Filter tool calls in/out. Paginated message loading.
Keyboard shortcut: Cmd+K jumps to search from anywhere.
Three TypeScript modules, one HTTP server, zero runtime dependencies:
lib/
├── formatters.ts # JSON serialization, truncation, timestamp parsing
├── session-parser.ts # Single-session JSONL parser (stats, messages, tools, diffs)
└── session-store.ts # Cross-session operations (list, search, filter, aggregate)
ui/
├── server.ts # Bun HTTP server — 10 REST endpoints + static files
└── public/ # Alpine.js SPA, OKLCH design tokens, light/dark theme
skills/ # Skill definitions
tests/ # Bun test runner, fixture-based
Data flow: Claude Code writes JSONL → this plugin reads it. Nothing is modified. Tasks come from ~/.claude/tasks/ with JSONL fallback for older sessions.
Each lib file doubles as a CLI:
bun run lib/session-store.ts list --sort recency --limit 10
bun run lib/session-store.ts search "database migration" --since 2025-01-01
bun run lib/session-store.ts tasks --status pending
bun run lib/session-parser.ts stats path/to/session.jsonl
bun run lib/session-parser.ts export path/to/session.jsonl --format md
Prerequisites: Bun v1.3+
# Install
bun install
# Run tests
bun test
# Typecheck
bun run typecheck
# Lint (Biome)
bun run lint
# Start the UI
bun run ui
npx claudepluginhub apappascs/claude-code-sessions --plugin claude-code-sessionsSearch across Claude Code and OpenClaw session history. Find past conversations, decisions, and code snippets instantly.
Persistent local memory for Claude Code. Every tool call, every file edit, every thinking block from every session — stored verbatim on your machine. Semantic recall in ~126ms with zero API calls.
qrec session recall engine
Session transcript timeline viewer for Claude Code and Codex agent sessions
Live TUI dashboard for monitoring all active Claude Code sessions, status, context usage, tokens, and latest messages at a glance.
Mission Control for Claude Code — auto-starts a web dashboard, provides 90 MCP tools (sessions, stats, live monitoring, projects, teams, insights, coaching, and more), and adds 9 skills including /session-recap, /daily-cost, /standup, /coaching, /insights, and /team-status.