Free tool

Claude Code transcript viewer

Open a Claude Code session file and read it as a conversation — prompts, replies, tool calls and their output, and optionally Claude's thinking. Search it, then export to Markdown or a single HTML page. Everything runs in your browser.

Drop a Claude Code session file here

Usually ~/.claude/projects/<project>/<session>.jsonl

Read in your browser. Nothing is uploaded.

Find your session file

# newest sessions for the current project (macOS / Linux)
ls -t ~/.claude/projects/$(pwd | sed 's/[^A-Za-z0-9]/-/g')/*.jsonl | head

# all projects, newest first
ls -t ~/.claude/projects/*/*.jsonl | head

Each line of the file is one JSON record: your prompts, Claude's replies (often split across several records), tool calls with their results, and bookkeeping such as titles and permission modes. The viewer stitches those back into a readable conversation.

Questions, answered.

Where does Claude Code store session transcripts?
Every session is a JSONL file under ~/.claude/projects/, in a folder named after the project directory with every character other than a letter or digit turned into a dash, for example ~/.claude/projects/-Users-ada-code-my-app/<session-id>.jsonl. On Windows it is %USERPROFILE%\.claude\projects\. Sort by modified date to find the latest session.
Is my transcript uploaded anywhere?
No. The viewer reads the file in your browser with the FileReader API and never sends it to VibeHub or anyone else. Transcripts can contain file contents, command output, and secrets, so check before sharing an export.
Can I export a Claude Code conversation to Markdown?
Yes. Open the session here and use the Markdown button, or HTML for a single self-contained page. Thinking blocks are left out unless you turn them on, and very long tool output is cut to 20,000 characters per call.
Why do Claude Code sessions disappear?
Claude Code deletes local session files after cleanupPeriodDays (30 days by default). Raise it in ~/.claude/settings.json, or keep sessions with the code they produced: the VibeHub Claude Code plugin attaches each session to the commit it led to.
Does it work with long, compacted, and resumed sessions?
Yes. Compaction summaries, background-task notifications, ! shell commands, and API errors are shown as what they are rather than as prompts. Files of 50 MB and more open fine. Records the viewer does not recognise are skipped, so newer Claude Code versions still open.

Version the whole vibe.

The vb CLI, public vibes, and GitHub mirroring are free forever.