cendor-cassette
Record an agent run once; replay it forever — deterministic, offline, and free. Unlike vcrpy
(HTTP-only), it captures the whole run: every LLM call and tool call, in order.
Agent tests with no API key — a recorded run replays in microseconds per call, offline.
·
pip install cendor-cassette
Using an AI coding assistant? npx @cendor/init (TS) / uvx cendor-init (Python) wires it up — or point it at cendor.ai/docs/for-ai-assistants.
from cendor.core import instrument
from cendor import cassette
client = instrument(OpenAI()) # the same instrumented seam used in production
@cassette.use("triage_happy_path.json") # record first run, replay after (auto mode)
def test_triage():
result = my_agent.run("My card was charged twice")
assert "refund" in result.tools_called
assert cassette.semantic_match(result.answer, "offers a refund")
Highlights
- Whole-run capture — every LLM and tool call, in order (not just HTTP, like
vcrpy). - Four modes —
auto(record then replay) ·record·replay(fail on an unrecorded call) ·rerecord(run live, reportdrift()without overwriting the committed cassette). - Decorator or context manager —
@cassette.use("run.json")/with cassette.using(...)(handy in pytest fixtures). - Meaning-based assertions —
semantic_match(actual, expected)(offline lexical default; opt into a free offline local-embedding scorer, a BYO-provider embedder, or an LLM judge).semantic_drift()filtersrerecordnoise down to real regressions. - Pluggable matching + redaction — a
normalizerignores volatile fields; secrets/PII redacted on write, but matching hashes the un-redacted request so redaction never collapses two distinct calls (redact=True|False|callable). - Parallel-safe — recording is scoped to the active
using()/use()context (aContextVar), so concurrent blocks never capture each other's calls; cassettes are written atomically. Under pytest-xdist, give each worker its own cassette path (e.g. suffix withPYTEST_XDIST_WORKER) so workers don't race on one file. - Faithful replay — dict-response providers (Ollama/Bedrock) replay as dicts and SDK-object providers as attribute objects;
stream=Trueandstream=Falsecalls match their own recordings (cassette format v2; committed v1 cassettes still replay). promote()turns a production JSONL trace into a replayable regression test (LLM and tool calls).
Semantic matching (opt-in)
semantic_match defaults to lexical_score — offline, deterministic, zero-dependency. For
meaning-aware (negation-sensitive) checks, pass a scorer into the existing hook. cassette binds no
model and adds no dependency unless you ask for one. Four tiers, hermetic-and-free → meaning-aware-but-costly:
- Lexical (default) —
lexical_score. Hermetic, deterministic, free, zero-dep. - Local embeddings (recommended) —
local_embedding_scorer(), free/offline/deterministic via model2vec static embeddings (numpy-only, no torch, ~8–30 MB). Behindpip install 'cendor-cassette[embeddings]'. - BYO provider embeddings —
embedding_scorer(embed_fn)wraps any provider (OpenAItext-embedding-3-small/large, Googlegemini-embedding, Cohereembed-v3; Anthropic has no embeddings API → use Voyage). Non-hermetic: a cloud embedder calls the network at score time.openai_embedding_scorer(client, model="text-embedding-3-small")is a thin convenience over an already-built OpenAI-shaped client. - LLM-judge — a
scorerthat calls your own instrumented client (a documented recipe, never a shipped dependency). Non-hermetic, non-deterministic, costs money.
from cendor import cassette
score = cassette.local_embedding_scorer() # free, offline, deterministic
assert cassette.semantic_match(result.answer, "offers a refund", scorer=score)
assert not cassette.semantic_match("we will not offer a refund", "offers a refund", scorer=score)
drift() stays byte-exact; at temperature > 0 it flags every run. semantic_drift(threshold=0.8, scorer=None) re-scores each divergence's recorded-vs-live text and keeps only those below the
threshold (real regressions, with a score), so cosmetic rewording is ignored. The alternative for
byte-stable drift: record/replay at temperature=0.
Wrap-around, test-time only — records via core's bus, replays via a core interceptor; no second patch, no network.
See docs/cassette.md · CHANGELOG. Part of the Cendor stack — github.com/cendorhq/cendor-libs. Powered by PowerAI Labs. Apache-2.0; provided "as is", without warranty — use at your own risk (LICENSE §7–8).
Metadata
Release files for cendor-cassette 1.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cendor_cassette-1.1.1.tar.gz | 32.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cendor_cassette-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.7 kB
Release files / cendor_cassette-1.1.1.tar.gz
| Download URL | cendor_cassette-1.1.1.tar.gz |
|---|---|
| Size | 32.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c730ae03171de53761289f355ecba13634ce34f7ba5563515432213bc209cf8
|
|
BLAKE2b-256 checksum How to use checksums |
44b9842d3c8e2b4449491716fa6241c4b8b810405cecd97bb12d9cd224d1b357
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logRelease files / cendor_cassette-1.1.1-py3-none-any.whl
| Download URL | cendor_cassette-1.1.1-py3-none-any.whl |
|---|---|
| Size | 22.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ea5d5ea82215c2e56b3a4bf0fbef77d6523533183c4ad139acd931e8af9a3ab6
|
|
BLAKE2b-256 checksum How to use checksums |
dd895770543fee611f8ee543ed37785e3f94134420f2b88159aa536e724d0723
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency log