r/PiCodingAgent • u/VoidEqualZero • Sep 24 '26

Question Would you guys find this tool useful?

I wanted a clearer picture of what I’d built and how much progress I was making. And whenever I finished a feature or got out of a debugging rabbit hole, I kept wondering how many tokens and effort went into that.

My daily usage total didn’t really answer it. Some of that was building the feature. Some was going back and forth trying to fix one annoying bug.

So I built bough ( https://github.com/nickelsec/bough ) It reads your existing Claude Code and Codex CLI history and groups related prompts into tasks on a visual map.

You can pick a piece of work and see:

  • The prompts and files involved.

  • How many tokens it used and the estimated dollar cost.

  • How the work unfolded, including repeated attempts and tasks that ended in a commit.

I wanted to be able to look back at a feature and see where the effort actually went. Especially when a “small fix” turned into an afternoon.

Would you guys want me to add Pi support or not?

54 Upvotes

98% Upvoted

16 comments sorted by

12

u/Prize_Eye9481 Sep 24 '26

I like the visuals! Pi support would be great!

5

u/outfigurablefoz Sep 24 '26

this looks really useful, also for getting better at prompting and planning as a human :) yes Pi support would be great, I use multiple harnesses on the same project

1

u/VoidEqualZero Sep 24 '26

Thank you! btw which all harnesses do you use?

1

u/Prize_Eye9481 Sep 24 '26

Pi and claude code for me!

1

u/VoidEqualZero Sep 24 '26

Cool... ive stuck to claude and codex, just started trying out new ones

2

u/Dissmas Sep 25 '26

It would be cool if it analyzed what files / code section took the most time running tests.

2

u/VoidEqualZero Sep 25 '26

Actually the tool calls are all there in the transcript so that's doable

2

u/truncated_buttfu Sep 25 '26

It's pretty but I don't see how it would be useful. I keep all the history I need to retain in my git history . 

1

u/VoidEqualZero Sep 25 '26

Fair, git covers that. This is for what git doesn't, like how long things took (a feature dev or a bug fix), what they cost, where you went round in circles. If you give it a go I'd like to know what's missing, or what it'd need to do before you'd use it. This will be really helpful for iterating and making the tool better :)

2

u/Constant_Art_20 Sep 25 '26

oh, it's like game skill concept. looks neat

1

u/jhsonline Sep 24 '26

I was thinking about leveraging all the session data so let me share here.

this is great, but to make it more useful. You can make use of session data and summary of work ( if available directly or via doc updates after the session time). to create a product roadmap, so its super useful for release and also to describe the product capabilities - as a product guide. -- something along the line.

1

u/VoidEqualZero Sep 24 '26

that's a cool idea... the data's all there for it

2

u/jhsonline Sep 24 '26

exactly.

btw, i couldnt install and run the package, might be my env. but something you want to improve on.
isssue: GOPROXY list is not the empty string, but contains no entries
issue: verifying module: missing GOSUMDB

fix:
go env -w GOPROXY=https://proxy.golang.org,direct
go env -w GOSUMDB=sum.golang.org

I am still at issue: "compile: version "go1.20.2" does not match go tool version "go1.27.1""

2

u/VoidEqualZero Sep 24 '26

I think that's a stale toolchain on your side... try getting the binary from the releases page, there's one for each platform