RepoJournal
Safety Evals Safety Evals
39 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-11-03
stories 61

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

Per-agent sandbox identities, and a math scorer that stops lying

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

inspect_ai lets several agents share one sandbox without sharing a Linux user, while inspect_evals fixes a scorer that was recording genuine antlr4 breakage as a model failure.

fix(math): surface an unusable antlr4 runtime instead of scoring every sample wrong UKGovernmentBEIS/inspect_evals

by mkzung

The math scorer's is_equiv_sympy swallowed every exception and returned False, so a missing or mismatched antlr4-python3-runtime (4.13.2 under sympy 1.14.0, for example) scored every sample wrong, is_equiv_sympy("2", "2") included, with the cause visible only at debug log level. ImportError from parse_latex now propagates instead, so an unusable runtime surfaces as an error rather than as near-...

feat: run each agent's sandbox tools as its own user (#6190) UKGovernmentBEIS/inspect_ai

by Ransom Richardson

sandbox_identity(user, cwd=, sandbox=) is a ContextVar scope that makes the built-in exec inside it run as the given Linux user. Several agents can now share one sandbox with per-agent isolation, since built and library-built tools are shared objects whose user has to be set at call time rather than construction.

fix(agent-bridge): Gemini tool calls through the chat completions bridge keep their thought signatures UKGovernmentBEIS/inspect_ai

by taxfree-python

On the chat completions bridge, messages_from_openai restored only the first reasoning block and dropped its internal field, so for Gemini 3 the thought signature stayed in the assistant text and tool calls went out unsigned. Those calls used to come back as a 400 from Gemini; they now keep their signature across the round trip.

fix(run_evals): skip SKIPPABLE_TASKS up front and make clean() failures non-fatal UKGovernmentBEIS/inspect_evals

by MattFisher

The smoke runner no longer dies when clean() raises, such as an OSError: Directory not empty on arvo while an orphaned cybergym download is still writing, and SKIPPABLE_TASKS is now applied up front so skip lists actually keep a task from running. If you run the eval sweep, a stuck cleanup now costs you a chunk rather than the whole run.

feat: experimental transcript events for agent communication and agent swarm evidence UKGovernmentBEIS/inspect_ai

by ransomr

Step one of the swarm event-type design lands experimental transcript events for agent communication and swarm evidence, replacing the InfoEvents that made hiding a swarm's messages also hide every other info event in the viewer. Also merged: the dev extra moves ruff from 0.9.6 to 0.17.2 and the python-packages group takes 36 dependency bumps, plus a fix that stops core_bench from constructing ...

Quick answers

What shipped in Safety Evals on November 3, 2026?
inspect_ai lets several agents share one sandbox without sharing a Linux user, while inspect_evals fixes a scorer that was recording genuine antlr4 breakage as a model failure. In total, 29 commits and 32 pull requests landed.
Who contributed to Safety Evals on November 3, 2026?
7 developers shipped this update, including Ransom Richardson, brandly, taxfree-python, dependabot, MattFisher, claude-code-aisi, and mkzung.
What were the notable Safety Evals updates?
fix(math): surface an unusable antlr4 runtime instead of scoring every sample wrong, feat: run each agent's sandbox tools as its own user (#6190), and fix(agent-bridge): Gemini tool calls through the chat completions bridge keep their thought signatures.