Merge every opencode session belonging to a project into one chronological transcript, laid out for the terminal.

An agent driven from more than one place at once — a chat bridge, a scheduled run, someone at the TUI — gets a separate opencode session for each. oc-transcript walks opencode's SQLite store and interleaves them into a single stream, each run of blocks opening under a banner naming the session it belongs to and the directory it ran in. A subagent's tag ends in ↓ and its banner rule is dashed rather than solid.

To audit a run after it happened: where the agent went wrong, and what to change so it does not go wrong the same way again. For a background run — a scheduled job, an agent driven from a chat bridge, a subagent that did most of the editing — nobody watched it happen, so the transcript is the only record there is.

--tools full prints the arguments each call was made with, the output that came back, the error when it failed, and how long it took. That is where the tooling problems show up — a description bad enough that the arguments are always wrong, output truncated before the useful part, an error the agent can't act on and retries three times over, a skill invoked two steps too late. --reasoning adds what the model thought it was doing right before the wrong turn.

And because every session under the project lands in one ordered stream, a mistake that repeats across a week of runs is one oc-transcript --all | grep … away — a pattern rather than an anecdote.

Grab an archive for your platform from the releases page, or install it with the Go toolchain:

go install github.com/Chi-teck/oc-transcript@latest

Or build from a checkout:

CGO_ENABLED=0 go build -o oc-transcript .   # or: task build

oc-transcript                      # last 24h of sessions run under the cwd
oc-transcript --all --tools full   # everything, with full tool output
oc-transcript --list               # just the sessions, no messages
oc-transcript --follow             # keep printing new turns as they complete

Scope is the working directory, the way git scopes itself: the sessions whose working directory sits inside --root are the ones you get. --everywhere ignores the root and takes the whole database. The path at the right of a banner is the directory that session ran in, written out whole rather than relative to the root: a transcript is usually redirected to a file and read somewhere else, where a relative path names nothing.

 ⚑ ❬a1b2c3❭ Flaky follow test                        ~/src/oc-transcript
────────────────────────────────────────────────────────────────────────

  │ 2026-08-17 10:01:00 • user
  │
  │ ci is red on main: TestFollowCursor times out. find the cause and
  │ fix it


  │ 2026-08-17 10:02:00 • assistant • claude-opus-5
  │
  │ Reproducing before I change anything.
  │
  │ bash go test ./internal/app -run TestFollowCursor        ok    10.4s
  │ read internal/app/follow.go                              ok     0.1s
  │ edit internal/app/follow.go                             ERR     0.1s
  │   err oldString not found in file
  │ edit internal/app/follow.go                              ok     0.2s
  │ bash go test ./internal/app -run TestFollowCursor        ok     2.6s
  │
  │ Fixed — the cursor now only advances past printed rows.

The flag before a tag says where the rest of that session is:

Times are local — whatever $TZ resolves to, and the same zone --since/--until are read in. The zone is not printed, so use TZ=UTC oc-transcript … if a transcript written with --out will be read elsewhere.

Run oc-transcript --help for the full list. The ones you reach for:

task check         # gofmt, go vet, golangci-lint, go test — the pre-commit gate
task test:update   # regenerate the golden files, then re-run the tests
task build         # CGO_ENABLED=0 go build -o oc-transcript .

Expected output is fixed by the golden files in internal/app/testdata/. CI runs the same checks on every push and pull request; pushing a v* tag publishes a release.

MIT — see LICENSE.