Claude Transcripts docs GitHub
Work in progressUnder active development — not tested as ready for use. Breaking changes land without notice, stored data may need to be discarded between revisions, and there is no auth or security model.

Backfill

backfill adopts the transcripts Claude Code already keeps on disk (~/.claude/projects/**/<id>.jsonl) as first-class history: sessions from before you installed, or from while the stack was down.

claude-transcripts backfill --dry-run                   # preview: adopt / skip / repair per session
claude-transcripts backfill                             # adopt everything not already stored
claude-transcripts backfill --force --session <id>      # rebuild one adopted session
claude-transcripts backfill --repair                    # finish sessions an interrupted write left short

All flags: cli.md.

What it writes

For each session, the same shape a live recording has, delivered through the webapi's /api/ingest/* routes (so it is indexed for search immediately):

Timestamps are the transcript's own, never the time of the backfill. --host and --actor set attribution. Token usage is computed with the same sumTranscriptTokens the hook uses, so counts match a live recording.

Not captured yet: subagent sub-transcripts. The run reports how many sessions have them.

Re-running

Not built