Bough

Reads your Claude Code, OpenAI Codex CLI and Pi session history, draws what you actually built, and prices it.

Not how long your streak is. Claude Code's own /stats covers that. This
answers a different question: what did you build, and what did each piece of
it cost?

Usage tools stop at a session, and a session is a hash that can cover weeks of
unrelated work. bough works out where one piece of work ends and the next
begins, so the money lands on things you recognise: that feature, that
afternoon lost to one bug.

Run it

That is the whole thing. It finds your projects and opens them in your
browser, a card for each with your time at the keyboard and what it cost.
Search them, narrow them to one agent, or sort by time or cost, then click one
to open it. Projects, at the top left, takes you back.

Inside a project you get a diagram of your own work. A square on the line is a sitting,
labelled with the day, the time you started and how long you were at the
keyboard. Smaller squares hanging off it are the tasks inside that sitting.
Every circle is a single prompt you typed.

Hover anything and the path back to its day lights up, with a note saying what
it was. Click it and the full record opens beside the drawing, scrolled to the
exact prompt, in your own words and untrimmed. Work that went badly is drawn in
rust rather than green.

A task carrying a small mark is one that ended in a commit, and the note gives
you the hash and the message. Everything else in the drawing is worked out from
your history; this is the part you can go and check.

Dotted lines can join sittings that went back to the same files, so work picked
up again later can be followed across the gap. On a long project there are a
lot of them, so they start hidden, and "What to show" in the rail turns…