Claude Code History Viewer

The unified history viewer for AI coding assistants.

Browse, search, and analyze conversations from Claude Code, Gemini CLI, Antigravity, Codex CLI, Cline, Cursor, Aider, OpenCode, ForgeCode, CodeBuddy Code, and Grok CLI — as a desktop app or headless server. 100% offline.

Website · Download · Report Bug

Languages: English | 한국어 | 日本語 | 中文 (简体) | 中文 (繁體)

Quick Start

Desktop app — download and run:

Homebrew (macOS):

brew install --cask jhlee0409/tap/claude-code-history-viewer

Headless server — access from any browser:

brew install jhlee0409/tap/cchv-server   # or: curl -fsSL https://raw.githubusercontent.com/jhlee0409/claude-code-history-viewer/main/install-server.sh | sh
cchv-server --serve                       # → http://localhost:3727

See Server Mode for Docker, VPS, and systemd setup.

Choose a mode:

Why This Exists

AI coding assistants generate thousands of conversation messages, but none of them provide a way to look back at your history across tools. CCHV solves this.

Twenty-nine assistants. One viewer. Switch between Claude Code, GitHub Copilot, Gemini CLI, Antigravity, Codex CLI, Cline (incl. Roo Code & Kilo Code), Cursor, Cursor Agent, Aider, OpenCode, ForgeCode, CodeBuddy Code, Grok CLI, Kimi, Kiro, Amazon Q CLI, Continue.dev, PearAI, Goose, Crush, llm, Open Interpreter, Pi, oh-my-pi, Mistral Vibe, Qwen Code, Zed, OpenHands, and Trae sessions seamlessly — compare token usage, search across providers, and analyze your workflow in a single interface.

No vendor lock-in. No cloud dependency. Your local conversation files, beautifully rendered.

Antigravity note: the viewer resolves the Antigravity root as ~/.gemini/antigravity and then reads session state from brain/ plus usage/cache artifacts from .token-monitor/rpc-cache/v1/; this matches the current runtime layout and root resolver in src-tauri/src/commands/antigravity.rs.

Table of Contents

• Features
• Installation
• Build from Source
• Server Mode (WebUI)
• Usage
• Accessibility
• Tech Stack
• Data Privacy
• Troubleshooting
• Contributing
• License

Features

Core

Provider Notes

New in v1.23.0

New in v1.18.0

New in v1.17.0

New in v1.16.0

New in v1.15.0

v1.14.0

v1.13.0

Older releases: see CHANGELOG.md for v1.12.0 and earlier.

More

Installation

Homebrew (macOS)

brew tap jhlee0409/tap
brew install --cask claude-code-history-viewer

Or install directly with the full cask path:

brew install --cask jhlee0409/tap/claude-code-history-viewer

If you see No Cask with this name exists, run the full cask path command above.

To upgrade:

brew upgrade --cask claude-code-history-viewer

To uninstall:

brew uninstall --cask claude-code-history-viewer

Migrating from manual (.dmg) installation? Move the existing app to Trash in Finder before installing via Homebrew to avoid conflicts. Choose one installation method — do not mix manual and Homebrew installs. Then run:

brew tap jhlee0409/tap
brew install --cask claude-code-history-viewer

Build from Source

git clone https://github.com/jhlee0409/claude-code-history-viewer.git
cd claude-code-history-viewer

# Option 1: Using just (recommended)
brew install just    # or: cargo install just
just setup
just dev             # Development
just tauri-build     # Production build

# Option 2: Using pnpm directly
pnpm install
pnpm tauri:dev       # Development
pnpm tauri:build     # Production build

Requirements: Node.js 20.19+ (or 22.12+), pnpm, Rust toolchain

Server Mode (WebUI)

Run the viewer as a headless HTTP server — no desktop environment required. Ideal for VPS, remote servers, or Docker. The server binary embeds the frontend — a single file is all you need.

New to server deployment? See the full Server Mode Guide (한국어) for step-by-step instructions covering local testing, VPS setup, Docker, and more.

Quick Install

# Homebrew (macOS / Linux)
brew install jhlee0409/tap/cchv-server

# Or one-line script
curl -fsSL https://raw.githubusercontent.com/jhlee0409/claude-code-history-viewer/main/install-server.sh | sh

Both methods install cchv-server to your PATH.

Start the Server

cchv-server --serve

Output:

🔑 Auth token: b77f41d4-ec24-4102-8f7a-8a942d6dd4a0
   Open in browser: http://192.168.1.10:3727?token=b77f41d4-ec24-4102-8f7a-8a942d6dd4a0
👁 File watcher active: /home/user/.claude/projects
🚀 WebUI server running at http://0.0.0.0:3727

Open the URL in your browser — the token is saved automatically.

Pre-built Binaries

Download from Releases.

CLI options:

Authentication

All /api/* endpoints are protected by Bearer token authentication. The token is auto-generated on each server start and printed to stderr.

• Browser access: Use the ?token=... URL printed at startup. The token is saved to localStorage automatically.
• API access: Include Authorization: Bearer <token> header.
• Custom token: --token my-secret-token to set your own.
• Environment variable: CCHV_TOKEN=your-token cchv-server --serve (useful for systemd/Docker).
• Disable: --no-auth to skip authentication entirely (only use on trusted networks).

Real-time Updates

The server watches ~/.claude/projects/ for file changes and pushes updates to the browser via Server-Sent Events (SSE). When you use Claude Code in another terminal, the viewer updates automatically — no manual refresh needed.

Docker

docker compose up -d

Check the token after startup:

docker compose logs webui
# 🔑 Auth token: ... ← paste this URL in your browser

The docker-compose.yml mounts ~/.claude, ~/.codex, and ~/.local/share/opencode as read-only volumes.

The sample Docker setup mounts Claude, Codex, and OpenCode only. To browse another provider, add its local data directory as a read-only volume at the path that provider expects inside the container, then restart the container.

systemd Service

For persistent server on Linux, use the provided systemd template:

sudo cp contrib/cchv.service /etc/systemd/system/
sudo systemctl edit --full cchv.service   # Set User= to your username
sudo systemctl enable --now cchv.service

Build from Source (Server Only)

just serve-build           # Build frontend + embed into server binary
just serve-build-run       # Build and run (embedded assets)

# Or run in development (external dist/):
just serve-dev             # Build frontend + run server with --dist

Health Check

GET /health
→ { "status": "ok" }

Usage

1. Launch the app
2. It automatically scans for conversation data from all 29 supported providers (Claude Code, Codex CLI, Gemini CLI, Cursor, Cline, Continue.dev, Goose, Zed, Qwen Code, Amazon Q CLI, and more — see the provider table above)
3. Browse projects in the left sidebar — filter by provider using the tab bar
4. Click a session to view messages
5. Use tabs to switch between Messages, Analytics, Token Stats, Recent Edits, and Session Board

Command-line flags

Launch the app pre-focused on a specific session with one of these selectors:

# Full UUID
claude-code-history-viewer --session 1265cd74-caa9-472e-b343-c4f44b5cf12c

# UUID prefix (8+ hex-or-dash chars, up to 36) — first match wins
claude-code-history-viewer --session 1265cd74

# Equals form also works
claude-code-history-viewer --session=1265cd74

# Exact Claude session-folder name under ~/.claude/projects/
claude-code-history-viewer --session-folder my-project

# Case-insensitive substring match against session titles
claude-code-history-viewer --session-title "auth bug"

--session accepts a full UUID, UUID prefix, or absolute path to a .jsonl file. --session-folder matches an exact Claude session-folder name, while --session-title performs a case-insensitive title substring search and may show a picker when multiple sessions match. If multiple selectors are supplied, precedence is --session > --session-folder > --session-title.

The app also accepts these deep-link forms from a registered desktop environment:

file:///absolute/path/to/session.jsonl
claude-code-history-viewer://session/1265cd74-caa9-472e-b343-c4f44b5cf12c
claude-code-history-viewer://session-folder/my-project
claude-code-history-viewer://session-title/auth%20bug

The viewer scans every known project, navigates to the matching session, and falls back to normal startup if no session matches.

Accessibility

The app includes accessibility features for keyboard-only, low-vision, and screen-reader users.

• Keyboard-first navigation:
  • Skip links for Project Explorer, Main Content, Message Navigator, and Settings
  • Project tree navigation with ArrowUp/ArrowDown/Home/End, type-ahead search, and * to expand sibling groups
  • Message navigator navigation with ArrowUp/ArrowDown/Home/End and Enter to open the focused message
• Visual accessibility:
  • Persistent global font size scaling (90%, 100%, 110%, 120%, 130%)
  • High contrast mode toggle in settings
• Screen reader support:
  • Landmark and tree/list semantics (navigation, tree, treeitem, group, listbox, option)
  • Live announcements for status/loading and project tree navigation/selection changes
  • Inline keyboard-help descriptions via aria-describedby

Tech Stack

Layer	Technology
Backend
Frontend
State
Build
i18n	5 languages

Data Privacy

Desktop mode is local-first. Conversation files are read from local disk; no conversation data is uploaded, and there is no analytics, tracking, or telemetry.

Server mode intentionally serves local files to browsers and clients that can reach the server. Keep it bound to 127.0.0.1 for local-only use, or keep token authentication enabled before exposing it to a network.

Troubleshooting

Contributing

Contributions are welcome! Here's how to get started:

1. Fork the repository
2. Create a feature branch (git checkout -b feat/my-feature)
3. Run checks before committing:

   pnpm exec tsc --build .   # TypeScript
   pnpm vitest run            # Tests
   pnpm lint                  # Lint
   just rust-check-all        # Rust format, clippy, and tests
   pnpm run i18n:validate     # Locale consistency
   

4. Commit your changes (git commit -m 'feat: add my feature')
5. Push to the branch (git push origin feat/my-feature)
6. Open a Pull Request

See Development Commands for the full list of available commands.

License

MIT — free for personal and commercial use.