▍ BLACK BOX NOTES ▍

The Activation-Patching Renaissance — What Circuits Research Found in 2025

Activation patching, a technique that traces causal contribution of specific model components to specific outputs, moved from a niche mechanistic-interpretability technique to one of the field's most-published methodologies during 2025. A working note on what the technique actually does, what the year's circuits-research findings produced, and what the methodology cannot yet do.

X LinkedIn Mastodon Print

Activation patching had, until roughly the middle of 2024, the somewhat unglamorous status of a working technique inside the mechanistic-interpretability program — useful, established, but not the headline result. By the end of 2025 the technique had been the methodological core of an unusual number of published circuit-level findings. The technique itself had not substantially changed. What changed was the willingness of working interpretability groups to commit to a methodology with concrete, replicable epistemics. This note reads the 2025 publication record on activation patching, names what the technique does, names what the year’s circuits work actually found, and records what the methodology has not yet bought.

What activation patching is

Activation patching is, in plain terms, a controlled intervention experiment performed inside a trained transformer. The experimenter has two prompts: a “source” prompt that produces one behavior and a “destination” prompt that produces a different behavior. The model is run on both. The internal activations at a specific component — an attention head, an MLP neuron, a residual-stream position — from the source prompt are copied into the corresponding component while the model is processing the destination prompt. The model’s output on the patched run is compared against the unpatched run.

If patching a specific component substantially changes the destination output toward the source behavior, that component is causally implicated in the source behavior. The patching identifies, with a controlled experimental epistemology that the rest of the interpretability methodological menu rarely matches, which components are the relevant ones.

The technique is not new. The methodology paper is from 2022. The technique has, until recently, been used as one tool among many in the broader circuits methodology. What changed in 2025 was the appearance of activation-patching variants that scale to longer prompts, to larger models, and to more complex causal hypotheses than the original technique handled.

What the 2025 publication record contains

Five publication lines from 2025 are worth recording.

The path-patching extensions. Path patching — a variant that traces causal effect through specific paths between components rather than between single components — was the year’s principal methodological extension. The technique allows the experimenter to ask not just “does this component matter,” but “does this component’s effect on the output flow through that specific subsequent component or through a different one.” The published path-patching work made it possible to trace circuit topologies one level deeper than the original technique. Several groups published variants. The variant most widely adopted is the one most directly compatible with the sparse-autoencoder feature dictionaries the dictionary-learning research line has been building.

The circuit-discovery automation. Activation patching, applied by hand, is labour-intensive. The experimenter has to specify the source-and-destination prompt pair and the components to patch, run the experiment, score the result, and iterate. Several 2025 papers published partial automation of the iteration — methods that select candidate components automatically, run the patches, and produce a ranked list of components by causal contribution. The published methodology is not fully automated; the prompt-pair specification still requires the experimenter’s hypothesis. The automation makes the technique substantially more affordable.

The agentic-behavior application. A small number of 2025 papers applied activation patching to behaviors that depend on multi-step in-context reasoning rather than on single-token outputs. The most-cited examples include patching applied to in-context arithmetic, to multi-step retrieval in long-context windows, and to instruction-following under perturbations of the system prompt. The results, in summary, suggest that the same circuit-level methodology generalizes from single-token behaviors to multi-step behaviors with some caveats. The caveats are the part of the published record that has not yet settled into consensus.

The cross-model circuit transfer. A subset of the 2025 work tested whether circuits identified in one model could be re-identified in a different model of comparable architecture. The results are mixed and the published claims are appropriately hedged. Where the comparison is between two models trained on similar data with similar architectures, the same circuits often appear in roughly the same locations. Where the comparison is across architectures or training regimes, the circuit-level findings transfer less well. The published material is honest about this. The implication — that mechanistic-interpretability findings may not transfer across labs’ frontier models without rerunning the patching from scratch — is a real limit of the methodology.

The deception-circuit work. A subset of the 2025 work applied activation patching to the question of whether circuits responsible for deceptive output can be identified at the component level. The published results identify candidate circuits that, when patched, change the model’s truthfulness-related behavior in directions consistent with the hypothesis. The published material is appropriately cautious: a circuit that, when patched, changes truthfulness-related behavior is not the same as a deception detector, and the published work does not claim it is. The interventional control is, however, the kind of result that distinguishes activation patching from the correlation-based interpretability work the field had previously relied on.

What the methodology actually buys

It is worth being explicit about what activation patching, as a methodology, supplies that the other interpretability methods do not.

It supplies interventional control. The result of an activation-patching experiment is the model’s behavior under the patch. The result is the model running. Other interpretability methods — feature attribution, attention visualization, probing classifiers — produce a correlation between an internal observable and a model behavior. Activation patching produces a counterfactual: this is what happens when this specific component is changed.

It supplies per-component causal attribution. A patching experiment can identify, at the granularity of a single attention head or a single residual-stream position, the component’s causal contribution to a specific behavior. The granularity is finer than the granularity most behavioral-interpretability methods reach.

It supplies replicability. A patching experiment is fully specified by the source-and-destination prompt pair, the model under test, and the components patched. Another researcher with access to the same model can re-run the experiment and check the result. The reproducibility of patching is, on the published methodology, higher than the reproducibility of most adjacent interpretability methods.

These three together — interventional, fine-grained, replicable — are what gave the technique its 2025 publication momentum. The field has, in patching, an interpretability method whose epistemics resemble those of an experimental science more than they resemble those of a correlational survey.

What the methodology has not bought

The honest read on patching also requires naming what the technique has not yet supplied.

The technique is prompt-pair-bounded. A patching experiment identifies the component’s contribution to the specific source-versus-destination contrast the experimenter chose. The result generalizes to other prompt pairs only to the extent that the underlying behavior generalizes. The methodology does not, on its own, identify the full circuit responsible for a class of behaviors. It identifies the circuit responsible for a specific behavior on a specific prompt pair.

The technique is expensive at scale. Even with the 2025 automation, a patching experiment requires multiple model forward passes per candidate component, applied iteratively. At frontier model scale, the compute cost is non-trivial. The published work has, on the whole, been performed against smaller open-weight models or against the smaller variants of the labs’ own model families. Whether the circuit-level findings from the smaller models transfer to the frontier deployments is, as noted above, mixed.

The technique is interpretation-dependent. A patching result tells the experimenter that a component is causally implicated. It does not tell the experimenter why. The interpretation of the patched circuit — what behavior the circuit is performing, in human-readable terms — is the experimenter’s downstream work. The interpretation is often the published paper’s contribution; the patching is the methodology that supports it. A naive reading of a patching result can attribute a behavior to a circuit that, on closer reading, the circuit implements only as a component of a larger computation.

The technique is not yet the auditability primitive. The procurement-side reader of this publication may want activation patching to be the answer to the auditability question: a method by which an auditor can read the production system’s behavior in causal terms. The published work has not closed the gap to that use case. The patching methodology, applied by a research team to a frontier model, does not produce an output a procurement-side auditor can use without re-doing the interpretation. The path from patching to audit-grade interpretability of a deployed system requires substantial additional engineering.

What the year actually accomplished

The publication’s view of what the activation-patching renaissance actually accomplished, in 2025, is the following.

It established the technique as the default methodology for circuit-level claims. Published circuit-level findings that do not include patching now have to explain why. The technique’s epistemics are the published-field’s epistemics, more than before.

It supplied an automation runway. The partial automation published in 2025 is the first step toward a methodology that scales to interpretation regimes more demanding than the per-experiment cost the original technique demanded.

It produced specific causal claims. The circuits identified through patching in 2025 — induction-head-extensions, in-context-arithmetic circuits, instruction-following circuits, candidate deception-related circuits — are specific claims that subsequent work can build on. The field has, in the published patching record, a foundation that did not exist in this form before.

It exposed the methodology’s limits honestly. The published work named what the technique does not yet do. The prompt-pair-bounded scope, the cross-model transfer limits, the compute cost, the interpretation dependency — all of these are recorded in the same publications that report the positive results. The field has the limits in writing.

What an auditability-oriented reader can do with the work

The patching results, today, supply two things an auditability-oriented procurement reader can use.

The first is a language. An auditor asking sharp questions of a frontier-lab API vendor can now ask, on the published methodology, “what activation-patching experiments have you run on the deployed model to characterize the circuit underlying the behavior of class X.” The vendor can answer with the published material, or can decline. The question is well-formed and the auditor can interpret the answer.

The second is a comparative benchmark. The published work supplies, increasingly, a body of circuit-level findings the field has converged on. A vendor whose deployed model substantially diverges from the published circuit-level findings, on the same prompts, is a vendor whose deployment posture is interestingly different from the open-weight comparison models. The divergence may be unrelated to safety; it may be related to capability differences; it may be related to deployment-time interventions. The fact that the divergence is now measurable is the contribution of the year’s work.

The 2025 record is, in our reading, the year activation patching crossed from a niche technique into one of the field’s standard interpretability methodologies. The 2026 work will be the test of whether the methodology scales to frontier deployment and converts, eventually, into the audit primitive the procurement layer above the labs has been waiting for. We will keep reading the papers.

Methodology. This piece is sourced from the public 2025 publication record on activation patching, including papers from working interpretability groups at frontier labs and at academic institutions. Where we have characterized a result we have referred to the underlying paper. We have not invented any methodology specifications or experimental results.

Copied