docs / workflow / review

Inbox

The inbox is where you inspect and edit staged traces before committing. Use the web inbox, the terminal inbox, or the session CLI subcommands.

Web Inbox

opentraces web
opentraces web --port 8080

This serves the React viewer from web/viewer/ through the local Flask app. The timeline view shows each step with tool calls and token counts. The review view groups context items by source (user input, filesystem, external, LLM output).

Web inbox - timeline view

Web inbox - review view

Terminal Inbox

opentraces tui
opentraces tui --fullscreen

Three-panel layout: sessions list, summary, and detail. Keyboard shortcuts for navigation, commit, reject, and discard.

Terminal inbox

CLI

opentraces session list
opentraces session show <trace-id>
opentraces session show <trace-id> --verbose
opentraces session commit <trace-id>
opentraces session reject <trace-id>
opentraces session reset <trace-id>
opentraces session redact <trace-id> --step 3
opentraces session discard <trace-id> --yes

commit moves a trace directly to Committed, reject keeps it local only, reset sends it back to Inbox, and redact rewrites the staged JSONL in place. session show --verbose prints the full step-level detail including raw tool inputs and outputs.

Stage Vocabulary

StageMeaning
inboxNeeds review
committedBundled for upload
pushedPublished upstream
rejectedKept local only

What To Look For

  • Secrets that escaped redaction
  • Internal hostnames and collaboration URLs
  • Customer names, paths, or identifiers
  • Traces that are too short or too trivial
  • Tool outputs that should be redacted before sharing

Inbox Flow

opentraces session commit <trace-id>
opentraces commit --all
opentraces push

If you need the old compatibility entry point, opentraces review still exists as a hidden alias, but web, tui, and session are the current surfaces.