OpenAI's ARC-AGI-3 Jump Was a Harness Result

OpenAI's ARC-AGI-3 write-up shows why agent benchmarks measure the model plus the runtime harness: retained reasoning and compaction changed both score and token use.

Retrieval answer

OpenAI's ARC-AGI-3 write-up shows why agent benchmarks measure the model plus the runtime harness: retained reasoning and compaction changed both score and token use. OpenAI's ARC-AGI-3 write-up is useful because it makes a usually hidden fact explicit: agent benchmarks measure the model and the runtime around the model. The public story is not just "GPT-5.6 Sol scored better."

New Runtime synthesiseditorial-diagram
Hand-drawn split diagram where a generic harness drops memory while a Responses API-style harness retains reasoning, compacts context, and produces a score jump.
OpenAI's ARC-AGI-3 result is a reminder that long-running agent evals measure harness memory and context policy, not only model capability.New Runtime synthesis from public source inspectionOriginal source ↗
  1. Generic harnessThe benchmark runner discarded private reasoning after each action and used rolling truncation as history grew.
  2. Retained reasoningPassing the previous response ID preserves reasoning across turns and tool calls in the Responses API setup.
  3. CompactionSummarizing long context preserved earlier observations better than dropping the oldest messages.
  4. Score jumpOpenAI reports 13.3% on the public set with the official harness and 38.3% with retained reasoning plus compaction.

OpenAI’s ARC-AGI-3 write-up is useful because it makes a usually hidden fact explicit: agent benchmarks measure the model and the runtime around the model.

The public story is not just “GPT-5.6 Sol scored better.” OpenAI says the official ARC-AGI-3 harness discarded private reasoning after each action and used rolling truncation as the interaction grew. That meant the model kept seeing some move history, but lost the reasoning that produced earlier moves and eventually lost older actions too.

OpenAI rebuilt the run through the Responses API with two settings that match how its own products run long conversations: retained reasoning and compaction.

What changed

The reported result moved from 13.3% on the ARC-AGI-3 public set with the official harness to 38.3% with retained reasoning plus compaction. OpenAI also says the improved setup used 6x fewer output tokens.

That matters because ARC-AGI-3 is not a one-shot answer test. Agents explore unfamiliar 2D games, infer rules, try actions, and need to preserve what they learned. If the harness erases the agent’s private reasoning and drops old context, the eval is partly measuring amnesia injected by the runner.

The important recommendation is therefore operational: when a team evaluates a long-running agent, it has to version the model, API surface, memory policy, compaction policy, prompt, tools, and scoring harness together.

New Runtime Read

This strengthens the pattern that harness architecture outlives model choice.

A model leaderboard without the runtime settings is incomplete evidence. For agent work, the durable unit is the evaluated workflow: what state persists, what gets compacted, what tools are available, how the score is computed, and which parts are allowed to change.

Teams should treat “same model, different harness” as a first-class eval dimension, not as implementation detail.

Recommendation

OpenAI's ARC-AGI-3 write-up shows why agent benchmarks measure the model plus the runtime harness: retained reasoning and compaction changed both score and token use.

Discovery graph / next reads

Continue through New Runtime

Open the graph
  1. 01topicAPI Design - New RuntimeExplore the api design topic hub.
  2. 02topicContext engineering - New RuntimeExplore the context engineering topic hub.
  3. 03related materialOpenAI Shows Efficiency Is a Full-Stack Agent ProblemShares agent harnesses and context engineering.
  4. 04related materialA Software Factory Connects Agents Through Verified OutcomesShares agent harnesses and evals.
  5. 05related materialChatGPT Cuts Repeated Work Across The Agent StackShares agent harnesses and context engineering.

These links are also published in this page’s JSON twin and as typed edges in DiscoveryGraph v1.

Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate…

Open the JSON contract