Benchmark definition

SWE-Explore

ActiveSWE_EXPLORE

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

Compare with others

About

Description: SWE-Explore
What it measures: SWE-Explore
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: Software Engineering
Domains: None recorded
Evaluation style: None recorded

Structure

One undivided item set. No components or scenarios recorded.

Tasks

Repository Exploration And Localization

Metrics

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

Metric	Role	Direction	Unit
Precision Metric code used by canonical Batch-2 benchmark definitions; exact benchmark-specific semantics remain in benchmark_metric parameters/methodology.	Primary	Higher is better	Percent
Recall Metric code used by canonical Batch-2 benchmark definitions; exact benchmark-specific semantics remain in benchmark_metric parameters/methodology.	Secondary	Higher is better	Percent
F1	Secondary	Higher is better	Percent
Ndcg Canonical Batch-2 metric code NDCG; benchmark-specific formula/parameters remain on benchmark_metric and methodology records.	Secondary	Higher is better	Score
Hit File Rate Canonical Batch-2 metric code HIT_FILE_RATE; benchmark-specific formula/parameters remain on benchmark_metric and methodology records.	Secondary	Higher is better	Score
Context Efficiency Canonical Batch-2 metric code CONTEXT_EFFICIENCY; benchmark-specific formula/parameters remain on benchmark_metric and methodology records.	Secondary	Higher is better	Score

Methodology

None recorded

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

No required conditions recorded. Every model is Not recorded for this benchmark.

Relevant · informational

Complex reasoning

CTXDEX models

Not recorded58 of 58

This benchmark records no required conditions. Without requirements, no model can be shown to meet them, so every model is Not recorded. This is correct, not missing data.

Scale

848
Issues
Total · Exact
10
Language
Total · Exact
203
Repository
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: FamilySwe Explore
Related: Derived from BenchmarkSWE-bench Multilingual
Derived from BenchmarkSWE-bench Pro
Derived from BenchmarkSWE-bench Verified
Changes: None recorded

Sources

None recorded

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.