Skip to main content

Framework recipes

Use these recipes after the quick start. Each path keeps the same operating loop: create a baseline, capture traces, promote reviewed failures into eval coverage, and gate regressions in CI.

Pick the shortest path

Node or Next.js

Use this when your app already has npm test, pnpm test, or a similar quality command.
Add a trace around the code path you want reviewers to inspect:
app/api/support/route.ts
Gate the same behavior in CI:

Python or FastAPI

Install the SDK and bundled CLI:
Add an async trace in the request path:
app.py
Run the local proof before opening a PR:

LangChain or RAG

For agents, chains, and retrieval systems, start by tracing the workflow shape. Then label the traces that reveal missed intent, wrong tool use, unsupported claims, stale retrieval, or unsafe output.
Use the generated cases as drafts. Keep them quarantined until a reviewer promotes them:

The proof packet

Every recipe should produce the same reviewer packet before a change merges: If one of those artifacts is missing, run: