Bough banner
nickelsec nickelsec

Bough

Development community

Description

Visualize your Claude Code session history as a diagram of the work you actually did: days, tasks, prompts and the commits that landed. Local-first, single Go binary, nothing leaves your machine.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

bough

Read your Claude Code history and see the work you actually did.

CI Release MIT Documentation

Not how many tokens you burned or how long your streak is. Claude Code's own `/stats` covers that. This answers a different question: what did you actually build?

Run it

bough

That is the whole thing. It finds your projects, asks which one, and opens it in your browser.

What you get is a diagram of your own work. A square on the line is a day you sat down. Smaller squares hanging off it are the tasks inside that day. 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.

To get those right, bough also reads the git history of the project it is describing, at the path your transcripts already name. That is a read and nothing else: no writes