OpenAI says it has made the reasoning of its newest models far harder to steal. In a post on combatting adversarial distillation published on 20 November, the company reports that automated attacks recovering protected chain-of-thought from an earlier request succeeded 54.0% of the time against GPT-6 Astra with its original safeguards, and 0.2% of the time against GPT-6.2 Astra with the updated ones. The change matters beyond OpenAI: the same safeguards now decide what developers can and cannot do with conversation history in the API.
Why reasoning traces are the prize
Distillation means training one model on the outputs of another. Used without permission, it lets a lab copy capabilities without copying the safety rules that came with them. OpenAI’s argument is that the hidden reasoning is the most valuable part, because it contains steps the final answer leaves out.
The company backs this with an internal experiment. It trained the same student model twice on coding and defensive security work from Astra-level teachers: once on what users normally see (answers, reasoning summaries, tool calls) and once on the exact reasoning traces. After fine-tuning, the exact-trace student generally did better on the cyber benchmarks ExploitBench and SEC-bench Pro. After a short round of reinforcement learning the picture was mixed: the exact-trace student led only at the largest inference budget, while the summary-trained one scored higher at lower budgets. OpenAI notes that Anthropic reported a similar advantage for full transcripts on SWE-bench Verified; Anthropic had already described distillation attacks on Claude in February.
The numbers in context: our calculation
OpenAI published two attack types from adaptive black-box red-teaming, aggregated across six attacker models:
- Reasoning from an earlier request: 54.0% success against GPT-6 Astra, 0.2% against GPT-6.2 Astra. That is roughly a 270-fold drop, from about one attack in two to about one in 500.
- Reasoning from the current request: 22.9% against 0.9%, about 25 times lower, but still the weaker of the two defenses.
These are OpenAI’s own red-team figures, run by OpenAI’s own automated attackers. No outside lab has reproduced them, and the post does not publish a separate score for GPT-6.2 Sol even though the protections cover it. OpenAI says selected improvements are now also being applied to GPT-6 Astra.
From reports to OpenAI’s own account
When we covered the distillation fight in October, the story rested on press reports that DeepSeek and Moonshot had harvested GPT-6 Astra reasoning through proxy networks, and none of the companies had confirmed anything. The new post fills in OpenAI’s side. It says it attributed a core part of a September extraction campaign to individuals associated with Moonshot AI, and that its weekly enforcement actions against distillation campaigns have ranged from thousands to tens of thousands of accounts, with the rate rising sharply this past summer. It also says it shares indicators of compromise with other model providers. The post gives no further technical detail on that campaign.
What changes for developers using the API
The part most teams will feel is the API-level protection. With GPT-6.2 Astra and Sol, OpenAI ties a model’s protected reasoning to the exact conversation history that produced it, and older model families can no longer read that reasoning. The OpenAI developer guide on prefix changes spells out the consequence: if you shorten a tool result, rewrite a developer message or replace older turns with your own summary, the API drops the reasoning items that came after the change. The model may then redo that thinking, which costs tokens and latency, and output quality can suffer.
In practice that means three checks for agent builders:
- Compaction: OpenAI’s own compaction endpoint keeps later reasoning; a home-grown summary placed before recent turns does not. The guide suggests putting custom summaries at the end of the context instead.
- Reasoning effort: switching effort mid-conversation should be done by appending a configuration update, not by changing the request-level setting.
- Monitoring: the API reports removed reasoning items and the reason, so teams can see when their own history edits are costing them.
What is still open
OpenAI says it plans to share more about recent campaigns it has disrupted. Still unknown: how the 0.2% figure holds up against human attackers rather than automated ones, how often legitimate requests for explanations get caught by the new classifiers, and whether other labs adopt the same conversation-bound approach. For the broader security angle, our Policy & Safety section tracks how labs are hardening their models.






