Reported in recent model launches

These model reports include this benchmark. Their harnesses, task subsets, scoring policies, and resource budgets can differ; follow each report’s evaluation notes before joining the numbers.

What it measures

Compare app-building outcomes across the original suite and the 1–100 collection, with each task set labeled separately.

How to read the result

Inspect runnable behavior and requirement coverage alongside visual quality; a polished interface can still fail core interactions.

Limits and comparison traps

Pin the project brief, tools, judge, and evaluation release. Preference and functional checks should remain separate when the source reports both.

Published evaluation

The linked publication documents the task and scoring procedure. Model results retain the source’s evaluation setting, native score units and available uncertainty.

Versions and evaluation settings

Consolidate navigation for the Vibe Code Bench family while keeping the original and 1–100 task sets in different measures.

Where this fits in an evaluation suite

The agent wrapper is part of the system. Pin tools, dependencies, timeouts, tests, and the repository revision. Compare contest coding separately from repository maintenance.

Start with a capability hypothesis, then choose a second test with a different failure mode. Keep the checkpoint, reasoning effort, agent tools, sampling policy, and scoring procedure fixed when measuring a training intervention. Record failures and missing outputs in the denominator.

A reproducible comparison

Pin the benchmark release, task split, model configuration, tools, sampling budget, and evaluation harness described by the primary source.

Publish the exact run configuration, item coverage, score units, and available uncertainty. If a source supplies only an aggregate or a single run, preserve that limit. A new model name or a rounded score alone does not establish a capability improvement.

PRIMARY EVIDENCE & FURTHER READING

  1. Vibe Code Bench — evaluation methodology and results ↗

    Vals AI · 2026

  2. Gemini 4 Argon Model Card ↗

    Google DeepMind · 2026

  3. Vibe Code Bench 1-100 — evaluation methodology and results ↗

    Vals AI · 2026

Reviewed 2026-10-26. Explanation and interpretation by RLTasks. Benchmark ownership remains with its original authors.