Quick Start
1
Score a 2-agent workflow
2
Add a token-budget ledger
3
Run inside an EvalSuite
How It Works
Context Evaluator reads the workflow trace and measures how much of each agent’s response tokens survive into the next agent’s request.When to choose which dimension
Pick the dimensions that match the data you have.Configuration Options
Full parameter narrative lives in the SDK source.
Methods
ContextEvalResult properties: handoff_score, budget_score, overall_score (average of dimensions present), content_loss_detected, plus to_dict().
Common Patterns
Gate a workflow in CI, catch handoff regressions, or combine with the Harness Evaluator.- CI gate
- Context + accuracy suite
Best Practices
Feed the full trace, not just the final message
Feed the full trace, not just the final message
Handoff scoring needs both
llm_request and llm_response events for each agent. Pass the complete workflow.trace_events, not a single summary string.Match agent_order to your workflow order
Match agent_order to your workflow order
Scoring walks adjacent pairs in
agent_order. List the agents in the exact sequence they run so each handoff is compared correctly.A budget of 0 or None is neutral, not a fail
A budget of 0 or None is neutral, not a fail
Entries with
budget_tokens of 0 score a neutral 5.0. Set a real budget only where you want a gate.LLM-free and deterministic — safe in CI
LLM-free and deterministic — safe in CI
No live model call runs, so scores are reproducible and require no API key.
Related
Evaluation Suite
Run all four evaluators as one CI gate
Evaluation Loop
Iterative agent → judge → improve loop
Judge
LLM-as-judge for evaluating outputs
Harness Evaluator
Score Interactive Test Harness traces
CHL Engineering
The Context / Harness / Loop rubric this evaluator scores against.

