Grep every Claude Code session you've ever run. The lossless Rust parser reads Claude Code's on-disk JSONL at 169 MB/s; the compiled CLI greps it and renders one line per event, 25 ms cold.
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 and ask Claude directly; 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.
Script it from Python
The CLI's funnel is four commands; your own tooling wants the events themselves. parse turns a path into a Transcript of typed lazy views, with the noise already dropped inside the engine:
from cc_transcript import NOISE_SPEC, discover, parse
transcript = parse(discover()[0], drop=NOISE_SPEC)
print(len(transcript.events), "events after the noise drop")
discover() lists every transcript on disk newest first, stream fans a whole corpus across the parse pool, and resolve finds one session by UUID. parse also reads OpenAI Codex CLI rollouts — hand it a path from ~/.codex/sessions and the same typed events come back. The getting-started guide builds this out to a composed filter and a sentiment score.
JSON output schema
show --json and grep --json emit JSONL, with one object per event. Each event
uses the envelope {i, kind, meta, model, text, blocks, stop_reason, usage};
fields that do not apply to its kind are omitted. Every object in blocks has
a type discriminator such as text, thinking, tool_use, tool_result,
or fallback.
More in the docs
- The Python library turns a transcript into typed lazy views, a composed filter, and a score in a dozen lines.
- Filtering events covers composable clauses, specs, and the ready-made
NOISE_SPEC. - Sentiment scoring buckets conversations and scores them around any inference engine.
- Feedback mining runs detectors, confidence calibration, and LLM verdict passes over your corpus.
- The Rust engine is the implementation — parsing, filtering, scoring, and mining — its correctness pinned by hand-owned literals and golden fixtures.
- Codex rollouts make the parser two-provider: OpenAI Codex CLI sessions lower into the same typed events, with rollout discovery, subagent joins, and per-session lifecycle and token totals.
list --provider codexfinds them from the shell. - API reference documents the complete typed surface, from
TranscriptEventtoSessionActivity.
Read the docs for the full guide. Licensed under PolyForm Noncommercial 1.0.0.
1 maintainer
Metadata
1 maintainer
Release files for cc-transcript 14.29.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cc_transcript-14.29.1.tar.gz | 12.4 MB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| cc_transcript-14.29.1-cp313-abi3-manylinux_2_28_x86_64.whl | CPython 3.13 | abi3 | Linux glibc 2.28+ x86-64 | Details |
| cc_transcript-14.29.1-cp313-abi3-manylinux_2_28_aarch64.whl | CPython 3.13 | abi3 | Linux glibc 2.28+ ARM64 | Details |
| cc_transcript-14.29.1-cp313-abi3-macosx_11_0_x86_64.whl | CPython 3.13 | abi3 | macOS 11.0+ x86-64 | Details |
| cc_transcript-14.29.1-cp313-abi3-macosx_11_0_arm64.whl | CPython 3.13 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 134.2 MB
Release files / cc_transcript-14.29.1.tar.gz
| Download URL | cc_transcript-14.29.1.tar.gz |
|---|---|
| Size | 12.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af160ade017dca4e59e73fd3053892d930b82ac9eeee146090d442060dbf0689
|
|
BLAKE2b-256 checksum How to use checksums |
4ab04e75b316e0439e4239a74e565ca15a494d26a9c94df0f32c24b369c5c18f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / cc_transcript-14.29.1-cp313-abi3-manylinux_2_28_x86_64.whl
| Download URL | cc_transcript-14.29.1-cp313-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 30.8 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
13602e0b2e23f066686dd11885b325ddb0062e932da6c3303bf15575907dd25b
|
|
BLAKE2b-256 checksum How to use checksums |
807719482ad7707170ed722f48db411b6ac06a463be6667374a67afc69873d7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / cc_transcript-14.29.1-cp313-abi3-manylinux_2_28_aarch64.whl
| Download URL | cc_transcript-14.29.1-cp313-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 30.3 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
5036b0025fc7f0478ee1d8262c8bb9d8e0a623c7eae155b59ead4e3609b735a7
|
|
BLAKE2b-256 checksum How to use checksums |
f38ad3608924bb145b480b0884fccf828dd3997695ea9891fc23993b588b6528
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / cc_transcript-14.29.1-cp313-abi3-macosx_11_0_x86_64.whl
| Download URL | cc_transcript-14.29.1-cp313-abi3-macosx_11_0_x86_64.whl |
|---|---|
| Size | 30.6 MB |
| Tags | CPython 3.13 abi3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
8e70e6de38bc37355262392f19a93dcb31945508c362a8b0137d701407631568
|
|
BLAKE2b-256 checksum How to use checksums |
bbd5905cb38eeff0b636106681cff8be5e1e5dc5238e7fd7386ccab995c7609c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / cc_transcript-14.29.1-cp313-abi3-macosx_11_0_arm64.whl
| Download URL | cc_transcript-14.29.1-cp313-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 30.1 MB |
| Tags | CPython 3.13 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b10499dfe3566a9d38372ca607669e83a88a9b570db0222380545612ba60976c
|
|
BLAKE2b-256 checksum How to use checksums |
bfc103c2a5cb4cc1595d2200d5b0e82814c591a1b7751ff1456412d2f3e4188e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log
