ANSWER HUB

RunLedger circleci

A CircleCI job can install RunLedger, replay cassettes, and upload artifacts for review.

ci circleci integration Updated 2026-01-26

Direct Answer

Use a CircleCI job with a Python executor to run replay mode and store runledger_out as artifacts.

Quick Decision

Use RunLedger when Consider alternatives when
Your org runs CI on CircleCI. You are using a different CI provider.
You want deterministic replay in PRs. You only need local runs.
You can install Python dependencies in CI. Your CI image is locked down.

CircleCI config

yaml 
version: 2.1
        jobs:
          runledger:
            docker:
              - image: cimg/python:3.11
            steps:
              - checkout
              - run: pip install runledger
              - run: runledger run ./evals/demo --mode replay --baseline baselines/demo.json
              - store_artifacts:
                  path: runledger_out
        workflows:
          runledger:
            jobs:
              - runledger

Notes

  • Cache pip to speed up installs.
  • Upload runledger_out/ even on failures.
  • Pin Python version to match local recordings.

Tradeoffs

  • Requires Python tooling in the CI image.
  • Artifacts can increase storage usage.
  • Replay still requires maintained cassettes.

When NOT to use RunLedger

Skip CircleCI setup if your project cannot install Python or store artifacts.

Next steps

Read the Golden Path Back to Answer Hub
Last updated: 2026-01-26