Claude code sessions skill

Search, analyze, and manage Claude Code session history.

by davila7·MIT license·★ 32,299 Stars on the repo·GitHub ↗

Use now

Files of Claude code sessions

davila7/main1 file shown
SKILL.md
Show the full text80 lines
claude-code-sessions/SKILL.md80 lines · 3.1 KB

Claude Code Sessions

Session intelligence plugin for Claude Code. Reads the JSONL session files that Claude Code writes to ~/.claude/projects/ and makes them searchable and analyzable.

What It Does

Claude Code records every session as a JSONL file — messages, tool calls, token counts, diffs, tasks. This plugin reads those files and provides two interfaces. Most operations are read-only; delete and cleanup skills can remove session files when explicitly invoked.

11 skills usable directly in Claude Code:

Skill Purpose
/session-search "query" Full-text search across every session
/session-stats Token usage, model distribution, tool breakdown
/session-list List sessions sorted by recency, size, or duration
/session-detail Deep dive into a specific session
/session-diff Compare two sessions — files, tools, topics
/session-timeline Chronological view of 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

Web dashboard at localhost:3000 with four views: Dashboard (summary stats), Sessions (sortable table with bulk operations), Search (full-text with context snippets), Tasks (grouped by status with orphan detection).

Install

/plugin marketplace add apappascs/claude-code-sessions
/plugin install claude-code-sessions@claude-code-sessions

No API keys. No config. No runtime dependencies. It reads what's already on disk.

For the dashboard:

bun run ui
# → http://localhost:3000

Architecture

Same TypeScript modules power skills, dashboard, and CLI:

lib/formatters.ts      — pure utilities, no I/O
lib/session-parser.ts  — parses one JSONL file into structured data
lib/session-store.ts   — scans all sessions, aggregates, searches
ui/server.ts           — HTTP endpoints + static file serving

Each lib file doubles as a standalone 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-parser.ts stats path/to/session.jsonl

Use Cases

  • Find the session where you solved a specific problem weeks ago
  • See which projects consume the most tokens
  • Track pending tasks across all sessions and projects
  • Resume a past session with full context
  • Compare how two sessions approached the same problem
  • Export session transcripts for documentation
1---
2name: claude-code-sessions
3description: Search, analyze, and manage Claude Code session history. Use when the user wants to find past sessions, check token usage, review tool breakdowns, resume previous work, or manage tasks across sessions. Provides 11 skills and a web dashboard.
4---
5 
6# Claude Code Sessions
7 
8Session intelligence plugin for Claude Code. Reads the JSONL session files that Claude Code writes to `~/.claude/projects/` and makes them searchable and analyzable.
9 
10## What It Does
11 
12Claude Code records every session as a JSONL file — messages, tool calls, token counts, diffs, tasks. This plugin reads those files and provides two interfaces. Most operations are read-only; delete and cleanup skills can remove session files when explicitly invoked.
13 
14**11 skills** usable directly in Claude Code:
15 
16| Skill | Purpose |
17|-------|---------|
18| `/session-search "query"` | Full-text search across every session |
19| `/session-stats` | Token usage, model distribution, tool breakdown |
20| `/session-list` | List sessions sorted by recency, size, or duration |
21| `/session-detail` | Deep dive into a specific session |
22| `/session-diff` | Compare two sessions — files, tools, topics |
23| `/session-timeline` | Chronological view of sessions on a project |
24| `/session-resume` | Generate a context recovery prompt from any session |
25| `/session-tasks` | Find pending and orphaned tasks across sessions |
26| `/session-export` | Export a session as clean markdown |
27| `/session-cleanup` | Find empty, tiny, or stale sessions |
28| `/session-delete` | Delete sessions and their associated tasks |
29 
30**Web dashboard** at `localhost:3000` with four views: Dashboard (summary stats), Sessions (sortable table with bulk operations), Search (full-text with context snippets), Tasks (grouped by status with orphan detection).
31 
32## Install
33 
34```bash
35/plugin marketplace add apappascs/claude-code-sessions
36/plugin install claude-code-sessions@claude-code-sessions
37```
38 
39No API keys. No config. No runtime dependencies. It reads what's already on disk.
40 
41For the dashboard:
42 
43```bash
44bun run ui
45# → http://localhost:3000
46```
47 
48## Architecture
49 
50Same TypeScript modules power skills, dashboard, and CLI:
51 
52```
53lib/formatters.ts — pure utilities, no I/O
54lib/session-parser.ts — parses one JSONL file into structured data
55lib/session-store.ts — scans all sessions, aggregates, searches
56ui/server.ts — HTTP endpoints + static file serving
57```
58 
59Each lib file doubles as a standalone CLI:
60 
61```bash
62bun run lib/session-store.ts list --sort recency --limit 10
63bun run lib/session-store.ts search "database migration" --since 2025-01-01
64bun run lib/session-parser.ts stats path/to/session.jsonl
65```
66 
67## Use Cases
68 
69- Find the session where you solved a specific problem weeks ago
70- See which projects consume the most tokens
71- Track pending tasks across all sessions and projects
72- Resume a past session with full context
73- Compare how two sessions approached the same problem
74- Export session transcripts for documentation
75 
76## Links
77 
78- **GitHub**: [github.com/apappascs/claude-code-sessions](https://github.com/apappascs/claude-code-sessions)
79- **License**: MIT
80 

Discussion