Install cc-analyzer

cc-analyzer ships as a single self-contained binary for macOS, Linux, and Windows — no Bun, Node, or other runtime required. Ordinary analysis is read-only over Claude's source transcripts and configuration. Its own state lives under $CC_ANALYZER_STATE_DIR, then $XDG_CONFIG_HOME/cc-analyzer, then ~/.config/cc-analyzer/.

One-line install

The installer detects your OS and architecture, downloads the matching binary from the latest release, checks its checksum when the release publishes a manifest, and installs it.

macOS / Linux

curl -fsSL https://cc-analyzer.brnby.com/install.sh | sh

Windows

irm https://cc-analyzer.brnby.com/install.ps1 | iex

By default it installs to ~/.local/bin (macOS/Linux) or %LOCALAPPDATA%\cc-analyzer\bin (Windows). If that directory isn't on your PATH, the installer prints the line to add to your shell profile.

Prefer to read before piping to a shell? Inspect the scripts first: install.sh · install.ps1.

Options

Both installers read two environment variables:

Variable	What it does	Default
CC_ANALYZER_INSTALL_DIR	Install directory	~/.local/bin · %LOCALAPPDATA%\cc-analyzer\bin
CC_ANALYZER_VERSION	Release tag to install, e.g. v0.4.1	latest

macOS / Linux

CC_ANALYZER_VERSION=v0.4.1 CC_ANALYZER_INSTALL_DIR="$HOME/bin" \
  sh -c "$(curl -fsSL https://cc-analyzer.brnby.com/install.sh)"

Windows

$env:CC_ANALYZER_VERSION = 'v0.4.1'
irm https://cc-analyzer.brnby.com/install.ps1 | iex

Download a prebuilt binary (manual)

Every release attaches a binary for each platform:

Platform	Asset
macOS (Apple silicon)	cc-analyzer-darwin-arm64
macOS (Intel)	cc-analyzer-darwin-x64
Linux (x64)	cc-analyzer-linux-x64
Linux (arm64)	cc-analyzer-linux-arm64
Windows (x64)	cc-analyzer-windows-x64.exe

macOS / Linux

curl -fL -o cc-analyzer \
  https://github.com/yorch/cc-analyzer/releases/latest/download/cc-analyzer-darwin-arm64
chmod +x cc-analyzer
sudo mv cc-analyzer /usr/local/bin/   # or anywhere on your PATH
cc-analyzer --help

Windows

curl.exe -fL -o cc-analyzer.exe `
  https://github.com/yorch/cc-analyzer/releases/latest/download/cc-analyzer-windows-x64.exe
.\cc-analyzer.exe --help

On macOS the binary is unsigned, so Gatekeeper quarantines the download. Clear the quarantine flag once:

xattr -d com.apple.quarantine /usr/local/bin/cc-analyzer

Verify the checksum

The one-line installer checks automatically when SHA256SUMS is available. For a manual download, compare the binary's hash against the release SHA256SUMS:

shasum -a 256 cc-analyzer   # or: sha256sum cc-analyzer
# then compare the printed hash to the matching line in:
curl -fsSL https://github.com/yorch/cc-analyzer/releases/latest/download/SHA256SUMS

Update

Installed as a binary, update in place:

cc-analyzer update

It downloads the latest release (streaming with a progress bar), verifies the checksum, and atomically replaces the running binary. Check without installing via cc-analyzer update --check. On Windows, re-run the installer one-liner.

cc-analyzer also prints a passive, once-a-day notice when a newer version is available; silence it with CC_ANALYZER_NO_UPDATE_CHECK=1.

First run and index freshness

Launch the terminal UI directly:

cc-analyzer

Or start the local web app and open it in your default browser:

cc-analyzer serve --open

Both commands build the local session index automatically when it is empty. After that, indexing remains explicit so a large changed session cannot make startup unexpectedly slow. The TUI, stats, and web app show when the index was last refreshed and warn when session files were added, changed, or deleted.

cc-analyzer index --check       # inspect freshness without changing the cache
cc-analyzer index               # incremental refresh
cc-analyzer serve --refresh     # refresh, then serve

index --check exits non-zero when the cache is stale, making it suitable for scripts. serve --open is opt-in and only opens a browser for loopback hosts.

Claude data directories

Claude Code stores its sessions in ~/.claude unless you have moved it. Find your case below — most people are the first one and have nothing to do.

I use the default ~/.claude

Nothing to configure. This is the default and always has been:

cc-analyzer index
cc-analyzer stats

I moved Claude Code's data directory

If you set CLAUDE_CONFIG_DIR for Claude Code, cc-analyzer reads the same variable — no cc-analyzer configuration at all:

export CLAUDE_CONFIG_DIR=~/dotfiles/claude   # you already have this
cc-analyzer index
cc-analyzer projects

To confirm what it picked up:

$ cc-analyzer claude-dir
Reading Claude Code data from:
  /Users/me/dotfiles/claude  (CLAUDE_CONFIG_DIR)

I have several Claude profiles

Work and personal, or several machines' data synced into one folder. Name each directory once; they are then analyzed together as a single portfolio:

cc-analyzer claude-dir set ~/work/.claude       # start the list with this one
cc-analyzer claude-dir add ~/personal/.claude   # append the next
cc-analyzer index          # the index mirrors the configured set
cc-analyzer stats          # both profiles, one report

set for the first one, add for the rest. That is deliberate: add appends to whatever is already in effect, which — before you have configured anything — is ~/.claude (or your CLAUDE_CONFIG_DIR). Two adds from a clean slate would therefore give you three directories, keeping the default alongside the two you named. That is the safe behaviour when you genuinely are adding to an existing setup, but if you want exactly the directories you list, begin with set.

cc-analyzer projects gains a claude dir column so you can tell them apart, and lists elsewhere name the directory only where two labels would otherwise be identical.

Managing the list:

cc-analyzer claude-dir                        # what is in effect, and why
cc-analyzer claude-dir add <path>             # append to what is in effect
cc-analyzer claude-dir set <path>             # replace the list with one
cc-analyzer claude-dir remove <path>          # drop one
cc-analyzer claude-dir reset                  # back to default resolution
cc-analyzer index                             # after any change

I just want to peek at another directory once

cc-analyzer --claude-dir=/mnt/backup/.claude projects
cc-analyzer --claude-dir=/mnt/backup/.claude sessions <projectId>
cc-analyzer --claude-dir=/mnt/backup/.claude analyze <session-id>
cc-analyzer --claude-dir=/mnt/backup/.claude doctor <session-id>

The flag covers exactly those four commands — the ones that read session files straight off disk. Anything index-backed (index, stats, audit, insights, report, serve, and the terminal UI) refuses it, because the index always covers every configured directory: a one-off scope would be silently ignored on a report, and would drop the other directories' rows on index. To scope those for real, configure the directories with claude-dir set and reindex.

Which directory wins

The first of these that names anything is used, and nothing below it is mixed in — so a directory you configure never silently picks up ~/.claude as well:

Order	Source	Notes
1	--claude-dir=<path>	One invocation; the four commands above only
2	CC_ANALYZER_CLAUDE_DIR	A :-separated list (; on Windows)
3	cc-analyzer claude-dir	Persisted in ~/.config/cc-analyzer/prefs.json
4	CLAUDE_CONFIG_DIR	Claude Code's own variable
5	~/.claude	The default

If your portfolio looks empty

cc-analyzer claude-dir

It prints every directory being searched, which setting put it there, and marks any that holds no projects/ directory:

Reading Claude Code data from:
  /Users/me/gone  (CLAUDE_CONFIG_DIR) — no projects/ directory

No Claude sessions found in any of these. If Claude Code stores its data
elsewhere, point cc-analyzer at it:
  cc-analyzer claude-dir set <path>

Two things worth knowing

Two directories can hold sessions for the same working directory. They stay separate projects rather than being merged, and the directory is named wherever the labels would collide.

The index mirrors your configured list, so removing a directory removes its sessions on the next cc-analyzer index. A directory that is merely unreachable at that moment — an unmounted volume, a folder mid-sync — keeps its data instead, so a disconnected drive never silently empties your history.

Telemetry & privacy

cc-analyzer reports anonymous, cookieless usage stats to a self-hosted Plausible instance, so its author can see which features are actually used. It is built to respect the tool's read-only, privacy-first nature:

• Never sent: session content, prompts, file paths, project names, tokens, costs, or anything identifying. Each CLI event carries only the command name (stats, index, …), the cc-analyzer version, your OS/arch, and a coarse session-count bucket (e.g. 11-100). The web app reports only which view you open (/session, /project, …) — the session id or project path in the URL is stripped before anything is sent.
• Where: the CLI and TUI send server-side events; the local web app (serve) bundles the Plausible tracker and this docs site loads its cookieless script. Telemetry state lives only under ~/.config/cc-analyzer/ — never in ~/.claude.
• Never in your way. A CLI command never waits on the network to report itself: it hands the event to a short-lived background copy of cc-analyzer and exits immediately. That is the second cc-analyzer process you may see briefly in ps — it sends one small request and stops. When telemetry is off, nothing is spawned and nothing is sent.
• On by default, easy to opt out. The first run prints a one-time notice.

Opt out in any of these ways — any one is enough:

cc-analyzer telemetry off        # persisted setting
export CC_ANALYZER_TELEMETRY=0   # per-shell / per-run
export DO_NOT_TRACK=1            # honored globally

Telemetry is also automatically disabled in CI (when CI is set). Check the current state any time:

cc-analyzer telemetry status

The DO_NOT_TRACK environment variable governs CLI telemetry and the locally served web app. In the web app and this docs site, localStorage.plausible_ignore = "true" disables browser analytics.

Run from source

With Bun ≥ 1.3:

git clone https://github.com/yorch/cc-analyzer.git
cd cc-analyzer
bun install
bun start <command>   # e.g. bun start stats

Uninstall

Remove the binary and, optionally, cc-analyzer's local state:

rm "$(command -v cc-analyzer)"
rm -rf ~/.config/cc-analyzer   # pricing cache + session index (safe to delete)

Your Claude Code data in ~/.claude — or any other directory you pointed cc-analyzer at — is never touched.

---

Next: build the index and read your stats ▸, or browse the docs ▸.