Cchistory

cchistory

Like the shell history command but for your Claude Code sessions.

Why cchistory?

When Claude Code runs shell commands, they don't appear in your shell history. This makes it hard to:
- Re-run useful commands from past sessions
- Build on previous work
- Learn from command patterns Claude uses
- Copy command sequences for documentation

📦 Installation

npm (recommended)

npx (try without installing)

From source

Usage

Follow mode

-f / --follow works like tail -f: cchistory prints the existing history and
then stays open, printing new commands as Claude Code writes them. It keeps
following across newly started sessions, and combines with the other flags and
with pipes:

Press Ctrl-C to stop. While following, the live commands are printed in the
order they arrive (matching tail -f file1 file2), rather than re-sorted by
timestamp.

✨ Features

- 🔍 Extract all Bash commands Claude executed across projects
- 🗂️ Filter by specific project or search globally
- 📊 Standard Unix tool compatibility (grep, awk, sort)
- ⚡ Fast streaming parser for large conversation logs
- 🚀 Zero-config - works with existing Claude Code setup

How It Works

Claude Code stores conversation history in ~/.claude/projects/. This tool:

1. Finds your Claude projects
2. Streams through conversation logs
3. Extracts shell commands Claude executed
4. Formats them like traditional shell history

📋 Example Output

Advanced Usage

Command Sources

Extracts commands from:
- Bash tool usage: Commands Claude executes via the Bash tool
- User "!" commands: Commands you run with ! command in Claude

Requirements

- Node.js 20+
- Claude Code with conversation history in ~/.claude/projects/

Note: Claude Code automatically cleans up conversation transcripts based on the cleanupPeriodDays setting…