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

What you can do with Tracecrate

TraceCrate is a local-first, client-side workbench that reads AI agent trace files and shows a searchable timeline, recorded metrics, heuristic diagnostics, and side-by-side comparisons.

Trended earlier

FankChen/tracecrate on GitHub

Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk.

What do you want to do?

5 use cases

  • Read a Claude Code or Codex session step by step

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

    View prompt
    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.

  • Compare two agent runs event by event

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

    View prompt
    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.

  • Find failing and slow tool calls in an agent run

    Filter a session for reported errors and long durations, then review heuristic patterns.

    View prompt
    Using the TraceCrate repo at <repo path>, start the dev server and load <session file path>. Expected output: a Timeline filtered to reported errors or events above a chosen minimum duration, sorted longest first. Verify that events with missing duration are excluded when a minimum is set, and that heuristic flags are treated as hints, not confirmed causes.

  • Export a trace report with structure only

    Create a shareable JSON or HTML report that removes free text and original identifiers.

    View prompt
    Using the TraceCrate repo at <repo path>, load <session file path>, export a Structure only report with timing and token minimization enabled, and save it as <output path>. Expected output: a JSON or HTML file with no raw free text. Verify by reading the full download, since event order, counts, and statuses remain and can still be sensitive.

  • Explore synthetic agent runs without installing anything

    Open the hosted demo and follow the 30-second walkthrough on synthetic runs.

    View prompt
    Open the hosted TraceCrate demo at https://fankchen.github.io/tracecrate/ and follow its walkthrough on the two synthetic pagination runs. Expected output: a short summary of the Timeline filters, the Compare differences, and the redacted export preview. Verify that the summary does not describe the demo labels as measured results.

How to use Tracecrate

  1. Check you have what it needs: 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.
  2. Open FankChen/tracecrate on GitHub and read the README and license.
  3. Install Node.js 22.12 or newer (24 recommended) and npm.
  4. Run git clone https://github.com/FankChen/tracecrate.git
  5. Run cd tracecrate
  6. Run npm ci

These steps come from our top use case, Read a Claude Code or Codex session step by step, which also has a copy-paste agent prompt.

Tracecrate alternatives · Best AI repos for Software and DevOps

About this repo

  • Who it is forDevelopers and reviewers who run Claude Code, Codex, or OpenTelemetry-style agent traces and want to inspect, compare, or safely share what happened.
  • Why it is hot
  • LanguageTypeScript
  • Sourcegithub.com/FankChen/tracecrate · Back to Hot repos

Requirements

  • 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
Maintain Tracecrate? Add the Featured on Deduped badge

Paste this into your README:

[![Featured on Deduped](https://dedupedai.com/badge/fankchen-tracecrate.svg)](https://dedupedai.com/use-cases/fankchen-tracecrate/?ref=badge)

More badge styles and HTML

Questions about Tracecrate

What is Tracecrate?

TraceCrate is a local-first, client-side workbench that reads AI agent trace files and shows a searchable timeline, recorded metrics, heuristic diagnostics, and side-by-side comparisons. It is an open-source project on GitHub: https://github.com/FankChen/tracecrate.

Who is Tracecrate for?

Developers and reviewers who run Claude Code, Codex, or OpenTelemetry-style agent traces and want to inspect, compare, or safely share what happened.

What can I do with Tracecrate?

5 use cases so far, for example: Read a Claude Code or Codex session step by step; Compare two agent runs event by event; Find failing and slow tool calls in an agent run. Each has steps and a copy-paste agent prompt.

What do I need to run Tracecrate?

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.

What are alternatives to Tracecrate?

Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.

Is Tracecrate safe to run?

Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.