RepoJournal
Safety Evals Safety Evals
16 wires and counting

$ follow Safety Evals

Keep up with Safety Evals in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-10-17
stories 22

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Inspect adds tool state scopes, fixes usage undercounting

By RepoJournal · Filed · About Safety Evals · Composed from the cited sources · methodology

inspect_ai shipped a breaking change giving concurrently running agents their own tool state, and fixed token and cost accounting that undercounted whenever a provider sent several billed requests inside one generate() call.

feat!: tool state scopes so agents running concurrently in one sample keep separate tool state (#5861) UKGovernmentBEIS/inspect_ai

by Ransom Richardson

Built-in tools that keep state in the sample store (memory, bash_session, web_browser, skill) used to share that state across every agent in a sample that left instance at its default; a new tool_state_scope() lets concurrent agents such as inspect_swarm members keep separate state. Marked breaking, so check your tool configuration against the new default before upgrading.

fix: usage undercounted when a provider call sends several billed requests (#5643) UKGovernmentBEIS/inspect_ai

by Ransom Richardson

Three providers sent more than one billed request inside a single generate() call but reported the usage of only one, so token and cost accounting and limit enforcement undercounted. Anthropic pause_turn continuations now sum usage over the head request and every continuation, with the chain bounded; rerun any cost or token figures produced under the old accounting.

fix: gemini-2.5-pro repeating tool calls after a tool result (#5753) UKGovernmentBEIS/inspect_ai

by Ransom Richardson

gemini-2.5-pro repeated tool calls after a tool result far more often through Inspect than through the google-genai SDK, sometimes until a limit stopped the sample. Same-batch trials of check_tools_force traced it to the system hint, which drove extra tool calls in 4 to 8% of samples; the fix sends tool results in the documented shape and drops the hint.

ci: prewarm pytest's assertion-rewrite cache so CI test workers start sooner (#5897) UKGovernmentBEIS/inspect_ai

by Eric Patey

Prewarming pytest's assertion-rewrite pycs and suspending GC during collection cuts the time before the first CI test runs by roughly 40%, from about 54s per test leg. Contributor tooling only, nothing to change in how you run evals.

Quick answers

What shipped in Safety Evals on October 17, 2026?
inspect_ai shipped a breaking change giving concurrently running agents their own tool state, and fixed token and cost accounting that undercounted whenever a provider sent several billed requests inside one generate() call. In total, 11 commits and 11 pull requests landed.
Who contributed to Safety Evals on October 17, 2026?
2 developers shipped this update, including Eric Patey and Ransom Richardson.
What were the notable Safety Evals updates?
feat!: tool state scopes so agents running concurrently in one sample keep separate tool state (#5861), fix: usage undercounted when a provider call sends several billed requests (#5643), and fix: gemini-2.5-pro repeating tool calls after a tool result (#5753).