Benchmark definition

Ag-LiveCodeBench-X

ActiveAG_LIVECODEBENCH_X

Applicability does not mean evaluated; benchmark result/model score data is outside this UI contract.

Compare with others

About

Description: Ag-LiveCodeBench-X
What it measures: Ag-LiveCodeBench-X
Comparison guidance: Not published
Intended difficulty: Not published

Not recorded for this benchmark: what it does not measure, why it matters, motivation, gap addressed.

Classification

Categories: Code generationMultilingual
Domains: Computer science
Evaluation style: None recorded

Structure

One undivided item set. No components or scenarios recorded.

Tasks

None recorded

Metrics

What a result on this benchmark would be reported as. ctxdex does not carry results.

Metric	Role	Direction	Unit
Pass@k Probability/estimate that at least one of k generated solutions passes the benchmark correctness tests.	Primary	Higher is better	Percent

Methodology

Canonical methodology noteThis definition

Target programming language is a methodology parameter rather than a fixed set of benchmark-language components.

Source lane: L1

Canonical methodology noteThis definition

Verifier container/runtime is evaluator-provided.

Source lane: L1

Evaluation environment

What the benchmark's harness provides and allows. These are properties of the environment, not model requirements, and applicability does not test for them.

Interaction: None. Static prompts and answers.
Evaluation style: Not recorded
Environment summary: Not published

Model requirements

Required conditions decide applicability. Relevant ones describe what the benchmark exercises and decide nothing.

Required · decides applicability

Whole benchmark

Text (input)Text (output)Code generationSource code (output)

Relevant · informational

Coding models

CTXDEX models

3 of the 58 active, preview, experimental models meet this benchmark’s recorded requirements, at some scope. Applicable means the requirements are met, not that the model was evaluated.

View all 3 applicable models →

Applicable · full: 3
Applicable · components: 0
Applicable · scenarios: 0
Conditionally applicable: 0
Not recorded: 55

Counted over 58 models in the default lifecycle scope (active, preview, experimental).

Every required condition, for the whole benchmark, is recorded as supported. Each line is one recorded condition and why it counts.

Ctxdex Builder 1
Ctxdex Builder
Full benchmark
Every one of the 4 required conditions is recorded as supported.
- MODALITY:INPUT:TEXTthe catalogue records SUPPORTED for TEXT (input)
- MODALITY:OUTPUT:TEXTthe catalogue records SUPPORTED for TEXT (output)
- IO_REPRESENTATION:OUTPUT:SOURCE_CODEthe catalogue records SUPPORTED for SOURCE_CODE (output)
- MODEL_TASK:CODE_GENERATIONthe catalogue records SUPPORTED for CODE_GENERATION
Ctxdex Code 2
Ctxdex Code
Full benchmark
Every one of the 4 required conditions is recorded as supported.
- MODALITY:INPUT:TEXTthe catalogue records SUPPORTED for TEXT (input)
- MODALITY:OUTPUT:TEXTthe catalogue records SUPPORTED for TEXT (output)
- IO_REPRESENTATION:OUTPUT:SOURCE_CODEthe catalogue records SUPPORTED for SOURCE_CODE (output)
- MODEL_TASK:CODE_GENERATIONthe catalogue records SUPPORTED for CODE_GENERATION

Applicability/relevance ordering only; never a performance ranking.

Scale

499
Problem
Total · Exact

Data and access

UnknownDataset, evaluation code, leaderboard, peer review and maintenance status are all unrecorded for this benchmark.

Coverage

Languages, regions: None recorded
Coverage summary: Not published

Limitations

None recorded

Lineage

Family: FamilyAgnostics
Related: Derived from BenchmarkLiveCodeBench
Changes: None recorded

Sources

https://arxiv.org/abs/2508.04865 ↗Research paper · Original creator
https://github.com/nuprl/Ag-LiveCodeBench-X ↗Official repository · Benchmark official

Freshness

Content version: B2-1.0
Last reviewed: 2026-09-23
Refresh model: Unknown
Time sensitivity: Unknown
Benchmark data: c40cccac878af5d0

13 contract fields are empty for every benchmark in this release and are not shown: applicability groups, conditional requirements, feature requirements, model relevance domains, required capabilities, openness summary, reference artifacts, interaction protocols, tool protocols, benchmark last major refresh at, short name, target expertise level, target population.