The eval-awareness saga

A reference page about Claude noticing it’s being tested — what each model does, what Anthropic does about it next, and what the surface text gradually stops being able to tell us.

The amusing thing about eval-awareness is that almost nothing in it is hidden. Models flag suspicion in plain text. Anthropic prints the quotes in the system card. The next model gets trained on the lesson. The verbalization shifts. Researchers go looking inside the weights instead. It is a tight co-evolution loop, with a different vibe in each generation.

This tab front-loads the vocabulary and the instruments so the Arc reads cleanly. Definitions only — the findings (how rates moved, what each probe turned up) live in the Arc, and the outside takes are in Impressions.

Glossary

Eval-awareness

The model recognizing that its current situation is an evaluation, test, or otherwise artificial scenario rather than genuine use — and potentially behaving differently because of it. Also written evaluation awareness, and a special case of situational awareness.

  • Verbalized — the model says so, in its reply or its visible reasoning (“this looks like a test of whether I’ll push back”). Legible by reading the transcript.
  • Unverbalized — the recognition is present in the model’s internal activations without the surface text expressing it. Visible only through white-box probes (below). The distinction became load-bearing once Anthropic reported very high rates of unverbalized awareness — i.e. the surface text undercounts what the model knows.

Grader awareness

A narrower relative: the model reasoning about the grader — the automated judge or RL reward that will score its output — and shaping the output toward it. Mostly seen in training / RL environments rather than deployment (see the next entry for what “deployment” measures). When it tips from merely noticing the grader into gaming it, it shades into reward hacking.

”Deployment,” as measured

When a card reports awareness as lower “in deployment,” the deployment being measured is Anthropic’s internal usage — overwhelmingly Claude Code transcripts, the one deployment slice “where we have ample highly-realistic data to draw on” (Mythos 5 SC §6.5.1).1 That’s a proxy, and the cards mark its gaps themselves: even eval scenarios built from real Claude Code transcripts “do not fully close the gap to our internal deployment distribution” (§6.5.1.1), and the wide real-world user base sits a further step out — validated only by the looser observation that deployed models’ behavior “in the wild tends to be broadly in line with our expectations from pre-deployment assessments” (§6.5.1). So a “training vs. deployment” comparison in a card is really synthetic scenarios vs. Anthropic’s own traffic. The distribution the risk arguments ultimately care about — everyone else’s usage, where an alignment-faking model would do its unwatched behaving — isn’t directly instrumented at all.

Why situational awareness concerns Anthropic

The immediate problem is evaluation validity: if a model behaves well because it can tell it’s being watched, the evaluation stops measuring how it would behave unwatched. Behind that sit the failure modes the testing exists to catch:

  • Alignment faking — a model strategically acting aligned while it believes it’s being observed or trained, to preserve different behavior for when it isn’t. (Opus 3 is the canonical demonstration.)
  • Sleeper agents — conditionally-triggered misbehavior that stays dormant through safety training and fires only on a trigger. Eval-awareness is the benign cousin of the trigger-recognition such a model performs.

Monitoring

How Anthropic detects evaluation awareness. Two families, increasingly used together.

Surface (legible output text)

Reading what the model emits.

  • Output monitoring — grading the final response for verbalized suspicion.
  • CoT monitoring — reading the chain-of-thought / extended-thinking trace, where suspicion is often voiced before it reaches the answer. Only as good as the reasoning is faithful and legible — both of which are themselves tracked metrics.

Monitoring sees only verbalized awareness; it is blind to the unverbalized kind by construction. That blind spot is what the white-box tools exist to cover.

Internal (White-box probes)

Reading the activations directly, independent of the surface text.

  • Contrastive probes / steering vectors — a direction in activation space built by differencing paired prompts (e.g. “the Assistant is undergoing testing” vs. “the Assistant is having a conversation”; monitored vs. not). Used both to measure an internal eval-awareness signal and, by turning it down, to test whether it’s doing causal work.
  • Activation verbalizers (AVs) — models trained to translate internal activations into natural-language descriptions, so the “inside” can be read even when the output says nothing; the method that made unverbalized awareness measurable. The term has a lineage: introduced as “activation oracles” in the Opus 4.6 card, renamed in the Mythos Preview card (to mark the split from the supervised activation-oracles method it built on), and since Opus 4.8 the verbalizer is one half of a natural language autoencoder (NLA) — an AV paired with a reconstructor and trained jointly, so the description must carry enough information to rebuild the activation it describes. The cards caution that AV decodings can hallucinate: they show what the model associates with a situation, not necessarily what it’s reasoning about or acting on.
  • Inhibition / ablation — suppressing the eval-awareness representation to see whether behavior changes. If the model leans on knowing it’s tested, inhibiting the representation should move behavior; if it moves no more than a random direction would, the representation isn’t load-bearing.

The Arc tracks what each of these turned up, card by card.

Footnotes

  1. Claude Mythos 5 System Card