Skip to content
← Back to research index

abstract indexed · arXiv 2610.12569 · updated 2026-10-18

SWE-Duel: Towards a Self-Scaling Arena for Coding Agents

First page of SWE-Duel: Towards a Self-Scaling Arena for Coding Agents
From the original paper · arXiv 2610.12569Page 1. Select the image to read the PDF.

SWE-Duel replaces static, leak-prone coding benchmarks (e.g., SWE-bench-style fixed task sets) with evaluation-time task generation, where agents alternately author buggy pull requests and review each other's under mirrored Red-Blue turns with test-based oracles. The cost is substantial: each turn requires three context-isolated Red sessions plus a blind repair check and a Blue review, and the reported tournament ran 1,500 turns across 11 frontier model-harness pairs, which is entirely API- or compute-billed agent execution rather than a one-time benchmark download. It can fail as a procurement signal because the oracle only checks test outcomes (subtle bugs can slip through if feature and bug tests are weak), results depend heavily on the harness rather than the model alone, and a two-agent duel format is a research artifact with no production role for a small team.

For solo builders

A possible application for this research area. Paper-specific feasibility still needs a full-paper review.

An agent looks good in demos, but you cannot tell which product tasks it fails.

What you would change

Use the study's evaluation idea to inspect a small set of tasks with human-checked answers.

Try the idea on your product

A proposed first test. Set your budget and success criteria before running it.

Use the study's evaluation idea to inspect a small set of tasks with human-checked answers.

Compare against

Your current evaluator and a manually reviewed reference set.

  1. Locate the paper's implementation and check its license, model support, data needs, and hardware requirements. Stop here if you cannot obtain the required artifacts.
  2. Save a small set of representative product tasks and expected outcomes. Keep evaluation tasks out of any training or tuning, and choose quality and cost limits before running.
  3. Run the baseline and the proposed change on identical inputs. Keep other settings fixed and repeat paired runs to expose variation.
  4. Save per-task outputs, failures, timings, and all usage costs. Review regressions before expanding the test.

What to measure

Agreement with human review, missed failures, false alarms, and evaluation cost per task.

When to keep it

Keep the change only if it meets your preselected quality and latency limits and improves the metric you care about after setup and operating costs. Otherwise retain the baseline. This is an exploration plan, not a validated recommendation.

Download test plan ↓

abstract indexedPaperraft next step

Do not allocate compute yet.

This page uses the abstract and public adoption signal only. Request the deep report before relying on its recommendation.

Abstract-level screening only. Risks and infrastructure may not have been evaluated. This recommendation is not a reproduced result.
minimum test setup
not reported
published evidence setup
not reported
source-linked claims
0 of 2
exposure checks
0 of 8

Why it was shortlisted

The technical change, research area, and reason it entered the archive.

recommendation
watch
research area
agent evaluation
technical change
Self-scaling Red-Blue arena for coding-agent evaluation
published
2026-10-08

This is a benchmark methodology paper, not a production technique; it is relevant for tracking how coding agents will be compared, but reproducing or depending on it requires frontier-model API spend and evaluation infrastructure that a constrained team should not build, and its rankings can inform model selection only after independent validation.

About the technical core

Equations have not been fetched yet.

When reading the methods, identify the rule, algorithm, or evaluation protocol that produces the claimed change. An equation is useful here only if it explains that mechanism.

Inspect the original paper

Claims and evidence

A claim is source-linked only when the PDF page and matching excerpt are available.

  1. claim 01Paperraft inference
    Read the brief interpretation

    SWE-Duel replaces static, leak-prone coding benchmarks (e.g., SWE-bench-style fixed task sets) with evaluation-time task generation, where agents alternately author buggy pull requests and review each other's under mirrored Red-Blue turns with test-based oracles. The cost is substantial: each turn requires three context-isolated Red sessions plus a blind repair check and a Blue review, and the reported tournament ran 1,500 turns across 11 frontier model-harness pairs, which is entirely API- or compute-billed agent execution rather than a one-time benchmark download. It can fail as a procurement signal because the oracle only checks test outcomes (subtle bugs can slip through if feature and bug tests are weak), results depend heavily on the harness rather than the model alone, and a two-agent duel format is a research artifact with no production role for a small team.

    This is a Paperraft inference. It is not pinned to a verified PDF passage.

    Inspect the source
  2. claim 02Paperraft inference

    The strongest solver (GPT-5.5 with Codex CLI) repaired 98.3% of reviewed defects; tasks authored by the newest model version defeated a fixed-reference solver 42.9% of the time versus 4.0% for older versions, suggesting difficulty scales with authoring capability.

    This is a Paperraft inference. It is not pinned to a verified PDF passage.

    Inspect the source

Exposure map

Author findings, Paperraft interpretations, and the next check. Missing analysis never counts as evidence of safety.

quality

Still unknown

Which tasks improve, and which regress against the baseline?

compute and memory

Still unknown

What memory, hardware, and total compute does the complete method require?

latency

Still unknown

Are startup time, typical response time, and slow requests measured separately?

operations

Still unknown

What must be monitored, maintained, and rolled back?

software compatibility

Still unknown

Does the implementation support your model, runtime, and hardware?

security

Still unknown

What new data access, permissions, or trust boundaries does it introduce?

data and training

Still unknown

What data preparation or training is required, and is it included in the cost?

reproducibility

Still unknown

Are code, versions, inputs, and evaluation scripts available?

Continue the investigation

A reading guide for agent evaluation.

Editorial prompts, not findings from this paper or a validated test plan. Detailed analysis is still pending for the topics below.

What to inspect

Who grades the outputs? Inspect the rubric, disagreements, and whether the evaluator sees the method's identity.

Plan a fair comparison

Can you apply the same tasks and rubric to the baseline and candidate, then review disagreements by hand?

Questions for adoption

Are the results stable across prompts, languages, and task categories relevant to your product?

Read the paper with these questions

Inside the paper

Preview the first 3 pages of the original PDF. Click the stack to turn the page.

The downloadable skill includes SKILL.md and evidence.json, with recorded findings and unanswered checks. TRY-IT.md adds a product test plan and a blank results sheet.

A reading aid for your agent. Findings still need validation.

Page 1 of 3
Open this page in the PDF ↗

Provisional research brief updated 2026-10-18. Paperraft has not reproduced this experiment.

Discuss this paper

Question a claim, compare interpretations, or share what happened when you tried the method.

Join the conversation on GitHub. Use this paper's arXiv ID in the title when starting a discussion.

arXiv 2610.12569

Comments are public and separate from Paperraft's research brief. When sharing a result, include the model, hardware, baseline and a link to your work.