COLDWORKS / docs / quickstart DESIGN PREVIEW · COLDWORKS-AUDIT HAS NOT SHIPPED Registry
GETTING STARTED

Quickstart

First audit in under a minute. There is nothing to install and no account to make — the only prerequisite is uv, which most Python developers already carry.

What to download

Nothing, in the usual sense. uvx fetches and runs the audit in one step, in an isolated environment it cleans up itself. If you prefer a persistent install:

EITHER WORKS
$ uvx coldworks-audit --help          # run without installing
$ uv tool install coldworks-audit     # or keep it on your PATH
No API key, no signup, no Docker, no database. The audit is a program that reads a file on your disk and writes a report next to it.

See it work before you export anything

Empty-handed? The package bundles a sample trace export and matching documents, so the first report costs you nothing but the command:

SAMPLE RUN
$ uvx coldworks-audit run --sample --open

This renders the full report — headline, repeat groups, anchored decisions, loss populations — on data we wrote, labeled as such on every screen.

Your first real audit

  1. Export traces from wherever they live — takes about 30 seconds. See Connect your traces for the Langfuse, LangSmith, and OpenTelemetry paths.
  2. Run the audit on the file:
FIRST REAL RUN
$ uvx coldworks-audit run ~/Downloads/traces.jsonl --open
  1. Read the headline. The fraction of your agent's tool calls that were exact repeats of a judgment it already made — in your own tool vocabulary. Repeats count as cache candidates only when their results agree; disagreeing repeats are reported separately as nondeterminism findings.

If the audit can't read your export

It doesn't report a silent zero. It prints a field census — "your spans carry tool names but not structured arguments" — so even a failed audit hands you a concrete, forwardable finding about your own telemetry.

Where to go next