Get started

The shortest path to a verdict is a log file and one command — no CI, no token, no model. Start there, then wire it into a pipeline.

On GitHub Actions there is nothing to install. One step, and it defaults to the run that triggered it — skip straight to GitHub Actions.

What "getting started" actually involves

  1. Install it — or don't, on GitHub Actions.
  2. Replay a saved log offline to see the report shape.
  3. Get a read-scoped token when you want it to fetch a live run itself.
  4. Add the job to your pipeline, where it runs only on failure.

Steps 1–2 need nothing but Python. Everything after that is about letting it reach your CI provider. An LLM is optional at every step — without one you get the full deterministic report, not a stub.