cc-transcript 9.0.0

Grep every Claude Code session you've ever run.

Grep every Claude Code session you've ever run. cc-transcript's lossless parser reads Claude Code's on-disk JSONL; the CLI lists transcripts, greps their content, and renders one compact line per event.

Get started

uvx cc-transcript list

Every session is already on disk under ~/.claude/projects — list finds them newest first, and stats collapses one into a screenful:

Driving with an agent? Paste this:

/plugin marketplace add yasyf/cc-transcript
/plugin install cc-transcript@cc-transcript

The plugin's skill teaches Claude to answer "what did I ask you yesterday?" from its own history, funneling through the CLI instead of reading raw JSONL.

No Claude Code? Point any agent at the CLI

Use `uvx cc-transcript` to investigate my Claude Code sessions: `list` finds
transcripts on disk, `stats` summarizes one, `grep` searches content, and `show`
renders one compact line per event. Start by listing my newest sessions and
summarizing the most recent one. Docs: https://yasyf.github.io/cc-transcript/

---

Use cases

Ask Claude what you asked Claude yesterday

Yesterday's session is a megabyte of JSONL, and pasting it into a chat blows the context window. Render the spine instead:

uvx cc-transcript show --signal --tail 20 ~/.claude/projects/<project>/<session>.jsonl

--signal keeps only the substantive user and assistant turns — one line per event, a few hundred tokens for the whole exchange. With the plugin installed, skip the command: ask Claude directly and its skill runs this funnel for you.

Find the session where you fixed that bug

The fix happened weeks ago, in one of a few hundred transcripts. Search them all:

uvx cc-transcript grep "TranscriptExpiredError" --project cc-transcript

Hits print under their transcript's path, each line carrying its raw event index — feed an index back into show --range to re-read the conversation around the fix. grep searches your newest 50 transcripts by default; --all takes it to every session on disk, and a no-match run exits 1 so it scripts cleanly.

Debug a token blowup from transcript evidence

A session burned through the context window and you want the culprit, not a guess. Rank the evidence:

uvx cc-transcript stats --per-file --project myapp

Each block reports text, thinking, and tool-io bytes plus per-tool call counts — the blowup stands out as an outsized tool io line. Then grep --tool <name> --with-result pins it to the exact calls.

More in the docs

• The Python library — raw JSONL bytes to typed events, a composed filter, and a score in a dozen lines — getting started
• Filtering events — composable clauses, specs, and the ready-made NOISE_SPEC — builder catalog
• Sentiment scoring — bucket conversations and score them around any inference engine — score specs
• Feedback mining — detectors, confidence calibration, and LLM verdict passes over your corpus — mine your sessions
• Two backends, one protocol — a Rust fast path and a Python reference, parity-asserted against each other — how parity works
• API reference — the complete typed surface, from TranscriptEvent to SessionActivity — reference

Read the docs for the full guide. Licensed under PolyForm Noncommercial 1.0.0.