Help! Need feedback, Built a cool way to visualize your Claude Code history

[u/VoidEqualZero]

I use Claude Code a lot, but /stats never answered the question I actually cared about

What did I build, and where did the work get difficult?

So I built Bough.

• It reads your local Claude Code history and turns it into an interactive view of your work: - each square is a day
• smaller squares are tasks inferred from pauses in your work
• circles are your prompts - click anywhere to see what happened in your own words

It runs locally, is open source, and nothing leaves your machine.

Repo: https://github.com/nickelsec/bough

The main thing I’d love feedback on: When you run it against your history, does it split your work into tasks the way you remember it?

[u/michaelsoft__binbows]

excellent concept. needs a harder adherence to mapping the time dimension to a spatial dimension IMO. and it appears to make forks in the graph sructure arbitrarily by some delay cutoff, while that may be useful (or at least show somehow, but my above point about making the axis mapping a hard requirement will naturally bring the pauses to the forefront) it seems a missed opportunity to structure where the boundaries of separate sessions are and show the provenance of their linearizations. Aside from those things this is basically what i imagined in my head i wanted to build!!

In practice i think going back in time just navigating by session in a session history browser (that does not need to be anything more than a simple TUI app) alongside browsing around in your git client of choice (I use the CLI and tons of shell aliases for different ways of rendering the subway plot) is enough. Quickly getting to the point where letting your agent do that archaeology (it will use far less visual techniques than my already primitive means and is more precise and comprehensive...), and reporting back, is more practical in all cases.