WeSearch

WebGameBench: Requirement-to-Application Evaluation for Coding Agents via Browser-Native Games

·3 min read · 0 reactions · 0 comments · 32 views
#artificial intelligence#game development#benchmarking
WebGameBench: Requirement-to-Application Evaluation for Coding Agents via Browser-Native Games
TL;DR · WeSearch summary

WebGameBench is a new benchmark designed to evaluate coding agents' ability to create browser-native games from structured specifications. The benchmark assesses the usability of the generated games through a runtime evaluator that interacts with the applications in real browsers. Initial results indicate that while some coding agents can produce playable games, there remains a significant gap in achieving high-quality outputs.

Key facts
About this source

arXiv cs.AI files mainly under ai research. We currently carry 1,128 of its stories.

Original article
arXiv cs.AI
Read full at arXiv cs.AI →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherarXiv cs.AI
Canonical URLhttps://arxiv.org/abs/2605.17637
Publication timeTue, 19 May 2026 00:00:00 -0400
Retrieval time2026-05-19T04:04:57.272Z
Last seen2026-05-19T04:04:57.272Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterjUV8jTjvVbmQ
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Computer Science > Artificial Intelligence arXiv:2605.17637 (cs) [Submitted on 17 May 2026] Title:WebGameBench: Requirement-to-Application Evaluation for Coding Agents via Browser-Native Games Authors:Wenyu Zhang, Guoliang You, Tianlun, Haotian Zhao, Tianshu Zhu, Haoran Wang, Xiaoxuan Tang, Mingyang Dai, Jingnan Gu, Daxiang Dong, Jianmin Wu View a PDF of the paper titled WebGameBench: Requirement-to-Application Evaluation for Coding Agents via Browser-Native Games, by Wenyu Zhang and 10 other authors View PDF HTML (experimental) Abstract:Coding agents are increasingly used as application builders, yet many evaluations still focus on source code, repository-level tests, or intermediate traces rather than the delivered application.

Excerpt limited to ~120 words for fair-use compliance. The full article is at arXiv cs.AI.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from arXiv cs.AI