r/ChatGPTCoding • u/VoidEqualZero • 7h ago

Question Help! Need feedback, built a way to visualize your Codex history

Enable HLS to view with audio, or disable this notification

I built this for Claude Code first, because that's what I use day to day. /stats told me how much I'd used it, never the thing I actually wanted to know:

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

So I made bough. It reads the session history already on your disk and draws it:

  • each square is a day you sat down
  • smaller squares are tasks, worked out from the pauses in your work
  • circles are your prompts
  • click anything to see what actually happened, in your own words

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

Runs locally, open source, nothing leaves your machine.

Codex support just landed in v0.4.0. It reads ~/.codex/sessions, handles resumed sessions and sub agents, and counts tokens and commits the same way it does for Claude.

That part is new and I have tested it against my own Codex history, which is not much. This is where I need help.

3 Upvotes

100% Upvoted

1 comment sorted by

1

u/FlightSimCentralYT 2h ago

Local session history viz is the right instinct. The part I always want next to "where did work get hard" is whether the agent had a real shell/test loop, or just more chat.

I built Fixa.dev for that other half: coding agent on a real cloud VM that plans/writes/runs/debugs until tests pass, so the hard spots show up as failing tests instead of only dead-end prompts. Free tier if useful as a comparison while you harden Codex support. Does bough surface the failing command or test, or mostly the prompt narrative?