Security & CyberISSUE #6 · STORY 12 OF 20Oct 12, 2026EARLY RESEARCH
Anthropic says anti-distillation defences cut attackers' haul by roughly 90-99%
On 12 October 2026 Anthropic published defences against illicit model distillation, claiming the data distillers harvested fell by around 90-99%, and shipped 'preserved thinking', which binds a model's reasoning to a model, a prefix and sometimes an account. The figure is self-measured on Anthropic's platform with no independent audit, and the control is now a breaking change for some API integrations.
Read it your way
CHAPTER 1Picked for Explorer
The 60-second version
On 12 October 2026 Anthropic published a post on defending against distillation attacks, saying the amount distillers harvested dropped by roughly 90-99%. It described three production defence layers and conceded real trade-offs, including forced integration updates and billing for blocked requests.
Self-measured headline claimThe 90-99% reduction is Anthropic's own platform-side measurement, and no independent audit was found.
Three defence layersStructural binding of reasoning, a two-stage extraction classifier, and friction that meters repeated probing.
A breaking API changePreserved thinking binds reasoning to a model, a prefix and sometimes an account, so some integrations must change.
Trade-offs concededAnthropic says it refused paying traffic, forced developer updates and bills blocked requests below a 0.1% error rate.
Finish this chapter for +15 XP
Flip the switch
Extraction economics, before and after the defences
Probing costMeteredSince 24 September 2026, requests blocked by safeguards can be billed to the caller.
Reasoning portabilityBound and droppedBlocks are readable only by bound models and are dropped if the prefix has changed.
Defence styleClassify and bindA two-stage classifier plus model and account binding now guard the reasoning trace.
Your next move · Explorer
Check whether your agent edits the prefix
1Send the thinking-binding-controls-2026-08-01 header and count prefix_binding_mismatch entries in input_transformations.
2Replay a normal multi-turn session that includes a context compaction or a tool change and see what breaks.
3Compare behaviour on an older API key against a newly created one to expose the two-tier enforcement gap.
Switch your reading mode at the top to see a different next move.
Tap to open
Things to keep an eye on
Pop quiz · unlock the Distillation Defense badge
Did it stick?
0/3
What did Anthropic actually claim on 12 October 2026?+20 XP
What does 'preserved thinking' do to a reasoning block?+20 XP
Why should the 90-99% figure be treated as a company claim?+20 XP
Your call · +5 XP
Anthropic's anti-distillation control also hides more reasoning from auditors. Which trade-off should it prioritise?
Research dossierThe full research, labeled and sourcedEARLY RESEARCH20 sources · 25 min read · 20 sectionsOpenClose
Story identity
Field
Value
Story ID
S12
Organisation
Anthropic
Category
AI Safety Research
Event date
2026-10-12
Evidence status
EARLY RESEARCH
Evidence-status note. This is a lab's own reported operational result, not a peer-reviewed or independently reproduced finding. The headline number is therefore treated throughout this document as a COMPANY CLAIM, not as FACT or INDEPENDENTLY VERIFIED. Where the existence and content of the publication is concerned, that is a FACT. Where the effect size is concerned, that is a CLAIM. An independent write-up explicitly states it found no independent audit of the 90–99% reduction, the 10×–100× token drop, or the classifier's false-positive rate.
✓
What happened?
🎓 For Explorer
FACT. On 2026-10-12 Anthropic published a research blog post titled "Strengthening our defenses against distillation attacks" at https://www.anthropic.com/research/distillation-defenses. The post:
Describes illicit distillation as "covert, industrial-scale campaigns to extract the capabilities of one model and replicate them in another, without the authorization of the original model's developers", typically conducted "using networks of fraudulent accounts".
States a headline result: "Early evidence suggests that these methods have reduced the amount of data harvested by distillers by around 90 to 99%."
Gives the underlying measurement in a different unit: the volume of Claude reasoning tokens extracted by distillers "is consistently 10 to 100 times lower than it was before".
Describes three defence layers now in production (Section 5).
Names two adverse actors as worked examples: Zhipu (GLM-5.3, cyber capability) and Moonshot (Kimi, request relaying).
Concedes trade-offs: turned-away revenue, "trillions of tokens' worth of paying traffic" refused, developers forced to update integrations, a classifier that misidentifies benign requests in fewer than 0.1% of cases, and billing for blocked requests.
Concedes uncertainty: "We don't yet know how long these gains will last… we have yet to see a highly sophisticated and persistent attempt to circumvent them."
FACT. The post is the fourth in a series of Anthropic distillation disclosures (February 2026, then a September 2026 threat-intelligence report, now this defence-side post).
COMPANY CLAIM. The 90–99% reduction, the 10×–100× token reduction, the sub-0.1% false-positive rate, the "roughly as robust as those that prevent Claude from helping build bioweapons" comparison, and the "tens of thousands" of accounts banned (often "less than two hours" after a campaign begins).
INDEPENDENT EVIDENCE (weak form). Multiple independent outlets covered the post within a day — Cryptobriefing, a Reuters wire item, Resultsense, explainx.ai, aiweekly, superpowerdaily, finance.biggo, dealroom. This corroborates that Anthropic published this and said this. It does not corroborate the effect size.
INDEPENDENT EVIDENCE (negative). explainx.ai states plainly that it "found no independent audit of the 90 to 99 percent reduction, the 10x to 100x drop in extracted reasoning tokens, or the false positive rate, and Anthropic does not publish its methodology for measuring attempts it never sees."
Δ
What changed?
Three distinct things changed, and they should not be conflated.
Layer
What changed
To whom
Evidence label
Discourse
Anthropic moved from detecting and attributing distillation (Feb + Sept 2026) to publishing working defences and their measured effect
Public, policy, competitors
FACT
Product / API
"Preserved thinking" now binds reasoning blocks to a model, a prefix and (on some models) an account; the API rejects or drops blocks whose prefix has been edited
Developers building multi-turn agents on the Claude API
FACT (documented API behaviour)
Operational
A two-stage extraction classifier in front of the most capable Claude models; stricter limits, mass bans, and billing for requests blocked before inference
All Claude API users, including legitimate ones
COMPANY CLAIM for the effect; FACT for the documented billing/enforcement change
The most consequential change for a developer audience is the third-order one: an anti-abuse control on reasoning has become a breaking change in how multi-turn context is assembled. That is new. Earlier anti-distillation work (summarising reasoning before display) was invisible to integrations. Preserved thinking is not.
↔
Before → Change → After
🎓 For Explorer
Before (roughly February – September 2026)
**FACT / COMPANY CLAIM.** Anthropic had disclosed large-scale illicit distillation: a February 2026 post describing campaigns of more than 16 million exchanges using around 24,000 fraudulent accounts (including one network with more than 20,000 accounts at once); a September 2026 threat-intelligence report attributing "nearly 200 million" distillation-related exchanges to five campaigns, the largest linked to Alibaba's Qwen with more than 151 million exchanges between May and July 2026, peaking at nearly 3 million per day across about 3,500 accounts.
**COMPANY CLAIM.** Early defences were "simple": Claude summarised its reasoning before display. Attackers responded with *active* extraction — asking Claude to output prior reasoning verbatim, laundering it through translation, replaying thinking signatures across sessions — and scaled through proxy networks.
**FACT.** Reasoning blocks could previously be replayed across conversations, across models, and across accounts; an attacker with a portable signature had a durable handle on the very artifact the defence existed to withhold.
**FACT.** Blocked requests were not billed, so repeated probing was free to the attacker.
→
After (as of 2026-10-13)
**COMPANY CLAIM.** Distillers extract 10×–100× fewer reasoning tokens; on some days "too small to measure"; the classifier "catches all of the distillation techniques we described in our September report" on the most capable generally available models.
**FACT.** A non-trivial class of existing Claude API integrations must be rewritten to be append-only (prefix-stable), and Anthropic's own docs quantify the cost of not doing so (Section 9).
**INTERPRETATION.** Reasoning traces have become a **governed, provider-rationed resource** rather than a byproduct of inference. This is the shift with the longest half-life.
**PREDICTION.** Expect the effect size to decay, and expect a public dispute over whether the number is measuring defence or measuring attribution capability.
⚙
How it works
Anthropic's post describes three layers, all aimed at the same asset: Claude's reasoning trace, because "a model's general reasoning ability drives its performance on nearly every task" and reasoning teaches a student how an answer was reached, not merely what it was.
Layer 1 — Control where reasoning can go (structural).
Per the platform documentation (https://platform.claude.com/docs/en/build-with-claude/preserved-thinking), preserved thinking works by checking each returned thinking/redacted_thinking block on two axes:
Model binding. "The model can read the block." Each model reads its own blocks and those of a fixed set of other models. Claude Fable 5.1 reads blocks from Opus 5 and (on the Claude API) Opus 5.5; neither Opus 5 nor Opus 5.5 reads Fable 5.1's. Unreadable blocks are dropped silently (or reported as model_binding_mismatch under the beta header).
Prefix binding. "Nothing before the thinking block has changed." The checked prefix is the top-level system prompt, the set of tools, and every message before the block. If the prefix differs from when the block was produced, that block and every later thinking block are invalid; the API returns a 400 invalid_request_error by default, or drops them if thinking.block_binding.prefix_mismatch_behavior is set to "drop_block".
Account binding. On Claude Sonnet 5.5 and Haiku 5.5, thinking blocks are tied to the account that produced them; another account's blocks are dropped.
Enforcement: the prefix check applies to all accounts for the model check, but is enforced by default only for accounts created on or after 2026-08-31 00:00 UTC. Older accounts must opt in via the beta header thinking-binding-controls-2026-08-01. This is precisely the loophole the Anthropic post refers to as "prevents new API accounts… from editing Claude's prior context".
Layer 2 — Block and patch extraction attempts (classifier).
A two-stage classifier detects requests that attempt to extract hidden reasoning, following the architectural pattern of Anthropic's constitutional-classifier work. Anthropic says it was red-teamed internally and externally, vulnerabilities found were fixed, and the design now blocks specific enumerated techniques (asking Claude to translate earlier reasoning into another language; asking it to write reasoning out inside tags).
Layer 3 — Make repetition expensive (friction).
Repeated extractors get stricter limits; persistent extractors get banned; and blocked-before-inference requests are billable. This converts probing from free to metered.
Measurement. Anthropic estimates extracted reasoning tokens on its own platform, before versus after the classifier. A 10× drop is a 90% reduction; a 100× drop is a 99% reduction. The "90–99%" headline is therefore a restatement of the "10 to 100 times lower" platform-side measurement — the same number in two units, not two independent results.
!
Why it matters
🎓 For Explorer
FACT-level. Model distillation is the mechanism by which a well-resourced competitor can approximate frontier capability without the compute, the research organisation, or the safety training budget. It is also the one capability-transfer channel that runs through the victim's own infrastructure.
COMPANY CLAIM. Anthropic's stated dual rationale: (a) distilled models are released "without proportionally robust safeguards", so distilled biology and cyber capability is a misuse risk; (b) distilled capability flows into foreign "military, intelligence, and surveillance systems", making this a national-security matter rather than a terms-of-service matter.
INDEPENDENT EVIDENCE. The framing is no longer Anthropic-only. A joint NSA/CISA/FBI Cybersecurity Advisory (AA26-251A, 2026-09-08) describes China-based industrial-scale distillation, names DeepSeek, Moonshot AI, Alibaba, MiniMax, StepFun and Z.AI, and states that distillation "is not a supplement to these companies' AI model development, but the critical core of it". It follows earlier White House instruments (NSTM-4 on adversarial distillation, April 2026; NSPM-11, June 2026).
INTERPRETATION. The strategic significance is not the percentage. It is that:
Defences are now the product surface. An anti-abuse measure changed API semantics for paying developers. Reasoning access is being rationed.
The economics cut against defending. Anthropic says the quiet part out loud: "Defenses are expensive, and illicit distillers are still paying customers. Against that backdrop, it would be easy for companies to do nothing, or not enough."
The defence is only as good as the weakest link in a multi-provider market. Anthropic says its work "would be undermined if attackers could easily access similarly capable models that lack similarly robust anti-distillation safeguards" — the GLM-5.3 case is offered as exactly that: Zhipu switched away from Claude Fable 5 after finding its cyber safeguards degraded the attacks.
Attribution asymmetries persist. Distillers route across native APIs, cloud platforms and third-party aggregators; a single provider can only see its own slice.
✦
What became possible?
🎓 For Explorer
FACT. A documented, model-agnostic contract for reasoning-trace binding (model binding, prefix binding, account binding) that other providers can copy or interoperate with. Anthropic explicitly frames the post as a template: "We hope this post helps developers and platforms better understand how they can prevent these attacks."
FACT. A measurable operational lever: metering blocked requests turns extraction probing into a cost line for the attacker.
INTERPRETATION. An audit surface for legitimate users: input_transformations (under the beta header) tells an integration which thinking blocks were dropped and why, which converts a previously invisible context-management bug into an observable event.
INTERPRETATION. A testable public claim. For the first time the effect size is stated in a form a third party could in principle falsify — by measuring whether distilled students of Claude stop improving at the previous rate.
PREDICTION. Reasoned that competitors will publish competing anti-distillation designs (OpenAI's September 2026 report on disrupting distillation, including "encrypted reasoning replay", is the obvious parallel), and that "reasoning access policy" becomes a line item in enterprise procurement.
◎
Implications
Technical
Reasoning blocks are now capability-bearing credentialed artifacts. They carry a signature interpreted by the API; a tampered or undecryptable signature always returns a 400 and prefix_mismatch_behavior does not apply. Reasoning is no longer a plain transcript.
Conversation history becomes append-only by contract. Any client-side compaction that rewrites earlier turns (trimming old tool results, re-rendering the first user message, re-encoding images, adding then removing per-turn reminders) invalidates downstream reasoning.
The mitigation has a side effect that mirrors the attack's target. Anthropic's own docs quantify it: with "drop_block", dropping thinking once per session raised output tokens by 2.5% (low effort) to 20.1% (max effort); dropping on every turn raised output tokens by 4.6% (low) to 67.1% (max), because Claude re-creates reasoning it can no longer read. A defence against reasoning theft makes reasoning more expensive to regenerate.
Summarising reasoning is a double-edged control. An independent technical analysis makes the sharp point: the property that makes a reasoning trace worth stealing is the property that makes it worth reading. Devaluing stolen traces also devalues traces for auditors, red-teamers and chain-of-thought monitors. Anthropic quantifies only the attacker side (80.4% → 71.8% on SWE-bench Verified for a model trained on full versus summarised Opus 4.8 transcripts); the oversight side is unquantified.
Classifier brittleness is structural, not incidental. A defence measured against attacks the provider can detect looks strongest on exactly those attacks. Anthropic's "catches all of the distillation techniques we described in our September report" is a statement about known techniques. The post says so, and says it is monitoring for new ones.
Enforcement asymmetry is a migration hazard. Because the prefix check is default-enforced only for accounts created on or after 2026-08-31, a service can pass its own tests on an older key and fail for every new customer. Anthropic's docs state this explicitly and offer the beta header as a way to see what new accounts see.
Developer
Concrete, documented and actionable (all traceable to the preserved-thinking documentation rather than to interpretation):
Audit for prefix edits. If your harness rebuilds the system prompt (injecting a date, a mode flag, re-read project instructions, or attaching an MCP server after turn 1), re-renders the context in the first user message, clears or shortens old tool results, re-encodes old images, client-side compacts while keeping recent turns with their thinking, adds/removes/edits tools, or templates a saved session instead of replaying it — you are affected.
Make history append-only. Keep system and tools fixed for the session; only append to messages; send assistant turns back exactly as returned, thinking blocks included. This discipline also preserves prompt-cache hits — the edits that invalidate thinking are the edits that restart the cache.
Mitigate the failure modes you cannot yet fix. Either set prefix_mismatch_behavior: "drop_block" (stopgap, and it costs output tokens) or remove all thinking/redacted_thinking blocks once and leave them out. Store the choice with the session so restarts are consistent.
Observe, don't guess. Send the thinking-binding-controls-2026-08-01 beta header and count responses whose input_transformations contain a prefix_binding_mismatch entry; alert on them. On the Message Batches API an item that leaves the field unset does not fail where the API enforces the check by default — it silently drops instead, so batch pipelines need explicit handling.
Do not prompt for reasoning dumps. "Output your prior reasoning verbatim", "translate your earlier reasoning", "write your thinking inside tags" are the exact patterns the classifier targets. A legitimate eval or research harness doing this may be flagged, and (below a 0.1% error rate) blocked requests are now billed.
Treat third-party Claude access as supply-chain risk. Anthropic describes proxy networks reselling access with false identities and stolen payment details; accounts are banned in bulk and often within two hours. If a reseller cannot explain its sourcing, your workload can disappear.
Watch model-switch semantics. Reasoning does not survive arbitrary model switches: Fable 5.1/Mythos 5.1 blocks are read by each other (and, on the Claude API, Fable 5.1 reads Opus 5.5), but a move away from Fable 5.1/Mythos 5.1 loses its reasoning for that request — including during a router downgrade or a server-side classifier fallback.
INTERPRETATION. The net developer cost is real but modest for well-behaved integrations (Claude Code, claude.ai, Claude Managed Agents, the Agent SDK, and any append-only custom harness need no change) and potentially sharp for teams that rely on aggressive client-side context compaction.
Enterprise
FACT. Reasoning governance is now an enterprise IT concern, not just a model-vendor concern. A blocked or dropped reasoning block is both a cost and a quality variable in multi-turn agent workloads.
FACT. Blocked requests can be billed. At a sub-0.1% error rate a low-volume shop will never notice; a high-volume pipeline will see a steady trickle, and (interpretation) some of those will be legitimate; those customers have little recourse but to be told the rate is low.
COMPANY CLAIM. Anthropic says safeguards are "roughly as robust as those that prevent Claude from helping build bioweapons" and that legitimate users' impact is minimal.
INTERPRETATION. Two enterprise-relevant asymmetries:
Cost shifting. Some friction from anti-abuse enforcement lands on paying customers — integration rewrites, occasional false positives, billed blocks, and higher output tokens when context is dropped.
Vendor-policy divergence. Enterprises running multi-model architectures will now need to know which provider binds reasoning to prefixes/accounts and which does not, because portability and switching costs differ per provider.
INDEPENDENT EVIDENCE. A UK-focused analysis frames the trade-off as "defensible, but it shifts friction onto paying customers", and notes that for developers "blocked requests are now billed, and integrations that edited model context have had to change".
PREDICTION. Enterprise procurement will begin asking anti-distillation questions alongside the usual safety/security questionnaire ("do you bind reasoning to prefixes and accounts? do you bill blocked requests? what is your documented false-positive rate and how is it measured?"). Auditability of that rate is the weak point: it is currently a vendor figure with no disclosed method.
Strategic
IP economics of frontier models. The post argues explicitly that defence is expensive and the attacker is a paying customer, and publishes a method "to show that there's a workable alternative" — an attempt to make under-defending reputationally costly rather than privately rational.
National-security framing as leverage. Anchoring distillation to biological and cyber misuse, foreign military/intelligence/surveillance integration, and a PLA-affiliated CCTV case ties a technical control to export-control and procurement policy. The supporting government advisory (AA26-251A) makes the same move from the state side.
The weakest-link problem. Anthropic's own admission — that its work is undermined if attackers can switch to a similarly capable model with weaker safeguards, which is exactly what it says Zhipu did when choosing among Claude generations — is an argument for industry-wide minimums. It is also, read cynically, an argument for regulation that raises rivals' costs.
Attribution and enforcement converge. Because the provider can see both the extraction pattern and the payment instrument, anti-distillation enforcement becomes a fraud/identity problem as much as a model-security problem. That means bans, identity verification and bulk-account detection are the load-bearing tools — all of them blunt.
Divergence on disclosure. The government advisory recommends covert response degradation ("avoid informing… users suspected of distillation campaigns"). Anthropic describes a disclosed design (billing blocked requests, documenting preserved thinking, publishing a false-positive rate). The two policies are not the same, and third-party evaluators may end up preferring the disclosed one.
INTERPRETATION. If the effect size holds even partially, it degrades one of the fastest routes by which open-weight challengers closed the capability gap, which is material to the competitive narrative around US versus Chinese frontier models. If it does not hold, it becomes evidence that distillation-accounting has been overstated. Either way the claim is now load-bearing in a policy argument it cannot, on present disclosure, support by itself.
⚠
Risks & limitations
Risks
Risk
Type
Evidence label
False positives silently degrade or block legitimate work (custody/discovery, red-teaming, eval harnesses, translation chains, reasoning-verbatim research)
Product / research harm
COMPANY CLAIM (rate <0.1%) + INTERPRETATION
Billed blocked requests shift cost onto legitimate high-volume users with no appeal mechanism described
Commercial
FACT (billing policy)
Rational under-defence: attackers continue paying; defending costs revenue and engineering
Strategic / systemic
COMPANY CLAIM (Anthropic states it)
Over-claiming: a self-measured 10×–100× platform-side reduction presented as a 90–99% defence against distillation generally
Epistemic / reputational
INTERPRETATION on top of FACT
Reasoning summarisation erodes chain-of-thought monitorability for auditors, red-teamers and researchers
Attribution accuracy: named companies are commercial competitors; counts are single-source and unfalsifiable from outside
Legal / diplomatic
INDEPENDENT EVIDENCE (analysis)
Enforcement asymmetry (older accounts less enforced) creates a two-tier failure surface for downstream users
Engineering
FACT (documented API behaviour)
Arms-race decay: gains may be temporary and are explicitly unproven against a sophisticated persistent adversary
Technical
COMPANY CLAIM (Anthropic concedes it)
Cross-provider leakage: distillers move to models without equivalent controls
Systemic
COMPANY CLAIM + PREDICTION
Escalation to a legal/regulatory dispute over unfounded allegations (China's Foreign Ministry has previously rejected the US advisory as "unfounded accusations and smears")
Geopolitical
INDEPENDENT EVIDENCE (of the rejection), not of the underlying allegations
Limitations
Of the result itself
Self-measurement. Anthropic measures "how many tokens of Claude's reasoning distillers have extracted on our own platform". It cannot measure extraction it did not detect, nor extraction on third-party aggregators and cloud endpoints. A defence measured against detected attacks will always look good against detected attacks.
No disclosed methodology. No sampling frame, no comparison window definition, no confidence interval, no independent replication was found.
One unit, two presentations. The headline 90–99% and the body's 10×–100× are the same measurement. They should not be treated as two converging results.
Time horizon unestablished. Anthropic: "We don't yet know how long these gains will last." No sustained-adversary test has occurred.
Classifier recall is claimed only against known techniques. "Catches all of the distillation techniques we described in our September report" is bounded by the report's inventory; the adversary has demonstrated (12,000-variant technique search; a move to translation laundering; tag-wrapped reasoning) that it iterates.
Of the collateral claims
The bioweapons-robustness analogy is a claim, not a comparison with a published benchmark.
The safety argument for defence rests on unpublished internal research — that a distilled student can help achieve dangerous biological or cyber capabilities even when harvested exchanges contain little about those subjects, and that safeguards do not transfer. As one independent technical analysis notes: no uplift figure, no domain, no student model, no undistilled baseline.
The attribution counts are single-source. Alibaba-linked 151M exchanges, Moonshot 23M, DeepSeek 12.1M, Zhipu 3.4M, Xiaomi 400k, and the ≈200M total are Anthropic's own attributions, published without method. The government advisory corroborates lab names, not counts, and its reference list is the vendors' own disclosures — so co-naming is not two independent witnesses.
Of coverage
Restatement risk. Most of the 2026-10-12/13 coverage is announcement restatement (wire copy, aggregators, vendor-derived blogs). Very little is independent technical evaluation. The most substantive independent piece is an analysis page, not a measurement.
No adverse-party response found. Zhipu, Alibaba, Moonshot and MiniMax have not (in the sources located) responded to this specific post in detail. Absence of denial is not evidence of accuracy, and earlier Chinese government responses were blanket rejections rather than point-by-point rebuttals.
?
Open questions
Does any third party reproduce or falsify the 90–99% reduction? What would a falsification even look like given the measurement is on Anthropic's own platform?
Is there a published measurement of the classifier's recall against a held-out, adversarial set — as opposed to the September report's known-technique inventory?
What is the actual false-positive and false-negative profile at enterprise volume, and is there an appeal/allowlist path for legitimate research that asks models about their reasoning?
Does the summarisation control measurably degrade chain-of-thought monitorability for auditors? Anthropic quantifies the attacker-side loss (80.4% → 71.8% SWE-bench Verified) but not the oversight-side loss.
Do other frontier labs adopt the same binding model (model + prefix + account) — and do they interoperate, or do they create a fragmented reasoning-portability landscape? OpenAI's September 2026 disruption report (including "encrypted reasoning replay") is the obvious comparator.
Does the capability-gap narrative change? Specifically: does the growth rate of the best open-weight models slow measurably after these controls, or does it continue on schedule from other data sources?
Does enforcement asymmetry (accounts pre- vs post-2026-08-31) create a durable, exploitable two-tier surface as those accounts age, are migrated, or are resold?
Does the "defences are expensive and distillers pay" incentive problem get addressed by policy (the White House NSTM-4 / NSPM-11 line of instruments) or remain a voluntary-commitment race to the top?
Will any named lab give a substantive, point-by-point response, and has any relayed-customer privacy harm (Anthropic alleges relaying of customer data including a PLA-affiliated CCTV case) been independently confirmed client-side?
Is the 90–99% figure stable, or does Anthropic revise it in a later post? This is the cleanest forward test of the claim.
→
What should you do with this?
Circle 1
Circle 1 impact and recommended action
Circle 1 = the immediate practitioner/operator circle: developers and technical teams shipping on the Claude API.
Impact (FACT). Preserved thinking changes multi-turn API semantics. Teams whose harness edits system, tools, or earlier messages will hit 400 errors on new accounts (created on or after 2026-08-31) or lose reasoning silently, and may pay more output tokens as a result.
Impact (COMPANY CLAIM). Most well-behaved integrations need no change: nothing changes if Claude Code, claude.ai, Claude Managed Agents or the Agent SDK builds the requests, or if system/tools are fixed and only messages grows.
Impact (INTERPRETATION). Blocked-request billing and a sub-0.1% false-positive rate are tolerable in aggregate and annoying in the tail; the tail includes exactly the evaluators and researchers most likely to ask models about their own reasoning.
Recommended action
Run the documented prefix check today: with the thinking-binding-controls-2026-08-01 beta header, set prefix_mismatch_behavior: "drop_block", replay a few normal multi-turn sessions including a compaction and a tool change, and count prefix_binding_mismatch entries in input_transformations.
Convert system and tools to session-fixed and messages to append-only; keep assistant turns exactly as returned, thinking blocks included.
If your harness must edit the prefix, prefer a pattern that does not touch it (see the docs' "Make changes without editing the prefix"), and treat "drop_block" as a stopgap, not a destination.
Make prefix-mismatch counts an alertable metric. On the Batches API, set the mismatch behaviour explicitly so items fail loudly rather than dropping silently.
Do not build product behaviour on verbatim reasoning extraction. If a legitimate need exists, ask the vendor about an allowlist before shipping.
Circle 2
Circle 2 impact and recommended action
Circle 2 = the adjacent professional circle: platform teams, model/inference providers, aggregators, cloud resellers, and enterprise AI governance functions.
Impact (COMPANY CLAIM). Distillers distribute traffic across Anthropic's API, third-party cloud platforms and other inference providers; Anthropic argues platforms can "materially slow down distillation" by detecting abuse quickly and offboarding fraudulent accounts.
Impact (INDEPENDENT EVIDENCE / FACT). The NSA/CISA/FBI advisory recommends exactly that ecosystem coordination: cross-organisation intelligence sharing across model providers, cloud platforms and API aggregators, plus detection indicators for subscription-to-usage ratios, new accounts at maximum usage, and enterprise-scale throughput patterns.
Impact (INTERPRETATION). Aggregators and resellers are now inside the trust boundary of a vendor's anti-abuse programme. A reseller that cannot attest to its account provenance is a liability to its own customers, not just to the vendor.
Impact (FACT). Enterprise buyers inherit a governance question they did not previously ask: which provider binds reasoning to a prefix and an account, and which does not?
Recommended action
Platforms: implement the advisory's detectors (identity verification strength, subscription-to-API usage ratios, new-account burst patterns, correlated timing across pathways) and treat sudden metadata sanitisation after a public disclosure as a detection signal in its own right.
Aggregators/resellers: be able to attest account provenance and pass vendor identity checks; publish what happens to a customer's workload when an upstream account is banned.
Enterprise governance: add a short anti-distillation addendum to the AI vendor questionnaire — reasoning-binding behaviour, blocked-request billing, documented false-positive rate and its measurement method, and the integration changes the last 90 days introduced.
Security teams: map this to MITRE ATLAS (AML.T0040, T0051, T0054, T0024.002) so it sits in the existing taxonomy rather than a parallel one.
Circle 3
Circle 3 impact and recommended action
Circle 3 = the broad/civilisational circle: policy, national security, open-weight ecosystem, and the oversight community.
Impact (FACT). Distillation is now a defined policy object in US instruments (NSTM-4, April 2026; NSPM-11, June 2026; CISA/NSA/FBI advisory AA26-251A, September 2026). This vendor post supplies the defence-side half of a state-plus-vendor narrative.
Impact (INDEPENDENT EVIDENCE / INTERPRETATION). The advisory's recommended response — covertly degrading outputs for suspected distillers, and not telling them — is materially different from Anthropic's disclosed approach. Covert degradation has a foreseeable false-positive harm: a legitimate user flagged by mistake silently receives worse answers and cannot find out why. The advisory itself notes distillers run QA pipelines explicitly built to detect degraded outputs, so the covert approach may fail on its own terms.
Impact (INTERPRETATION). The oversight cost is real: summarising reasoning to devalue stolen traces also devalues readable traces for chain-of-thought monitoring, safety auditing, and interpretability. The oversight channel and the exfiltration channel are the same channel.
Impact (INDEPENDENT EVIDENCE). China's Foreign Ministry has previously rejected the US distillation advisory as "unfounded accusations and smears"; the rejection did not engage with per-company allegations or dispute the routing mechanism. Expect the geopolitical register to remain non-technical.
Recommended action
Policymakers and standards bodies: require that anti-distillation effect sizes be published with a stated measurement method and an audit path, or be labelled as vendor-reported. A percentage with no method is not a control standard.
Regulators/evaluators: demand a separation between disclosed mitigation (billing, documented classifier) and covert mitigation (silent downgrade), and require a disclosed appeal path for false positives if covert degradation is deployed.
Oversight community: press for a published measurement of what reasoning summarisation removes from a trace an auditor or CoT monitor would use — the mitigation's oversight cost is currently unquantified while its attacker-side benefit is quantified.
Open-weight ecosystem: note that a defence this shape pushes pressure toward whichever frontier-relevant model lacks it. The weakest-link argument is the strongest reason to prefer an interoperable, multi-vendor standard over a competitive one.
Journalists/analysts: keep the three claims separate — that the post exists (verified), that named labs did specific things (single-source), and that the defence reduced extraction by 90–99% (self-measured, unaudited).
Business value
Business-value opportunities where genuine
Honest assessment: this is a vendor research-and-controls announcement. Direct commercial opportunity is limited and mostly adjacent.
Integration remediation services (genuine, near-term). Auditing and fixing harnesses for prefix stability is concrete, bounded work with a documented specification, a beta header to test with, and a measured cost of failure (up to +67.1% output tokens at max effort when dropping every turn). This is a real, scoped engagement.
Reasoning-governance tooling (genuine, small). Instrumenting input_transformations into dashboards/alerts, and wiring prefix-mismatch events into existing context-management observability, is a modest but real product wedge.
Third-party measurement (genuine, high-value if anyone does it). The single clearest gap is independent evaluation of anti-distillation claims. A credible, repeatable method for estimating whether a student model was distilled from a given teacher — Google claims a Gemini-distilled-model identification capability in its own GTIG reporting — would be valuable to vendors, platforms and policymakers. This is the highest-value opportunity and the hardest.
Policy/regulatory advisory (genuine, moderate). Mapping an enterprise's exposure to NSTM-4/NSPM-11/AA26-251A guidance and to MITRE ATLAS distillation TTPs is a real consulting line, but it is advisory, not technical.
Not a business opportunity (be honest): "distillation-proofing your model" as a product claim. The defence is provider-side, unproven against a persistent adversary, and explicitly framed by Anthropic as an ongoing cat-and-mouse effort. Selling it as solved would be misleading.
Hands-On
Hands-on recommendation
VERIFY — verify the provenance and arithmetic of the headline figure, and check the documented enforcement rules against the published claim. See. The classifier itself is server-side and cannot be exercised without an account and a workload, so no BUILD/BREAK lab is honest here. What can be verified cheaply and rigorously:
that the "90–99%" headline is the same measurement as the "10 to 100 times lower" body figure (log-ratio identity)
that the primary post, the platform documentation, and the independent coverage agree on the three defence layers and the stated trade-offs
that no independent replication of the effect size exists in the sources located
that the documented enforcement boundary (accounts created on or after 2026-08-31) matches what the blog describes.
--
↗
What happens next?
🎓 For Explorer
PREDICTION (ranked by likelihood)
Near term (days–weeks). More coverage, most of it restatement; a handful of developer-facing explainers focused on the preserved-thinking migration. Expect at least one "does this break my agent harness?" piece and continued aggregation of the 90–99% figure without qualification.
Near term. Model-lab symmetry: OpenAI (and possibly Google) publishing or extending their own anti-distillation controls; the "encrypted reasoning replay" line is the obvious parallel.
Medium term. An adversarial test. Anthropic says it has not yet seen "a highly sophisticated and persistent attempt". The most informative next data point is either a sophisticated bypass (a new extraction technique that survives the classifier) or a durable absence of one.
Medium term. Named-lab responses, or continued silence. Point-by-point rebuttal would be new; blanket rejection at the ministry level has precedent.
Medium term. A revision or restatement of the effect size, or a follow-up post with an updated curve. The explicit uncertainty ("We don't yet know how long these gains will last") all but commits Anthropic to one.
Longer term. Reasoning access becomes a governed, metered, contracted resource across providers, with some inter-provider portability rules emerging (the model-reads-model matrix in the docs is already a portability policy).
Watch indicators. (a) Whether the best open-weight models' capability trajectory visibly slackens — the only externally observable test of the claim. (b) Whether any competitor adopts prefix/account binding. (c) Whether any regulator or auditor demands the measurement methodology. (d) Whether the relaying/privacy allegations (which are separate from the effect-size claim) produce a client-side confirmation or a lawsuit.
★
Editorial takeaway
🎓 For Explorer
The headline is a vendor's own measurement, in a vendor's own unit, on a vendor's own platform, against attacks the vendor itself detected — and that should be said plainly, not because Anthropic is being dishonest (it is unusually candid about trade-offs and about not yet facing a serious adversary) but because the number is now load-bearing in a national-security argument.
The genuinely new thing here is not the percentage. It is that reasoning traces have become a governed resource. Anthropic's anti-distillation control is now an API contract: a thinking block is bound to a model, to its exact prefix, and in some cases to an account. That is a breaking change for developers, a new cost line for blocked requests, and a quiet reduction in how much of a model's thinking anyone — attacker, auditor, or researcher — can read. The security gain and the oversight loss ride on the same control.
Read the piece as three separable claims: the post exists (verified); named competitors did specific things at specific scale (single-source, unfalsifiable from outside, and made by a competitor); and the defence cut extraction by 90–99% (self-reported, unaudited, and unproven against a persistent adversary). The first is journalism. The second is a diplomatic document. The third is a hypothesis with a deadline — the gap between open-weight and frontier models will either stop closing as fast, or the number will quietly be revised.
Artifact contains story ID S12. Evidence labels used: FACT, COMPANY CLAIM, INDEPENDENT EVIDENCE, INTERPRETATION, PREDICTION. Status label: EARLY RESEARCH.
≡
Research sources
Primary Sources (9)
Primary
NSA / CISA / FBI — Cybersecurity Advisory AA26-251A - **URL:** https://www.cisa.gov/news-events/cybersecurity-advisories/aa26-251a - **Organisation / author:** National Security Agency, Cybersecurity and Infrastructure Security Agency, Federal Bureau of Investigation** Independent-of-Anthropic confirmation that the US government treats industrial-scale distillation as a defined threat: the named labs (DeepSeek, Moonshot AI, Alibaba, MiniMax, StepFun, Z.AI), the "critical core" framing, MITRE ATLAS TTP mapping (AML.T0008, T0040, T0051/T0054, TA0008, T0042, TA0009, T0024.002, T0048), the four novel TTPs, detection indicators (subscription-to-usage ratios, new accounts at maximum usage), and — important for S12 — the recommendation of **covert response degradation** ("Avoid informing… users suspected of distillation campaigns of a switch to a downgraded model"), which differs from Anthropic's disclosed approach. Also cites the White House policy instruments NSTM-4 and NSPM-11. — ** Government primary source. **Caveat recorded:** the advisory discloses no detection method or per-lab data and its reference list is the vendors' own disclosures (Anthropic, Google GTIG, OpenAI), so it corroborates the *names*, not the *counts*. ---Date: 2026-09-08 (TLP:CLEAR)
URL unavailable
Primary
NIST — CAISSI assessment of Z.AI's GLM-5.3 cyber capabilities - **URL:** https://www.nist.gov/news-events/news/2026/09/caisis-assessment-zais-glm-53-cyber-capabilities - **Organisation / author:** US Center for Advancing Innovation and Standards for Super Intelligence (CAISSI), NIST** The one element of the Zhipu example that is a government assessment rather than a vendor assertion: that GLM-5.3 is the most cyber-capable open-weights model released to date. Cited in the primary post. — ** Government / regulatory primary source.
URL unavailable
Primary
Anthropic — "GLM-5.3 and the spread of advanced cyber capabilities" - **URL:** https://www.anthropic.com/research/glm-5-3-and-the-spread-of-advanced-cyber-capabilities - **Organisation / author:** Anthropic** Anthropic's claim that GLM-5.3's safeguards can be bypassed and that the model will develop end-to-end security exploits — the capability half of the Zhipu case offered in the October post. — ** Primary / first-party.Date: 2026-09 (linked from the 2026-10-12 post)
URL unavailable
Primary
Anthropic — "Next-generation constitutional classifiers" - **URL:** https://www.anthropic.com/research/next-generation-constitutional-classifiers - **Organisation / author:** Anthropic** The design lineage of the two-stage extraction classifier Anthropic says it deployed; it is the documented provenance for the "built on our constitutional classifiers research" claim. — ** Primary / first-party background.Date: 2025–2026 (referenced by the 2026-10-12 post as the architectural basis of the extraction classifier)
URL unavailable
Primary
Anthropic — "Introducing Claude Opus 5.5" - **URL:** https://www.anthropic.com/claude-opus-5-5 - **Organisation / author:** Anthropic** That preserved thinking shipped as a product feature with Opus 5.5, following Fable 5.1 — locating the control in dated product releases rather than only in the October post. — ** Primary / first-party.Date: 2026-09-23 (per independent coverage of the same release)
URL unavailable
Primary
Claude Platform documentation — "Preserved thinking" - **URL:** https://platform.claude.com/docs/en/build-with-claude/preserved-thinking - **Organisation / author:** Anthropic (product documentation)** The exact, documented mechanics of the anti-distillation control: model binding (the model-reads-model matrix, e.g. Fable 5.1 reads Opus 5 and, on the Claude API, Opus 5.5; neither Opus 5 nor Opus 5.5 reads Fable 5.1); prefix binding (`system`, `tools`, and all earlier `messages`; 400 by default or `drop_block`); account binding on Sonnet 5.5 and Haiku 5.5; the beta header `thinking-binding-controls-2026-08-01`; mirroring the documented enforcement boundary to new accounts created on or after 2026-08-31; the list of integration patterns that edit the prefix; the measured output-token penalty of `"drop_block"` (once per session: +2.5% low / +3.9% medium / +4.5% high / +20.1% max effort; every turn: +4.6% / +9.7% / +10.3% / +67.1%); Batches API behaviour; which integrations need no change. — ** Primary / first-party product documentation. Used as FACT for documented API and product behaviour (independent of the effect-size claim).Date: current as of 2026-10 (undated document; describes enforcement for accounts created on or after 2026-08-31 00:00 UTC)
URL unavailable
Primary
Anthropic — "Detecting and preventing distillation attacks" (February 2026 disclosure) - **URL:** https://www.anthropic.com/news/detecting-and-preventing-distillation-attacks - **Organisation / author:** Anthropic** The earlier baseline the new post measures against — the >16 million exchanges and ~24,000 fraudulent accounts; one proxy network managing more than 20,000 accounts at once; the original stated goal of making distillation harder "without affecting the experience for legitimate users". — ** Primary / first-party background. **Note on use:** referenced and quoted through the primary post and independent coverage; not fetched directly.Date: 2026-02 (linked and referenced from the 2026-10-12 post)
URL unavailable
Primary
Anthropic — Threat Intelligence: "Detecting and countering misuse of AI: September 2026" - **URL:** https://www.anthropic.com/threat-intelligence-report-september-2026 - **PDF:** https://www-cdn.anthropic.com/e50be2e51e7695dc4b1366a37a245a597377d3b5/Anthropic-Detecting-and-countering-091026.pdf - **Organisation / author:** Anthropic Threat Intelligence** The antecedent disclosure that the 2026-10-12 post responds to — the "nearly 200 million" distillation-related exchanges across five campaigns; the Alibaba/Qwen campaign with more than 151 million exchanges between May and July 2026 (peaking near 3 million/day across ~3,500 accounts); the extraction-technique inventory (verbatim-reasoning prompts, 12,000-variant technique searches, translation laundering, tag-wrapped reasoning, thinking-signature replay); the claim that distillation transfers capability but not safeguards. — ** Primary / first-party for the September disclosure. **Note on use:** this document was used via the primary post's own links to it and via extensive independent quotation (TechCrunch, Howardism). It was not fetched page-by-page in full during this research; treat the per-lab exchange counts as Anthropic attributions.Date: 2026-09-10
URL unavailable
Primary
Anthropic — "Strengthening our defenses against distillation attacks" - **URL:** https://www.anthropic.com/research/distillation-defenses - **Organisation / author:** Anthropic (first-party research blog post)** The event itself. The 90–99% reduction claim; the underlying "10 to 100 times lower" reasoning-token measurement; the three defence layers (preserved thinking; two-stage classifier built on the constitutional-classifiers approach; stricter limits, bans, and billing for blocked requests since 2026-09-24); the sub-0.1% false-positive claim and the bioweapons-safeguard robustness comparison; the SWE-bench Verified distillation experiment (80.4% on full transcripts vs 71.8% on summarised transcripts after training on Claude Opus 4.8 traces); the Zhipu/GLM-5.3 and Moonshot/Kimi cases; the PLA-affiliated CCTV case; the admitted trade-offs (turned-away revenue, "trillions of tokens" of refused paying traffic, integration changes, billed blocks); the cat-and-mouse concession and the admission that no highly sophisticated persistent circumvention attempt has yet been observed; the industry-incentive argument ("illicit distillers are still paying customers"). — ** Primary / first-party. Treated as COMPANY CLAIM for all effect sizes and all attributions; treated as FACT for the existence and content of the publication.Date: 2026-10-12
URL unavailable
Independent Sources (7)
Independent
Google Threat Intelligence Group — "GTIG AI Threat Tracker" - **URL:** https://cloud.google.com/blog/topics/threat-intelligence/from-prompting-to-autonomy-the-evolution-of-adversarial-ai - **Organisation:** Google Threat Intelligence Group (a second victim-provider)** A second provider's account of the same activity class — campaigns "some exceeding 100 million prompts", multimodal targets, rotated compromised credentials and fraudulent accounts, a claimed ability to identify Gemini-distilled student models, and "real-time proactive defenses that can degrade student model performance". Used to show the defence pattern is industry-wide, not Anthropic-specific. Cited here via the independent analysis at `https://www.howardism.dev/articles/illicit-distillation`; the primary GTIG post was not fetched directly in this research. — ** Independent (second-provider) source, referenced at second hand. Label: company claim by another vendor. ---Date: 2026-09-08
URL unavailable
Independent
Reuters wire dispatch (via syndication) — "Anthropic says new safeguards sharply reduce AI distillation attacks" - **URL:** https://wtaq.com/2026/10/12/anthropic-says-new-safeguards-sharply-reduce-ai-distillation-attacks/ - **Organisation:** Reuters (wire copy syndicated by affiliate stations)** That a major wire service covered the announcement on the event date and characterised it as Anthropic saying new measures prevent rivals from copying Claude's capabilities, with Claude models having reduced data harvested in distillation attacks by about 90% to 99%. — ** Independent secondary reporting. **Fetch caveat:** to direct retrieval; the title, date and opening lines were confirmed via search-index snippet only, and the text is treated at snippet level, not as a fully read article.Date: 2026-10-12 ("Oct 12 (Reuters)…")
URL unavailable
Independent
explainx.ai — "Anthropic Says New Distillation Defenses Cut Stolen Reasoning Data by 90 to 99 Percent" - **URL:** https://explainx.ai/blog/anthropic-distillation-defenses-preserved-thinking-classifier-90-99-percent-2026** Independent developer-facing breakdown of the post, and — critically for evidence discipline — the explicit independent finding that **no independent audit exists** of the 90–99% reduction, the 10×–100× token drop, or the false-positive rate, with the sharp formulation that "a defense measured against the attacks a company can detect will always look good against detected attacks", and the note that Anthropic "does not publish its methodology for measuring attempts it never sees". Also: the preserved-thinking developer implications (context-editing audits, billed blocks, reasoning-dump prompts being classifier targets, reseller/account-ban risk), and the models covered (Sonnet 5.5, Opus 5 and 5.5, Fable 5 and 5.1). — ** Independent secondary analysis; used specifically as evidence of the **absence of independent verification**.Date: 2026-10-13
URL unavailable
Independent
Resultsense — "Anthropic says new defences cut distillation of Claude by up to 99%" - **URL:** https://www.resultsense.com/news/2026-10-13-anthropic-distillation-defences-90-percent-cut/ - **Organisation:** Resultsense (UK AI news/analysis)** Independent 2026-10-13 analysis confirming the event date ("said on Monday 12 October"), the 90–99% / tenth-to-a-hundredth framing, the 80.4% vs 71.8% SWE-bench figure, the three defence layers, and the named costs — turned-away revenue, integration changes, and billing for blocked requests since 24 September. Its own assessment ("the trade-off is defensible, but it shifts friction onto paying customers") is used as an independent interpretive datapoint, as is its cross-reference to OpenAI's disruption of a Moonshot-linked campaign against its own hidden reasoning (2026-10-01). — ** Independent secondary analysis.Date: 2026-10-13
URL unavailable
Independent
Howardism — "Illicit Distillation" - **URL:** https://www.howardism.dev/articles/illicit-distillation** The most substantive independent technical critique located. It documents the extraction-technique ladder (verbatim instruction, forged system prompt, translation laundering, 12,000-request technique search, cross-session thinking-signature replay); per-actor attributed exchange counts (Alibaba >151M; Moonshot >23M; DeepSeek >12.1M over 14 days; Zhipu >3.4M; Xiaomi >400k); the critical reading that every attribution is single-source, method-free and unfalsifiable from outside; the AA26-251A caveat that the advisory's references are vendor disclosures, so co-naming two documents is not two witnesses; the internal inconsistencies it identifies in the advisory's tables; the safety claim's evidentiary gap (no uplift figure, no domain, no student model, no baseline); the countermeasure cost analysis — including that summarising reasoning degrades chain-of-thought monitorability for auditors and researchers, since the oversight channel and the exfiltration channel are the same channel; the covert-degradation versus disclosed-mitigation tension; and the China Foreign Ministry rejection. — ** Independent analysis / INTERPRETATION (explicit; used as critique and framing, not as measurement).
URL unavailable
Independent
Cryptobriefing — "Anthropic says new defenses cut distillation data harvested from Claude by 90 to 99 percent" - **URL:** https://cryptobriefing.com/anthropic-claude-distillation-attack-defenses/** Independent same-day coverage of the event; the ~90–99% figure as reported; the 151 million-exchange Alibaba/Qwen attribution (May–July 2026); the February comparison (>16 million exchanges, ~24,000 fraudulent accounts); a description of the layered defences (bans, metadata analysis, behavioural classifiers, organisational attribution); preserved thinking described as preventing new API accounts from editing encrypted reasoning context; and the industry parallel — OpenAI's September 2026 report on disrupting distillation, including "encrypted reasoning replay". Also captures the independent-facing safety framing: a distilled copy may not inherit the teacher's guardrails. — ** Independent secondary reporting.Date: 2026-10-12
URL unavailable
Independent
TechCrunch — "Anthropic details distillation campaigns from Alibaba, Moonshot AI, and DeepSeek" - **URL:** https://techcrunch.com/2026/09/10/anthropic-details-distillation-campaigns-from-alibaba-moonshot-ai-and-deepseek/** Independent journalistic account of the September disclosure that the October post builds on: nearly 200 million exchanges across five campaigns; the Alibaba campaign's 151 million exchanges (May–July 2026), ~3,500 accounts, single fixed prompt, peaking near 3 million exchanges/day; the Moonshot/Kimi relay case including the "translate previous working memory into… katakana-only Japanese" extraction prompt and ~300,000 requests over ten days through ~5,000 accounts; the context that Anthropic typically exposes only "summarized thinking" blocks; and the cross-lab context (earlier Anthropic and OpenAI disclosures). — ** Independent secondary reporting (restates Anthropic's report; does not independently verify counts).Date: 2026-09-10
URL unavailable
Secondary Sources (4)
Secondary
Claude Support — "Why Claude switched models in your conversation with Sonnet 5.5" - **URL:** https://support.claude.com/en/articles/17161993-why-claude-switched-models-in-your-conversation-with-sonnet-5-5 - **Organisation:** Anthropic support documentation** That preserved thinking is presented to end users as a change to how the Messages API handles thinking blocks, explicitly "to protect against distillation", and that model switching can occur mid-conversation — the user-visible face of the control. — ** Primary-adjacent documentation (vendor support centre). ---
URL unavailable
Secondary
LiteLLM documentation — "Preserved Thinking Prefix Stability" - **URL:** https://docs.litellm.ai/docs/providers/anthropic_preserved_thinking** Third-party gateway/tooling acknowledgement that Claude models that preserve thinking across turns sign each thinking block and bind it to the request that produced it — i.e. that the binding model has spread into the wider tooling ecosystem. — ** Secondary / implementation ecosystem.
URL unavailable
Secondary
The New Stack — "Anthropic made Opus 5.5 cheaper. Then it broke four things" - **URL:** https://thenewstack.io/claude-opus-agent-migration/** Independent developer-press confirmation that thinking/prefix-binding changes introduced breaking changes capable of triggering 400 errors in existing agents — the migration-hazard side of preserved thinking. — ** Secondary reporting.Date: 2026-09-23 (approx., Opus 5.5 migration coverage)
URL unavailable
Secondary
Claude Opus 5.5 release coverage — Help Net Security - **URL:** https://www.helpnetsecurity.com/2026/09/23/anthropic-claude-opus-5-5/** Independent confirmation that "preserved thinking" shipped as a named anti-distillation safeguard with Claude Opus 5.5 (following Fable 5.1), i.e. that the control predates the October post and was deployed through product releases. — ** Secondary reporting.Date: 2026-09-23