AI EVALUATION, IN CONTEXT.BY EQUALITY MACHINE

Claire Radar

GameASG-Bench

A browser-game generation benchmark with 47 tasks. It checks whether a coding agent delivers the requested gameplay, not just valid source code; strict task success and average check rates describe different levels of completion.

Original GameASG-Bench paper v1 and the pinned public implementation. All tables retain the authors’ results and experimental settings; AI Benchmark Radar has not rerun them.

The deliverable: a complete browser game

Each of the 47 tasks asks for one executable index.html, covering 12 genres with 32 2D and 15 3D games. Agents receive target.md, game-spec.md and tdd.md. First-party code must fit inside the HTML; only task-permitted CDN libraries may remain external. The evaluator serves no companion assets.

GameASG-Bench · Task format and execution guide (pinned release)

A test interface tied to real gameplay

The window.__gameTest contract exposes reset, loadScenario, input and getSnapshot. A prepared scenario establishes a legal starting point; a player action must still cause the outcome. The interface must control the visible game itself, rather than a separate state that merely satisfies tests.

GameASG-Bench · Armor Alley public gameplay contract (pinned release)

Evidence layers and requirement priorities

L1 inspects the delivered source. L2 executes the game in Chromium, preparing a scenario, acting and observing the outcome on a fresh page for each check. P0 covers launch and interface prerequisites; P1 covers required gameplay; P2 covers extensions. Layer and priority answer different questions.

GameASG-Bench · Task format and execution guide (pinned release) · GameASG-Bench · Browser check isolation and execution code

Read task success and check rates separately

Strict success requires verified delivery, completed evaluation, every L1 check, and every applicable L2 P0/P1 check; P2 is excluded. Its denominator includes all 47 planned tasks, including failures and missing results. L1 and L2 Mean average task-level rates; priority columns pool applicable checks. NOT_APPLICABLE checks are excluded, including P1 when marked that way.

GameASG-Bench · Strict success, aggregation and cost estimation code · GameASG-Bench · Applicable-check and priority aggregation code

Nine model–harness configurations

All nine configurations complete evaluation on every task at maximum reasoning effort. Each task is attempted once. These are the authors’ observations, with no repeated-run uncertainty estimate.

Paper v1, Table 3 · Task completion and check rates
ModelHarnessStrict success: count/47 (%)L1 %L2 Mean %L2 P0 %L2 P1 %L2 P2 %
GPT-6-AstraCodex CLI26/47 (55.3)98.093.299.092.792.4
Claude-Opus-5Claude Code24/47 (51.1)99.690.491.289.991.1
GPT-5.6-SolCodex CLI21/47 (44.7)98.991.3100.089.791.9
DeepSeek-V4-FlashClaude Code18/47 (38.3)99.489.398.086.790.2
DeepSeek-V4-ProClaude Code15/47 (31.9)99.685.285.383.988.9
Kimi-K3Claude Code15/47 (31.9)97.788.598.086.389.7
GLM-5.2Claude Code11/47 (23.4)98.884.691.283.383.0
Hunyuan-3Claude Code10/47 (21.3)98.381.796.178.282.3
MiniMax-M3Claude Code7/47 (14.9)98.370.691.264.575.4

Parentheses contain percentages. A high mean check rate does not imply that a task passed every required check. Original model names, values and precision are retained; these are not reruns by this site.

GameASG-Bench paper v1 · Experimental settings and Tables 3–9 · GameASG-Bench · Strict success, aggregation and cost estimation code

Artifact size and resource use

Resource means use available measurements; missing entries are excluded rather than treated as zero. Input tokens combine input, cache reads and cache writes. Monetary values are estimates from the report script’s fixed rates, excluding request-specific surcharges and tool fees.

Paper v1, Table 4 · Mean artifact size and reported resources
ModelHarnessArtifact KBInput tokens kOutput tokens kEstimated cost USD
GPT-6-AstraCodex CLI78.82896.155.54.4445
Claude-Opus-5Claude Code68.5212,632.6142.411.8500
GPT-5.6-SolCodex CLI64.671,382.545.71.7867
DeepSeek-V4-FlashClaude Code85.2113,038.4203.60.2461
DeepSeek-V4-ProClaude Code90.3412,944.3202.90.7431
Kimi-K3Claude Code57.511,263.972.32.5518
GLM-5.2Claude Code60.331,067.147.00.6184
Hunyuan-3Claude Code52.882,474.588.90.1779
MiniMax-M3Claude Code81.764,918.971.10.4069

Artifact sizes cover all 47 tasks per configuration. k = 1,000 tokens; KB = 1,024 bytes. These historical cost estimates are not current provider prices, and different accounting conventions limit efficiency comparisons.

GameASG-Bench paper v1 · Experimental settings and Tables 3–9 · GameASG-Bench · Strict success, aggregation and cost estimation code

Tool access changes the workflow

DeepSeek-V4-Flash is tested at maximum reasoning effort. The full-tool baseline uses Claude Code and a nominal 120-turn budget; the no-tool condition instead sends serialized API input. Syntax-only access permits node --check, without a browser.

Paper v1, Table 5 · DeepSeek-V4-Flash tool configurations
Tool settingStrict success: count/47 (%)L1 %L2 P0 %L2 P1 %L2 P2 %
No tools (serialized API)7/47 (14.9)98.583.365.380.1
File read/write only6/47 (12.8)98.887.366.273.4
Files + syntax checking9/47 (19.1)98.286.363.469.3
Full tool access18/47 (38.3)99.498.086.790.2

Every condition completes evaluation on 47 tasks. No tools = serialized API; file-only = read/write; syntax = files plus syntax checking; full = full tool access. The no-tool comparison also changes input delivery, so it does not isolate one tool alone.

GameASG-Bench paper v1 · Experimental settings and Tables 3–9

The denominator matters when runs stop early

This comparison fixes DeepSeek-V4-Flash, Claude Code, full tools and maximum reasoning effort. The conditional success column describes only tasks that reach evaluation; the all-planned column measures delivery across the full benchmark.

Paper v1, Table 6 · Nominal turn budgets
TurnsEvaluated / plannedSuccess / all planned (%)Success / evaluated (%)L1 %L2 P0 %L2 P1 %L2 P2 %
3010/477/47 (14.9)7/10 (70.0)100.0100.094.097.6
6032/4713/47 (27.7)13/32 (40.6)99.788.681.688.5
12047/4718/47 (38.3)18/47 (38.3)99.498.086.790.2

The 30-turn result of 70.0% is 7 successes among 10 evaluated tasks; the primary result is 7/47 (14.9%). Check rates also describe the evaluated subset. Do not compare conditional rates as if all runs had completed.

GameASG-Bench paper v1 · Experimental settings and Tables 3–9 · GameASG-Bench · Strict success, aggregation and cost estimation code

Reasoning settings and token use

The authors vary reasoning effort while keeping DeepSeek-V4-Flash, Claude Code, full tools and the nominal 120-turn setting. Read the task-success and token columns together.

Paper v1, Table 7 · Reasoning-effort comparison
EffortStrict success: count/47 (%)L1 %L2 P0 %L2 P1 %L2 P2 %Mean reasoning tokens
Low7/47 (14.9)98.393.171.780.237,699
High19/47 (40.4)99.497.182.788.9138,232
Max18/47 (38.3)99.498.086.790.2189,210

Low, High and Max are the reported settings. Reasoning tokens are per-task means. The observed difference between High and Max comes from single runs; it is not evidence of a stable superiority across repetitions.

GameASG-Bench paper v1 · Experimental settings and Tables 3–9

Equal totals can hide different failures

With DeepSeek-V4-Flash, maximum effort and full tools, the two harnesses produce the same success count. Only 10 tasks succeed in both: each harness uniquely succeeds on 8, and neither succeeds on 21.

Paper v1, Table 8 · Harness comparison
HarnessStrict success: count/47 (%)L1 %L2 P0 %L2 P1 %L2 P2 %
Claude Code18/47 (38.3)99.498.086.790.2
Codex CLI18/47 (38.3)99.296.187.192.2

This compares complete harness configurations on the same 47 tasks. Equal strict-success totals do not imply identical artifacts or failure patterns.

GameASG-Bench paper v1 · Experimental settings and Tables 3–9

What the failure traces reveal

Table 9 describes two interaction defects. GPT-6-Astra/Codex CLI’s Diner Dasher passes L1 and P0/P2 but real mouse/touch drags fail to advance service. DeepSeek-V4-Flash/Claude Code’s Turbo Smash Beast stops natural-time simulation after reset or scenario loading, breaking acceleration and coasting checks.

GameASG-Bench paper v1 · Experimental settings and Tables 3–9

What passing can establish

Passing supports compliance with the published requirements under these checks. It does not certify enjoyment, visual quality or production readiness. The test code is public; standard generation containers omit it. NOT_APPLICABLE exclusions and model–harness differences should remain visible when interpreting a comparison.

GameASG-Bench · Task format and execution guide (pinned release) · GameASG-Bench · Applicable-check and priority aggregation code · GameASG-Bench · Armor Alley public gameplay contract (pinned release)

Record the full experiment setup

Pin the repository revision, model, harness, reasoning setting, tool permissions and budget. The runtime pins Claude Code 2.1.206 and Codex CLI 0.153.4. Defaults allow one generation attempt, 3,600 seconds and 120 Claude Code turns. Use a fresh experiment ID; an existing HTML can be re-evaluated. README examples use different defaults from some paper rows and are not exact reproductions.

GameASG-Bench · Pinned runtime image · GameASG-Bench · Generation budgets and container setup · GameASG-Bench · Task format and execution guide (pinned release)

Evidence available for this benchmark

The guide reproduces the paper's result tables with their separate tasks and metrics; these tables have not been added to normalized score data.

Start with these resources

Cited documents and dates (1)

Catalog collected on 2026-10-14; resources and fields reflect that saved source.

Recorded attention

Observed on: 2026-10-11

GitHub stars
10
Hugging Face paper upvotes
1

areal-project/gameasg-bench · View source snapshot

Dated attention observations, not live counts or benchmark scores.

Evaluation context and evidence

Source
Claire Radar
Publisher
Not recorded
Benchmark release
2026-09-18
Collected
2026-10-14
Modality
Not recorded

These are source-reported observations, not independent reruns by this site. Check the task version, evaluation protocol, unit and reporting date before comparing models. Results from different setups are not a universal ranking.

Paper results 6

The guide above contains the paper's tables, retaining tasks, units, denominators and citations.