Recover prior work from Claude Code session transcripts. Use when the user asks to find something from a previous session, resume earlier research, or recall what was decided.
Installs into .claude/skills of the current project.
Are you the author of Session Search?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/yichen-zju-session-search)
---
name: session-search
description: Recover prior work from Claude Code session transcripts. Use when the user asks to find something from a previous session, resume earlier research, or recall what was decided.
---
# Session Search
Search prior Claude Code session transcripts directly via Bash.
## Where transcripts live
Session transcripts are JSONL files under `~/.claude/projects/<project-slug>/`, where `<project-slug>` is the working directory path with `/` replaced by `-` (e.g. `~/.claude/projects/-home-user/`). Each line is a JSON record with `type` (user, assistant, etc.) and message content.
## Search
```bash
# Find sessions mentioning a topic
grep -ril "scaling laws" ~/.claude/projects/-home-user*/
# Search current project only
grep -ril "replication" ~/.claude/projects/-home-user/
# Show matching user messages with context
grep -h '"type":"user"' ~/.claude/projects/-home-user/*.jsonl | grep -i "literature review"
```
For large result sets, triage by file modification time (`ls -lt`) to find recent sessions first.
## Also check durable artifacts
Before digging through transcripts, check the durable research artifacts — they were designed to survive sessions:
- `CHANGELOG.md` (lab notebook)
- `notes/` (session logs)
- `outputs/.plans/` (run plans with task ledgers and verification logs)
- `outputs/`, `papers/` (final artifacts with provenance sidecars)
- The memory directory (`~/.claude/projects/-home-user/memory/`)
