DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to read a Claude Code or Codex session step by step with Tracecrate

Load one authorized agent session file and browse its events in a local timeline.

Who it is forA developer who ran Claude Code or Codex on a task and wants to see the exact sequence of messages, tool calls, and results.

The problemRaw agent transcripts are long JSONL files that are hard to scan for what the agent actually did.

The outcomeA searchable, filterable timeline of the session where tool inputs, outputs, and recorded errors can be opened and read.

What you need first

  • Node.js 22.12 or newer (24 recommended) and npm for local use
  • A modern desktop browser with Web Workers support
  • Trace files you are authorized to inspect: Claude Code JSONL, Codex rollout JSONL, OTLP JSON, or TraceCrate native JSON

Steps

  1. Install Node.js 22.12 or newer (24 recommended) and npm.
  2. Run git clone https://github.com/FankChen/tracecrate.git
  3. Run cd tracecrate
  4. Run npm ci
  5. Run npm run dev, then open the address Vite prints.
  6. Click Choose files, select only a session file you are authorized to inspect, then open a tool event in Timeline.

Prompt for your agent

Using the TraceCrate repo at <repo path>, run npm ci and npm run dev, then load the authorized session file <session file path> through Choose files. Expected output: a Timeline listing that session's events with search and kind filters working. Verify that token totals appear only where the file reports them and that missing values are shown as unknown, not zero.

Caveat. Claude session files are private, so only select files you are authorized to inspect, and TraceCrate does not scan agent directories for you.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page