Benchmark archive

Reports

Long-form, dated analysis of Claude benchmark claims. Each report separates model, harness, effort setting, cost, source provenance, and what the score can actually prove.

Citable baseline

Report index facts

Dated facts with primary-source links where the underlying source is available.

6Long-form benchmark reports in the July 2026 baseline.
3Free client-side tools linked from the report archive.
T4Network treatment: llms files, JSON-LD, source callouts, and cite-this-page blocks.

Coding

Claude vs GPT Coding

A source-first comparison of Claude and GPT coding benchmark claims, with SWE-Bench Pro, Terminal-Bench, model availability, and effort settings separated.

Updated 2026-07-06 / 9 min

Methodology

SWE-Bench Pro vs Verified

A methodology report on SWE-Bench Verified, SWE-Bench Pro, contamination risk, resolve-rate metrics, and how Claude benchmark readers should interpret both.

Updated 2026-07-06 / 8 min

Agentic Coding

Terminal-Bench Agents

A report on Terminal-Bench 2.0, command-line agent evaluation, Claude and GPT leaderboard readings, and why model-only conclusions are risky.

Updated 2026-07-06 / 8 min

Cost

Cost and Context

A practical report on Claude and GPT pricing, context windows, output limits, effort controls, and why cost-per-answer is not the same as input-token price.

Updated 2026-07-06 / 8 min

Reasoning

Reasoning and Science

A report on academic reasoning, professional work, science-oriented benchmarks, and the limits of translating lab scores into operational Claude decisions.

Updated 2026-07-06 / 7 min

Multimodal

Documents and Vision

A report on multimodal benchmark claims, document workflows, OSWorld-style computer use, and what Claude and GPT comparisons miss when they focus only on text answers.

Updated 2026-07-06 / 7 min

Keep reading

Related tools and methods

Internal links are selected to keep benchmark, tool, and methodology context together.

Tool

Model comparison

Filter Claude, GPT, and benchmark-reference models by provider, access, price, context window, and published coding benchmark evidence.

Report

Claude vs GPT Coding

Use SWE-Bench Pro for contamination-aware software repair, Terminal-Bench for command-line agent behavior, and provider launch tables only when you preserve the harness and effort settings.

Report

SWE-Bench Pro vs Verified

Use Verified for continuity and Pro for current frontier signal; when scores conflict, inspect dataset, scaffold, cost caps, and whether the result is model-only or agent-plus-model.

Source

Primary-source index

Inspect the Anthropic, OpenAI, benchmark-owner, and research sources behind the baseline.