r/coolgithubprojects 18h ago

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

https://github.com/nickelsec/bough

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?

4 Upvotes

4 comments sorted by

1

u/BP041 18h ago

Nice—I've been meaning to do something like this too. Curious if you're pulling from the markdown session files directly or scraping from Claude Code's internal logs? The JSON metadata alongside each session has token counts and prompt lengths, tbh that's the part I'd want to visualize most.

1

u/VoidEqualZero 17h ago

the jsonl transcripts in ~/.claude/projects, one file per session. no separate metadata files, token counts are in those same records. deliberately skipped them though, /stats already does that well

1

u/Far-Entrepreneur-920 17h ago

Pretty neat! Can I configure what data is used?

1

u/VoidEqualZero 17h ago

Not yet, the thresholds are compile time constants right now :)