ccgarden

Grow a garden from your local Claude Code session history.

ccgarden reads the JSONL transcripts under ~/.claude/projects, rolls them up into a small sqlite history db, and renders the result as an SVG tree: one growing organism that represents everything you've built with Claude Code on this machine.

(This is a dummied-up example with a few months of synthetic data across five repos, several models, and a handful of tools — enough to show every shape the renderer draws. Your own garden will look sparser at first and fill in as you work.)

What each shape means

Hover (or tap, on mobile) any shape for the exact numbers behind it.

Install

uv tool install ccgarden

(or pipx install ccgarden). This installs two commands: ccgarden and ccstats.

To hack on it instead, clone the repo and run uv sync, which puts the same two commands in the project's virtualenv.

Usage

uv run ccgarden

This will:

1. Scan ~/.claude/projects and record today's snapshot into ~/.claude/ccstats.db (same as running ccstats — see below).
2. Replay the full day-by-day history from that db into an animated SVG timelapse of the garden growing.
3. Write it to ~/.claude/ccgarden.svg and open it in your browser (add --no-open to skip that last step).

Run it again any day and the garden picks up where it left off — new rings, longer branches, bigger clouds, more leaves.

Options

So a still image of just this year's garden, written somewhere else and without touching the db, is:

ccgarden --static --since 2026-01-01 --no-record --no-open -o garden.svg

The plot (--plot)

A bird's-eye kitchen garden from the same data. Each repo is a raised bed (area = lines added + sessions). Every model and effort combo is its own plant: Opus grows brassicas and fruiting plants, Sonnet leafy greens, Haiku herbs. More plants mean more sessions, bigger plants mean more effort, and the legend lists which plant is which and its share of replies — hover one to find it in the beds. Skills bloom in the flower border. The potting bench holds your busiest tools, the rain barrel fills with tokens, and the sundial shows the hours you prompt (blue petals = night). Butterflies come out on working days, fireflies at night, and rain and weeds when you stay away. A bed you've worked in the last 14 days has its sprinklers running and dark, wet soil; the soil dries and the spray shrinks the longer it's left. In the timelapse each plant sprouts and grows as its repo's sessions add up, and each flower swells with its skill's calls; it has a Replay button and a day slider.

ccstats

The underlying stats engine can also be run on its own, for a terminal-native usage report instead of (or before) rendering a garden:

uv run ccstats                       # summarize all local session logs
uv run ccstats --since 2026-06-01    # limit the window
uv run ccstats --json                # machine-readable output
uv run ccstats --record --since 2026-01-01 --until 2026-07-01  # backfill history

Run uv run ccstats --help for the full list of flags.

Development

uv run pytest
uv run ruff check .

License

MIT — see LICENSE.