What shipped

Graphs are declared in code and versioned alongside your agents. A supervisor can fan out to children in parallel or sequence them, and the retry budget is enforced across the whole tree rather than per node.

Delegation respects the parent’s retry budget and handoff policy. If a child trips a handoff condition, the whole workflow escalates rather than the child failing silently.

The regression landed in v1.7.0 with the stricter schema validator and affected any agent whose tools declared required fields. No migration is needed.

Budgets now decrement once per attempt. No change is needed on your side — existing agents will simply use the budget you configured.

Suites live beside your agent definitions and run inside the same job as the rest of your tests, so there is no extra infrastructure to stand up.

Thresholds are declared per case. A regression below the floor fails the job with the offending run linked, so reviewers land on the trace rather than a log dump.

Existing keys keep their current access until you scope them, so nothing breaks on upgrade. Scoping is available from workspace settings and through the management API.

Each tool contract can additionally declare an allowlist of hosts it may reach. Calls to anything outside the list are blocked before the handler executes and surface as a policy span in the trace.

This changes the SDK’s default flush behaviour. If you were polling for completed runs, you can subscribe to the span stream instead and drop the poll loop.

The export path is unchanged — OpenTelemetry batches still ship on the same interval, so existing collectors need no reconfiguration.