claude-code-sessions
/claude-code-sessions
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.
- Author
- davila7 ↗
- Repository
- claude-code-templates ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- What It Does
- Install
- Architecture
- Use Cases
- Links
SKILL.md preview
--- name: claude-code-sessions description: 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. --- # 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 ```bash /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: ```bash 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: ```bash 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 ## Links - **GitHub**: [github.com/apappascs/claude-code-sessions](https://github.com/apappascs/claude-code-sessions) - **License**: MIT
Versions
The database has no other skills named claude-code-sessions.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version a8ab9a5cc7bd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100context-report
Analyze Claude Code context efficiency. Use when evaluating session token usage. - 84prism-analyze
Analyze Claude Code session health using PRISM. Use when asked to check token usage, audit CLAUDE.md, understand why sessions are failing, or list projects. - 100sessions
Search and ask questions about coding agent session history across Claude Code, Codex, and Cursor. Use when asking what was worked on, what was tried before, how a problem was investigated across sessions, what happened recently, or any question about past agent sessions. Also… - 100cq
Query past Claude Code sessions using the cq CLI (SQL over session transcripts via DuckDB). You MUST use this skill whenever the user asks about their Claude session history, tool usage, errors, or past commands. This includes questions like "what tools have I used", "how many… - 100mine-history
Extract and synthesize learnings from past Claude Code session transcripts into project documentation. Use when asked to "mine history", "extract learnings from past sessions", "what patterns keep recurring", or "improve docs from history". - 100dig
Mine Claude Code sessions — timeline, gaps, repo attribution, session history. Use when user says "dig", "sessions", "past sessions", "timeline", "what did I work on", or wants to see session history. Do NOT trigger for finding code/projects (use /trace), exploring repos (use…