# bough

> Claude Code and OpenAI Codex CLI write down everything you do with them.
> bough reads that back and draws what you built: a day you sat down, the work
> inside it, every prompt you typed, and which of them ended in a commit. You
> can search your prompts to find the one you half remember. It runs on your
> own machine, opens files that are already there, and sends nothing anywhere.

Every session leaves a JSONL transcript behind, Claude Code under
`~/.claude/projects` and Codex under `~/.codex/sessions`. Those files hold a
remarkably detailed record of how a piece of work actually went, and they are
close to unreadable: one session can run for days and wander through a dozen
unrelated things.

Other tools will read that history back as a conversation, or add up what it
cost you. bough answers a different question, which is what you built. It is
one Go binary with no dependencies and nothing to sign up for. Point it at a
project and it opens a diagram in your browser.

Once the diagram is open you can narrow it: to the work that touched one file,
to a range of dates, to the sittings worth calling sittings, or by typing words
you remember writing, which rings every prompt that holds all of them.

## Documentation

- [Getting started](https://www.bough.run/docs): installing it and reading your first project.
- [The transcript formats](https://www.bough.run/docs/format): where both agents keep your history, and the one pattern they share.
- [The Claude Code JSONL transcript format](https://www.bough.run/docs/format/claude-code): what is in the files under ~/.claude/projects, record by record, and the four things that will catch you out. The files are append-only with replay, so a naive line count comes out about three times too high.
- [The Codex CLI rollout file format](https://www.bough.run/docs/format/codex): what is in the files under ~/.codex/sessions, how a tool call is paired to its result, and why input tokens already contain the cached ones, so adding the two doubles every total.
- [Tuning](https://www.bough.run/docs/tuning): how bough decides where one piece of work stops and the next starts.

## Source

- [Repository](https://github.com/nickelsec/bough): Go, MIT licensed.
- [Releases](https://github.com/nickelsec/bough/releases): binaries for macOS, Linux and Windows.