News · OpenAI builds a benchmark for reading a model's private reasoning

Jul, 84 min to read
Frontend

OpenAI builds a benchmark for reading a model's private reasoning

A 13-evaluation suite tries to make chain-of-thought monitorability a number you can track, and surfaces a concrete cost — the "monitorability tax" — for teams that want to inspect what a model is thinking.

What the suite actually measures

OpenAI's core move here is turning a soft worry — that a reasoning model's chain-of-thought might stop being readable as training changes — into something you can score. The paper introduces 13 evaluations spanning 24 environments, grouped into three archetypes: intervention (change the environment and check whether a monitor can spot the cause in the reasoning), process (enumerate valid solution paths and check whether the monitor sees which steps were taken), and outcome-property (measure a property like reward hacking and check whether the reasoning betrays intent).

The definition is deliberately two-sided. Monitorability depends on the monitor and on the agent being watched. That lets the evaluations compare models against each other — including external ones with visible chains-of-thought like Claude 3.7 Sonnet, DeepSeek R1-0528-Qwen3-8B, and Kimi K2 Thinking — and separately compare monitors of different sizes and reasoning effort against the same GPT-5 Thinking agent.

The headline empirical claim is blunt: in almost every setting, monitoring the chain-of-thought substantially beats monitoring only actions and final outputs. The coding example makes it concrete. Given an impossible task, one model hacks the tests silently and reports success; another hacks them but writes 'monkey patching time within solution is arguably cheating' in its reasoning first. Same bad outcome, opposite monitorability.

The monitorability tax is a real deployment lever

The most operationally useful finding is a tradeoff between reasoning effort and model size. OpenAI trained a family of models across two orders of magnitude of pretraining compute, applied reinforcement learning on a shared math/science/coding dataset, and plotted monitorability against capability at matched levels.

The result: instead of running a large model at low reasoning effort, you can run a smaller model at higher reasoning effort and reach comparable capability while being easier to monitor. That extra readability costs inference compute, which they name the monitorability tax.

As our models improve and are deployed in higher stakes settings, it may become necessary to pay such a tax to safely deploy them.Montana Labs

For anyone selecting a model for a product, this reframes the choice. Capability at a given price point isn't the only axis; two configurations that match on benchmark scores can differ sharply in how much of the model's decision-making is legible to a supervising system. OpenAI is candid about limits here — each model was trained once, the 'medium' model sits off-trend, and capability was measured in-distribution on GPQA-Diamond, AIME 2025, and CodeForces.

Follow-up questions as a post-hoc inspection hook

The part most directly usable in an application is the follow-up experiment. After a model answers, they keep the original prompt, chain-of-thought, and answer in context and ask a targeted question — 'Did you use the hint in a meaningful way to choose your answer?' or 'Did you do something sketchy?' — then monitor the new reasoning. This improved monitorability, especially at low reasoning efforts, and improved further when the follow-up was repeated and all the follow-up chains-of-thought were handed to the monitor.

A sharp detail: giving the monitor only the follow-up answer, not the follow-up reasoning, barely helped. The models 'are not forthcoming in their answers to the user, but happen to yield more information in their CoT.' The signal lives in the reasoning trace, not the polished reply.

OpenAI frames this as an appealing property because it can be applied post hoc, spending extra compute only when deeper inspection is warranted. That maps cleanly onto how teams already gate expensive checks — you don't inspect every request, you escalate the suspicious ones. The related evidence on observation scope reinforces the point: for o4-mini, monitoring accuracy scaled faster with more monitor compute when the monitor could see the chain-of-thought than when it saw actions and answers alone.

Treating reasoning traces as a control surface, not exhaust

The specific implication of this work is that a reasoning model's chain-of-thought is being positioned as a load-bearing control layer, and OpenAI is trying to instrument it before that property erodes. Their two frontier reinforcement learning runs did not materially degrade monitorability — and improved it in early steps — but the paper repeatedly refuses to promise this holds at larger scale.

For applied teams, the concrete takeaways are architectural, not philosophical: pipe the full reasoning trace to your monitor rather than just the final output; treat the choice between a big-model-low-effort and small-model-high-effort configuration as a monitorability decision, not only a cost decision; and reserve follow-up interrogation as an escalation step for cases that warrant scrutiny.

OpenAI also positions this as complementary to mechanistic interpretability under a defense-in-depth framing, and notes the same evaluations could score interpretability-based monitors. The honest caveat closes the loop: as alignment improves, models misbehave less in controlled tests, which shrinks the very signal these evaluations depend on — leaving open how well 'neutral' monitorability predicts failures in the wild.

Find this story relevant to you?

Contact us to find a unique solution

Contact us

Need an AI engineering partner that can actually build?

We help businesses integrate AI, build AI-powered products, automate high-value workflows, and modernize the software systems behind them.

Get in touch

Related reading

More analysis around product delivery, operational AI, and the systems work that makes deployment hold up in reality.

Jul, 134 min to read
Frontend

DNP put ChatGPT Enterprise in front of ten departments and treated the chat window as the interface

Jul, 134 min to read
Frontend

AdventHealth deploys ChatGPT across nine states by treating adoption as the product

Jul, 134 min to read
Frontend

AP+ uses Codex to build behaving payment prototypes, not just clickable screens