RankingEffort benchmarks

Claude Opus 5.5

Compare models

1 measured results · 1 effort settings · 1 benchmark/harness combinations

Change model

Compare with

Choose a second model and its effort to see both profiles and benchmark differences below.

Compare with

Capability profile

One configuration, seven capabilities

Comparison score · 0–100
Claude Opus 5.5 · Max capability radarComparison scores from 0 to 100. Unknown capabilities have no point; lines stop at gaps. Hollow points are preliminary. Exact values and support labels follow the chart.AgenticHard reasoningCodingHuman prefKnowledgeMultimodalLong context50100

Gaps are unknown, not zero. Hollow points are preliminary.

  • Agentic

    Unknown
  • Hard reasoning

    Unknown
  • Coding

    Unknown
  • Human pref

    Unknown
  • Knowledge

    Unknown
  • Multimodal

    Unknown
  • Long context

    Unknown

Each profile belongs to the named configuration. Capability scores use a shared panel for all axes, distinct from the overall ranking panel; they are not accuracy percentages or direct head-to-head wins.

Capability score evidence

Claude Opus 5.5 · Max: No connected estimate. No admitted path to the complete configuration reference panel

Which sources carry the weight?

    These shares describe the comparisons entering the fit, not fractions of the final score. Source balancing does not prove independence: overlapping sources may remain correlated.

    This configuration did not qualify for the dated stability audit.

    What evidence is missing from the fit?

    Across all collected settings for this model: 45 observations, 0 contributing, 0 matched without graph weight and 45 excluded. Counts do not establish rank eligibility.

    • 1 · Evaluator has not been reviewed for independent admission
    • 44 · Provider-published lab self-report. Shown as a labeled claim and not admitted as a matched board comparison.
    Inspect every observation and exclusion →

    Benchmark results

    These are published benchmark scores. Supported effort estimates also appear on the Capability leaderboard. Results from different harnesses occupy different rows. Missing cells stay unknown; no scores are copied between effort levels.

    Benchmark / sourceMax
    Bug Hunt BenchBug Hunt Bench · Native agentic CLI per row, blind judge against a withheld key. The CLI is named in each configuration.
    Benchmark details

    105 planted bugs across two production repositories (45 and 60). Score is (fixed / 105) * 100, counting planted bugs fixed only. Primary rows are featured and not superseded. Display only pending comparability review. Many rows are single runs.

    Unit: percent. Source collected 2026-09-22.

    40.95%
    Reported settings

    Opus 5.5; Claude Code; effort max (first_party); source ceiling. Single run; fixed 43 of 105 planted bugs. partial 3; claimed_only 3; extras 9; evaluation 2026-09-22. Score is (fixed / 105) * 100. Extras, partials and claimed-only are not scored. Source caveat: ONE RUN, not a mean - and this board has already measured a 13-point spread between two runs of one identical max-effort configuration, so treat 43 as a single draw, not a settled level. Runs a 1M context window with zero compactions; [source caveat truncated].

    What these comparisons mean

    Each source reports its own effort labels. Matching labels do not establish equal compute budgets or identical fallback behavior. Open Reported settings to inspect the exact model name, agent and task coverage. Multiple results at one level remain visible rather than selecting the best. Source-reported None or Non-reasoning labels are not treated as evidence that an API supports those settings.

    These measurements use their own dated source collection. The leaderboard fits identified configurations jointly; it contains no pooled model ratings. Explicit thinking budgets are separate configurations. Read the methodology.

    Download all effort benchmark results · 7,531 results across 242 models · Collected 2026-09-22