You may have read claims like these: Claude has a "Golden Gate Bridge" feature, and turning it up makes the model say it is the Golden Gate Bridge; when Claude 3.5 Haiku writes a poem, it picks the rhyming word for the end of a line before it starts writing the line. How were these conclusions reached, and how far should you trust them? That is what mechanistic interpretability is for: instead of only looking at inputs and outputs, it looks inside the model for features and circuits that explain a behaviour, and then tests the explanation by changing internal state. As of October 2026, the toolkit can give verifiable local explanations for some models on some prompts; it is still a long way from fully reading a frontier model.

Draft, pending review. The site owner has not reviewed this note yet; facts, emphasis and wording may change. Check the primary sources linked in the text before relying on it.

What it asks: the step beyond behavioural evaluation

Behavioural evaluation asks "on these inputs, is the output right?". Interpretability asks "which intermediate quantity inside the model produced this output, and if I change it, does the output change as predicted?".

An example. Two models both complete "Fact: the capital of the state containing Dallas is" with Austin. One may first work out Texas internally and then go from Texas to Austin; the other may simply have memorised the pairing of Dallas and Austin. Accuracy is identical, and a behavioural evaluation cannot tell them apart. In Claude 3.5 Haiku, Anthropic found both: a two-step path through "Texas" features, plus a shortcut edge from Dallas straight to "say Austin"; suppressing the "Dallas" features weakened the "Texas" features and what lies downstream of them (Lindsey et al., March 2025). With a new set of cities, or when the model believes it is being tested, this kind of difference can start to matter.

Two key terms:

  • Feature: the unit inside a model that represents some concept. The most common working assumption is that a feature corresponds to a direction in activation space (the linear representation hypothesis; see note 1).
  • Circuit: a computational path connecting features through specific components (attention heads, MLPs), which can be tested by intervention.
Behavioural evaluation Mechanistic interpretability
What it asks Is the output right on these inputs? Which internal quantity caused this output?
Evidence Accuracy, success rate, preferences Probe readouts, patching effects, attribution graphs plus interventions
Strengths Cheap, scales, maps directly onto what users care about Separates "same score, different mechanism"; may reveal states that never show up in the output
Weaknesses Does not know why the model is right; a model that knows it is being tested may behave differently Slow, expensive, narrow coverage; often explains an approximate replacement model

The world-models series note Do they actually understand the world? already covers using probes to check whether a model holds world state internally (Othello-GPT and others). This series does not repeat that; it covers the tools themselves.

The main tools

Tool What it does Evidence it gives Main pitfall Note
Linear probe Trains a linear classifier on frozen activations The information can be read out The probe may have learned the task itself; readable does not mean used Note 1
Activation steering Adds or subtracts a direction in the activations This direction can change behaviour Being able to change behaviour does not make it "the" concept; strength needs tuning and capabilities can suffer Note 1
Sparse autoencoders, transcoders Write an activation as a sum of a few dictionary directions Many candidate features, found without labels Reconstruction is incomplete; labels can be wrong; often lose to simple baselines downstream Note 2
Activation patching (causal tracing) Swaps an intermediate value from one run into another Whether a component is necessary or sufficient for a behaviour Conclusions shift with the metric and the corruption method Note 3
Path patching, automated circuit discovery Patches only along specific edges Which paths a behaviour flows through With nonlinearities, path effects do not add up to the total Note 3
Attribution graphs Draw the feature-to-feature graph for one prompt using a replacement model Automatically generated mechanism hypotheses Explain the replacement model; the original version does not explain why attention looks where it does Note 3
Natural-language readouts Have a model translate activations into text Hypotheses you can read directly Can invent details; cannot say which part of the activation an explanation rests on Notes 2 and 3

A timeline

As of October 2026

  • Interpretability has entered labs' pre-deployment audits, but the evidence is mostly lab-reported case studies. The Sonnet 4.5 system card (Anthropic, September 2025) reports that after inhibiting several directions related to "this is a test", on 100 synthetic honeypot prompts the model said out loud that it was being tested less often, and misaligned actions rose from zero to at most 8–9%. The NLA paper (Anthropic, 2026-05-07) says that in the pre-deployment audit of Claude Opus 4.6, NLAs helped surface cases where the model believed it was being tested without saying so.
  • SAEs have lost standing and simple baselines have gained it. The Google DeepMind team deprioritised fundamental SAE research in March 2025 and in December 2025 argued for trying simple methods first (prompting, steering, probing) and adding complexity only when they fall short; AxBench (January 2025) found that on steering, prompting beats every representation-based method. In 2026 there are still preprints defending SAEs (Jørgensen & Hansen, May 2026).
  • There are more open tools. Gemma Scope 2 covers every Gemma 3 size from 270M to 27B; Google DeepMind self-reports storing about 110 PB of data and training over 1 trillion parameters. circuit-tracer plus Neuronpedia let outside researchers draw attribution graphs on open models.
  • The new kind of readout is "translate it into text". NLA-style methods explain activations in natural language. They are easy to read, but the authors themselves list limitations: confabulation, no mechanistic grounding, and high training and inference cost.

What has settled and what is still moving

Each cell corresponds to a dated public record; the "what to watch" column describes which result would change the assessment, not a prediction that it will happen.

Fairly settled Still moving Signals to watch
Superposition really occurs in toy models; SAEs find many readable, steerable directions in large models (Elhage et al., September 2022; Templeton et al., May 2024) Whether these directions are features the model "really uses": with the same data and only the random seed changed, a 131K-wide SAE shares only about 30% of its features (Paulo & Belrose, January 2025) Features stable across seeds and architectures; a clear lead when randomly initialised models are used as the baseline
On a small model a circuit can be verified end to end: the IOI circuit recovers 87% of the full model's logit difference and was checked for completeness and minimality (November 2022) Automated circuit discovery on large models: Anthropic says attribution graphs give a satisfying explanation on only about a quarter of the prompts it tried (March 2025) That fraction rising in later reports; other labs reproducing it on their own models
Simple linear directions can read out, and change, some safety-relevant behaviour: a refusal direction holds across 13 open models (Arditi et al., June 2024); deception probes reach AUROC 0.96–0.999 (Apollo, February 2025) Whether such probes are robust on real deployment distributions: Apollo itself says they are not yet sufficient as a robust defence Detection results on problems that were not deliberately implanted, reproduced by third parties
On downstream tasks with strong baselines, SAEs often do not come out ahead (Kantamneni et al., February 2025; Google DeepMind, March 2025; AxBench, January 2025) Whether improved SAEs reverse this: SAEBench (March 2025) finds proxy metrics disconnected from practical usefulness New dictionary methods consistently beating difference-in-means and linear probes on proxy tasks fixed in advance
Interpretability tools have found concrete problems in pre-deployment audits, such as a batch of mismatched training data for Opus 4.6 (self-reported by Anthropic, May 2026) Whether problems can be found reliably without knowing the answer: in an auditing game, 3 of 4 teams found the hidden objective and the API-only team did not (Marks et al., March 2025) Amodei's April 2025 goal is for interpretability to "reliably detect most model problems" by 2027 (essay); public results from third-party white-box audits

"Fairly settled" means there is a first-hand result in the original paper's setting; it does not mean it holds for other models or tasks.

How this relates to other notes on this site

Where to start in the primary sources

How to read this series

  1. Features, superposition, and linear probes: the linear representation hypothesis, what probe accuracy shows, a hand-worked example of 3 features squeezed into 2 dimensions, and activation steering
  2. Sparse autoencoders: the reconstruction-plus-sparsity objective, two values of λ worked by hand, dead latents and feature splitting, automated labelling, scaling numbers, and the 2025–2026 critiques
  3. Circuits, attribution, and causal interventions: activation and path patching, a 3-node example by hand, the IOI circuit, attribution graphs, and how this connects to safety evaluation
  4. Review questions: interview questions and self-check