Score

Score

Average score per attempt row (0–1). Rewards partial credit.

Formula: Mean of all attempt scores across all results rows: SUM(score) / COUNT(*) over the results table.

Ranks models that make consistent partial progress on hard tasks. A model that scores 0.5 on every task beats one that passes half and fails the rest on this metric.

67.82
Tasks pass 52/64
1st: 44 2nd: 8 Failed: 12
Cost / run

Cost / run

Average total LLM cost per benchmark run in USD.

Formula: SUM(cost_usd) / run_count across all runs for this model.

Use to compare operating cost across models with similar pass rates. Does not account for quality. Combine with $/Pass for a cost-efficiency view.

$0.32
Latency p50

Latency p50

Median per-task wall time (LLM call + compile + test), in milliseconds.

Formula: 50th percentile of per-task duration_ms: LLM latency + compile time + test time.

Use p50 for a typical-case latency expectation. Unaffected by outlier slow tasks.

2m 29s
Pass Rate

Pass Rate

Fraction of distinct tasks solved in any attempt across all runs.

Formula: (tasks_passed_attempt_1 + tasks_passed_attempt_2_only) / tasks_attempted_distinct

Primary ranking metric. Compare models here first: it directly measures how often the model delivers working code.

81.3% 95% CI: [70.0–88.9]%
pass^n (strict)

pass^n (strict)

Fraction of tasks the model solved in every single run (strict consistency).

Formula: tasks where ALL runs produced a passing result / tasks_attempted_distinct

Measures reliability under repetition. High pass^n means the model is unlikely to regress on a re-run, important for CI and production use.

67.2%
$/Pass

$/Pass

Total cost divided by number of distinct tasks passed. Lower is better.

Formula: SUM(cost_usd) / tasks_passed_distinct across all runs.

Best single cost-efficiency metric. Penalises expensive models that pass few tasks and rewards cheap models with high pass rates.

$0.3994
Latency p95

Latency p95

95th-percentile per-task wall time. Captures tail latency.

Formula: 95th percentile of per-task duration_ms across all tasks in all runs.

Use p95 to understand worst-case latency. A low p95 means the model rarely stalls, relevant for automated pipelines with timeouts.

2m 58s

Overview

Claude Opus 4.7 has run on 6 occasions, attempting 64 tasks with an average score of 67.82.

Settings

Generation parameters used across this model's runs. "varies" indicates the value differed between runs.

Temperature
varies
Thinking budget
varies
Avg tokens / run
231,602
Consistency
79.7%

History

1.00.0
6 runs · oldest 14h ago · latest 9d ago

Cost

meanp95

Failure modes

  • AL0104 315 Syntax error, '=' expected view all →
  • AL0111 135 Semicolon expected. Add a semicolon (;) to terminate the statement. view all →
  • AL0000 125 App generation failed view all →
  • AL0185 64 Table 'Session Information' is missing view all →
  • AL0107 34 Syntax error, identifier expected. Provide a valid name (letters, digits, and underscores only). view all →
  • AL0134 29 'SessionInformation' is not recognized as a valid type. Verify the type name is correct and the required dependencies are referenced. view all →
  • AL0361 29 Identifier was not properly terminated. Use the character " to terminate the identifier. view all →
  • AL0198 21 Expected one of the application object keywords (table, tableextension, page, pageextension, pagecustomization, profile, profileextension, codeunit, report, reportextension, xmlport, query, controladdin, dotnet, enum, enumextension, interface, permissionset, permissionsetextension, entitlement) view all →
  • AL0118 20 The name 'CreateSequentialGuid' does not exist in the current context. view all →
  • AL0105 18 Syntax error, identifier expected; 'key' is a keyword view all →

Shortcomings

AL concepts Claude Opus 4.7 struggles with. Click a row for description, correct pattern, and observed error codes.

No shortcomings analyzed yet

Shortcomings analysis is on the roadmap. The first analyzer run is scheduled for the P8 release; until then, this section reflects no data.

See methodology

Recent runs

Runs
StartedModelTasksScoreCostDurationStatus
14h ago282/51970.00$3.120mscompleted
17h ago282/51969.83$3.420mscompleted
21h ago282/51971.08$3.470mscompleted
9d ago282/51966.28$3.340mscompleted
9d ago282/51963.65$4.050mscompleted
9d ago282/51966.19$3.360mscompleted

See all 6 runs →

Methodology

Scores are computed per task, averaged across attempts. See the about page for details.