DreamX Team
Paper · Project website · Results · Get started
LoopArena evaluates models as runtime Controllers of a separate coding Worker. The Controller reviews progress, assigns the next step, requests verification, and decides when to stop. Type II/III compare Controller models with a shared Worker, Reporter, task, budget, and source-native evaluator.
- October 14, 2026: We expanded LoopArena from 90 to 160 Type I questions and from 27 to 80 paired Type II/III coding tasks. The coding tasks span SCBench, BeyondSWE, and LoopsBench. See the updated leaderboard and setup guide.
- August 28, 2026: The LoopArena paper and open-source benchmark were released.
| Setting | Controller task | Scope | Size | Metric |
|---|---|---|---|---|
| Type I | Choose the best of four complete Loop Contracts | One frozen control point | 160 questions | Contract Accuracy |
| Type II | Guide a Worker through a condensed coding task | One task slice | 80 tasks × 3 repeats | Strict Success Rate |
| Type III | Guide a Worker through a full coding task | Original task state | 80 tasks × 3 repeats | Strict Success Rate |
Type II and III are paired across 21 SCBench, 29 BeyondSWE, and 30 LoopsBench tasks. Type I evaluates one multiple-choice decision without running a Worker. The coding settings retain Controller–Worker interaction and use source-native terminal evaluation. For SCBench, the primary success criterion is Core checks; protocol and budget validity are required for every source.
The Worker changes the repository. A read-only Reporter summarizes observable progress, and the Controller receives an Evidence Packet and returns the next Loop Contract. No-control and fixed-control policies are reported as references; they are not included in the Controller-model ranking. See the protocol for role boundaries, budgets, and scoring.
The main panels evaluate six Controller models. All Type II/III Controller panels use Qwen3.7-Plus as the shared Worker and Reporter. The table shows the primary Core-based score; each coding-task panel has 240 runs.
| Controller | Type I accuracy | Type II SSR | Type III SSR |
|---|---|---|---|
| Qwen3.6-35B-A3B | 43.13% | 55.83% | 33.75% |
| Qwen3.7-Plus | 60.63% | 56.67% | 34.17% |
| DeepSeek-V4-Flash-0731 | 45.63% | 50.83% | 28.33% |
| GLM 5.2 | 54.38% | 40.42% | 24.17% |
| GPT-5.5 | 61.88% | 56.67% | 36.25% |
| Claude Opus 4.8 | 56.25% | 58.75% | 33.75% |
The interactive leaderboard also shows reference policies and estimated costs. Its aggregate data covers all three settings. Costs are normalized no-cache inference estimates, not invoices.
Install Python 3.10+ and the model-gateway dependency:
python -m pip install -e '.[gateway]'Configure an OpenAI-compatible endpoint using .env.example
or environment variables. Model IDs are supplied explicitly:
export OPENAI_API_KEY=YOUR_API_KEY
export OPENAI_BASE_URL=YOUR_BASE_URL
looparena-type1-run --data benchmarks/type1/questions \
--model MODEL_ID --preflight-only
looparena-type1-run --data benchmarks/type1/questions \
--model MODEL_ID --output runs/type1-smoke.jsonl --limit 1Type II/III require the pinned upstream task data, starting workspaces, and Docker runtimes. Follow data preparation and execution for source revisions, local paths, preparation commands, and single-case or panel runs. Large upstream repositories and container images are obtained from their original sources.
benchmarks/type1/: 160 questions and scoring format.benchmarks/type2/: 80 condensed coding tasks.benchmarks/type3/: 80 paired full coding tasks.src/looparena/: preparation, execution, and evaluation code.docs/setup.md: installation and resource preparation.docs/protocol.md: experimental protocol.
If you use LoopArena, please cite the paper:
@article{wang2026looparenabenchmarkingmodelsruntime,
title={LoopArena: Benchmarking Models as Runtime Controllers for Loop Engineering},
author={Yi Wang and Haopeng Zhang and Chengxiang Huang and Rui Dai and Kaikui Liu and Piotr Koniusz and Xiangxiang Chu},
journal={arXiv preprint arXiv:2608.28281},
year={2026},
url={https://arxiv.org/abs/2608.28281}
}LoopArena code and documentation are licensed under Apache-2.0. Third-party task material retains its own terms; see third-party notices.


