One passing run is a sample, not a test.
Agents are non-deterministic, so a single successful run proves almost nothing. Exact-match assertions are too brittle for generated text, and pass/fail hides the thing that actually regressed.
Run the same scenario against multiple agents from the same starting state, capture every decision as a commit, and score the runs comparatively with a judge agent. Two agents can reach the same answer by very different routes; only trajectory comparison sees the difference.
Scenario runner · judge scoring · run diffing · sealed audit epochs
Source-available under BSL-1.1, converting to Apache 2.0 18 months after each version's first publication. Internal use — including in production — is unrestricted.
What git was to source code, AgentStateGraph is to agent state.
Write a fact once. Every tool remembers it.
The context lives with the code, not in a chat log.
A conversation is a tree. Stop storing it as a line.
Optimise cost per unit of work, not cost per token.