Cclens

cclens

A lens onto your Claude Code usage. cclens reads your session transcripts and
live configuration, extracts them into a local SQLite store, and shows where
time, tokens, and effort are being wasted — and how to fix it: unused or heavy
config, recurring tool failures, where the work gets stuck, and the cost picture
behind it all.

The design intent lives in docs/specs/; this README is how to
run it.

Install / build

With Homebrew (macOS and Linux, Intel and arm):

With Cargo, from crates.io (builds from
source; bundled SQLite needs a C compiler):

With Nix (no toolchain to set up):

From source — dev tools are pinned by the Nix flake, tasks run via just:

Plain Cargo also works (cargo build --release) if you have a recent stable
Rust; the flake just pins it. CI runs nix develop -c just check / just test.

Publishing a GitHub Release for a vX.Y.Z tag builds binaries for Linux, macOS,
and Windows (x86_64 and arm64 each), attaches them to that release with
.sha256 files, points the
lambdalisue/homebrew-cclens
tap at the new archives, and publishes the crate to crates.io. The release is
published before its assets are built, so the notes are visible for a few
minutes with nothing attached yet.

The tag is the only place a version is written down: the release workflow
rewrites version in Cargo.toml from it before building and publishing, so
the committed 0.0.0 is a placeholder and cutting a release never means
bumping a file first. The flake stamps it too, without being told the tag:
VERSION is marked export-subst, so the archive GitHub serves for the tag
carries the tag in it (see
nix-github-release).

The tap covers Linux and macOS only; on Windows, take the -pc-windows-msvc
archive for your arch from the release, or build from source. CLAUDE_CONFIG_DIR
names the…