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

How to compare two agent runs event by event with Tracecrate

Load two sessions and see recorded metric differences and aligned tool calls.

Who it is forAn engineer testing a prompt, configuration, or code change who wants to know how two agent runs differ.

The problemComparing two long agent runs by hand means matching events and metrics across two separate transcripts.

The outcomeA comparison view showing recorded metric differences, tool-call counts, and changed fields for aligned events, with links back to the original events.

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. Run npm ci and npm run dev in the cloned Tracecrate folder, then open the printed address.
  2. Click Choose files and select the baseline session and the changed session together, up to 5 files per selection.
  3. Open Insights, then Compare.
  4. Scroll to Event-by-event comparison and check changed fields, or choose Tools only.
  5. Click an event button to jump to the original session and timeline page.

Prompt for your agent

Using the TraceCrate repo at <repo path>, start the dev server and load the two authorized session files <baseline file> and <changed file>. Expected output: the Compare view with recorded metric differences shown as B minus A and an event-by-event list. Verify that the comparison is described as descriptive, since repeated tool names can align ambiguously and this is not a controlled benchmark.

Caveat. The README labels its demo baseline and optimized runs as manufactured, so comparisons show what was recorded, not measured improvements.

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