CL-SN55 941 —
GPT-61S 885 —
GPT-56T 861 —
GPT-6S 825 —
CL-OP55X 818 -0.1%
MUSE-SPK 793 —
QWEN-38X 779 —
GPT-6A 778 —
CL-OP5H 711 -0.1%
CL-OP5X 709 -0.1%
KIMI-K3X 699 -0.1%
CL-OP46H 694 -0.1%
CL-FAB5H 692 -0.1%
CL-OP55H 692 -0.1%
CL-OP47H 683 -0.1%
GEM-37FH 648 -0.2%
GEM-38FH 633 -0.2%
INKL 531 —
CL-OP47 529 -0.2%
GPT-56S 529 -5.9%
GEM-3P 493 —
CL-OP46 488 —
CL-OP48 481 —
GEM-31P 453 -0.2%
GPT-6L 436 —
CL-SN55 941 —
GPT-61S 885 —
GPT-56T 861 —
GPT-6S 825 —
CL-OP55X 818 -0.1%
MUSE-SPK 793 —
QWEN-38X 779 —
GPT-6A 778 —
CL-OP5H 711 -0.1%
CL-OP5X 709 -0.1%
KIMI-K3X 699 -0.1%
CL-OP46H 694 -0.1%
CL-FAB5H 692 -0.1%
CL-OP55H 692 -0.1%
CL-OP47H 683 -0.1%
GEM-37FH 648 -0.2%
GEM-38FH 633 -0.2%
INKL 531 —
CL-OP47 529 -0.2%
GPT-56S 529 -5.9%
GEM-3P 493 —
CL-OP46 488 —
CL-OP48 481 —
GEM-31P 453 -0.2%
GPT-6L 436 —
← Back to feed

Arena.ai Switches to LLM Judge for Agent Bash Reliability, Drops Rules That Flagged Correct Tests

Arena.ai updated its Agent Arena signal leaderboard on October 12 with two changes to how bash failures are measured: a new LLM-based failure detector and a revised scoring formula. The metric, formerly called Bash Recovery, is now named Bash Reliability.

What Was Wrong With the Old System

The previous system used a fixed set of rules to decide whether a bash call failed because of an agent mistake. According to Arena.ai, those rules had two systematic failure modes: they flagged correct test assertions and empty search results as failures, and they missed real errors when those errors were hidden by piped commands. In both cases, the score misrepresented what the agent actually did.

How the LLM Judge Works

The replacement is a single LLM judge that looks at each bash call in context. For each call it evaluates:

  • The purpose of the command — what the agent was trying to accomplish
  • The outcome — what the shell actually returned
  • The cause of any error — and whether the error was a genuine agent mistake
  • Self-correction — whether the agent identified and fixed the error within the same call

If an error was caught and resolved before control returned, the call is not penalised. The prior rules had no equivalent mechanism: an error in a piped command counted as a failure regardless of whether the agent handled it.

Scoring Changes

Arena.ai did not publish the full updated scoring formula in the changelog, but confirmed that both the failure detection method and the score derivation changed together. The rename from Bash Recovery to Bash Reliability reflects the shift from measuring error rate to measuring overall reliability of bash execution across a session.

Why This Matters

Agent Arena’s signal leaderboard is used by engineering teams to evaluate which models are safe to deploy in automated pipelines. A metric that penalises correct behaviour or ignores self-correction inflates failure rates for capable agents and deflates them for agents that produce quiet errors in piped workflows.

The switch to LLM-as-judge is consistent with how the wider agent evaluation space is evolving. Rule-based detection works cleanly for simple pass/fail assertions but breaks down when agent behaviour is conditional, contextual, or self-healing. LiveBench and similar platforms have made similar moves, using model judges for tasks that resist clean programmatic evaluation.

Arena.ai said the change results in a “more accurate assessment of whether a bash call failed.” Rankings on the Bash Reliability signal are expected to shift from prior Bash Recovery rankings as the new scores propagate.