A Python CLI tool that converts Claude Code transcript JSONL files into readable HTML and Markdown formats.

Browser log demo:

TUI demo:

📋 View Changelog - See what's new in each release

This tool generates clean, minimalist HTML pages showing user prompts and assistant responses chronologically. It's designed to create a readable log of your Claude Code interactions with support for both individual files and entire project hierarchies.

📄 View Example HTML Output - Download a real example generated from this project's development (large file, ~100 MB)

TL;DR: run the command below and browse the pages generated from your entire Claude Code archives:

uvx claude-code-log@latest --open-browser

• Interactive TUI (Terminal User Interface): Browse and manage Claude Code sessions with real-time navigation, summaries, and quick actions for HTML export and session resuming
• Project Hierarchy Processing: Process entire ~/.claude/projects/ directory with linked index page
• Individual Session Files: Generate separate HTML files for each session with navigation links
• Single File or Directory Processing: Convert individual JSONL files or specific directories
• Session Navigation: Interactive table of contents with session summaries and quick navigation
• Token Usage Tracking: Display token consumption for individual messages and session totals
• Runtime Message Filtering: JavaScript-powered filtering to show/hide message types (user, assistant, system, tool use, etc.)
• Chronological Ordering: All messages sorted by timestamp across sessions
• Interactive timeline: Generate an interactive, zoomable timeline grouped by message times to navigate conversations visually
• Cross-Session Summary Matching: Properly match async-generated summaries to their original sessions
• Date Range Filtering: Filter messages by date range using natural language (e.g., "today", "yesterday", "last week")
• Rich Message Types: Support for user/assistant messages, tool use/results, thinking content, images
• System Command Visibility: Show system commands (like init) in expandable details with structured parsing
• Markdown Rendering: Server-side markdown rendering with syntax highlighting using mistune
• Floating Navigation: Always-available back-to-top button and filter controls
• CLI Interface: Simple command-line tool using Click

This tool helps you answer questions like:

• "How can I review all my Claude Code conversations?"
• "What did I work on with Claude yesterday/last week?"
• "How much are my Claude Code sessions costing?"
• "How can I search through my entire Claude Code history?"
• "What tools did Claude use in this project?"
• "How can I share my Claude Code conversation with others?"
• "What's the timeline of my project development?"
• "How can I analyse patterns in my Claude Code usage?"

The TUI provides an interactive interface for browsing and managing Claude Code sessions with real-time navigation, session summaries, and quick actions.

# Launch TUI for all projects (default behavior)
claude-code-log --tui

# Launch TUI for specific project directory
claude-code-log /path/to/project --tui

# Launch TUI for specific Claude project
claude-code-log my-project --tui  # Automatically converts to ~/.claude/projects/-path-to-my-project

TUI Features:

• Session Listing: Interactive table showing session IDs, summaries, timestamps, message counts, and token usage
• Smart Summaries: Prioritizes Claude-generated summaries over first user messages for better session identification
• Working Directory Matching: Automatically finds and opens projects matching your current working directory
• Quick Actions:
  • h: Generate and open session HTML in browser
  • m: Generate and open session Markdown in browser
  • v: View session Markdown in embedded viewer (with table of contents)
  • c: Resume session in Claude Code with claude -r <sessionId>
  • r: Reload session data from files
  • p: Switch to project selector view
  • H/M/V: Force regenerate HTML/Markdown (hidden shortcuts for development)
• Project Statistics: Real-time display of total sessions, messages, tokens, and date range
• Cache Integration: Leverages existing cache system for fast loading with automatic cache validation
• Keyboard Navigation: Arrow keys to navigate, Enter to expand row details, q to quit
• Row Expansion: Press Enter to expand selected row showing full summary, first user message, working directory, and detailed token usage

# Process all projects in ~/.claude/projects/ (default behavior)
claude-code-log

# Explicitly process all projects
claude-code-log --all-projects

# Process all projects and open in browser
claude-code-log --open-browser

# Process all projects with date filtering
claude-code-log --from-date "yesterday" --to-date "today"
claude-code-log --from-date "last week"

# Skip individual session files (only create combined transcripts)
claude-code-log --no-individual-sessions

This creates:

• ~/.claude/projects/index.html - Top level index with project cards and statistics
• ~/.claude/projects/project-name/combined_transcripts.html - Individual project pages (these can be several megabytes)
• ~/.claude/projects/project-name/session-{session-id}.html - Individual session pages
• ~/.claude/projects/project-name/session-{session-id}.md - Markdown versions (generated on-demand via TUI)

# Single file
claude-code-log transcript.jsonl

# Specific directory
claude-code-log /path/to/transcript/directory

# Custom output location
claude-code-log /path/to/directory -o combined_transcripts.html

# Open in browser after conversion
claude-code-log /path/to/directory --open-browser

# Filter by date range (supports natural language)
claude-code-log /path/to/directory --from-date "yesterday" --to-date "today"
claude-code-log /path/to/directory --from-date "3 days ago" --to-date "yesterday"

When processing all projects, the tool generates:

~/.claude/projects/
├── index.html                           # Master index with project cards
├── project1/
│   ├── combined_transcripts.html        # Combined project page
│   ├── session-{session-id}.html        # Individual session pages
│   ├── session-{session-id}.md          # Markdown version (on-demand via TUI)
│   └── session-{session-id2}.html       # More session pages...
├── project2/
│   ├── combined_transcripts.html
│   └── session-{session-id}.html
└── ...

• Project Cards: Each project shown as a clickable card with statistics
• Session Navigation: Expandable session list with summaries and quick access to individual session files
• Summary Statistics: Total projects, transcript files, and message counts with token usage
• Recent Activity: Projects sorted by last modification date
• Quick Navigation: One-click access to combined transcripts or individual sessions
• Clean URLs: Readable project names converted from directory names

• User Messages: Regular user inputs and prompts
• Assistant Messages: Claude's responses with token usage display
• Summary Messages: Session summaries with cross-session matching
• System Commands: Commands like init shown in expandable details with structured parsing
• Tool Use: Tool invocations with collapsible details and special TodoWrite rendering
• Tool Results: Tool execution results with error handling
• Thinking Content: Claude's internal reasoning processes
• Images: Pasted images and screenshots

• Responsive Design: Works on desktop and mobile
• Runtime Message Filtering: JavaScript controls to show/hide message types with live counts
• Session Navigation: Interactive table of contents with session summaries and timestamp ranges
• Token Usage Display: Individual message and session-level token consumption tracking
• Syntax Highlighting: Code blocks properly formatted with markdown rendering
• Markdown Support: Server-side rendering with mistune including:
  • Headers, lists, emphasis, strikethrough
  • Code blocks and inline code
  • Links, images, and tables
  • GitHub Flavored Markdown features
• Collapsible Content: Tool use, system commands, and long content in expandable sections
• Floating Controls: Always-available filter button, details toggle, and back-to-top navigation
• Cross-Session Features: Summaries properly matched across async sessions

Markdown export provides a lightweight, portable alternative to HTML:

• GitHub-Flavored Markdown: Compatible with GitHub, GitLab, and other Markdown renderers
• Hierarchical Structure: Sessions organized with headers and collapsible details
• Message Excerpts: Section titles include message previews for quick navigation
• Code Preservation: Syntax highlighting hints via fenced code blocks
• Embedded Viewer: TUI includes built-in Markdown viewer with table of contents
• Image Support: Configurable image handling (placeholder, embedded base64, or referenced files)

Install using pip:

pip install claude-code-log

Or run directly with uvx (no separate installation step required):

uvx claude-code-log@latest

Or install from source:

git clone https://github.com/daaain/claude-code-log.git
cd claude-code-log
uv sync
uv run claude-code-log

See CONTRIBUTING.md for development setup, testing, and architecture documentation.

• tutorial overlay
• integrate claude-trace request logs if present?
• convert images to WebP as screenshots are often huge PNGs – this might be time consuming to keep redoing (so would also need some caching) and need heavy dependencies with compilation (unless there are fast pure Python conversation libraries? Or WASM?)
• add special formatting for built-in tools: Glob, Grep, LS, MultiEdit, NotebookRead, NotebookEdit, WebFetch, TodoRead, WebSearch
• add ccusage like daily summary and maybe some textual summary too based on Claude generate session summaries? – import logs from @claude Github Actions
• stream logs from @claude Github Actions, see octotail
• wrap up CLI as Github Action to run after Cladue Github Action and process output
• feed the filtered user messages to headless claude CLI to distill the user intent from the session
• filter message type on Python (CLI) side too, not just UI
• add minimalist theme and make it light + dark; animate gradient background in fancy theme
• do we need special handling for hooks?
• make processing parallel, currently we only use 1 CPU (core) and it's slow
• merge git worktree directories