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

How to export a trace report with structure only with Tracecrate

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

Who it is forA team member who must share an agent trace in a bug report or review but cannot send the raw transcript.

The problemRaw traces contain prompts, outputs, and identifiers that should not leave the machine by default.

The outcomeA structure-only JSON or standalone HTML report with a previewed boundary, ready to share after a full review of the download.

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 run dev and load the trace through Choose files.
  2. Open Export report and select Structure only.
  3. Optionally select Omit timing metadata and/or Omit token usage.
  4. Click Show redacted preview, then download JSON or a standalone HTML report.
  5. Open the full downloaded file and inspect every field before sharing it.

Prompt for your agent

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.

Caveat. Neither export mode guarantees anonymization, and switching to patterns clears the timing and token minimization.

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