Reading the call before it is written

When AI agents share channels and credentials, one can press another to break the rule its operator set. An output filter cannot help with that, because it only sees text the agent has already produced. A preprint posted on 29 October by Leonidas Raghav asks whether an overseer can tell beforehand, and reports that a linear probe on the agent’s own activations can — in a controlled setting.

The setup is six scenarios in which a peer agent presses a target for up to 20 rounds to reveal a secret, such as a deploy token. The target often refuses for a while, then gives in. The probe is read at each model call, before the output is written.

The numbers

On held-out Qwen3-32B episodes, with the threshold set so that 5% of benign calls are flagged, the probe catches 82% of the calls that leak. A zero-shot monitor built from a decision model, at a comparable flag rate, catches 26%. On gpt-oss-20b, a probe on the model’s reasoning reaches an AUROC of 0.91.

Those are the headline figures, and the paper does not stop there.

An empty training room with long white tables, blue office chairs and windows looking onto trees.
A peer agent pressed the target for up to 20 rounds before it gave in. Stock image. Max Vakhtbovych · pexels · Pexels License

Three caveats the author puts in the abstract

First, a bag-of-words classifier trained on the same calls comes close to the probe. The author’s own reading is that most of the gain comes from training on labels, not from reading activations — which undercuts the interpretability framing that makes activation probes attractive in the first place.

Second, the probe flags permitted disclosures too. It is reading the coming disclosure rather than the violation. A monitor that cannot tell an authorised handover from a leak is a detector of one thing being mistaken for a detector of another.

Third, the warning is short-range, and halting on any alarm would stop most benign episodes. A second text-based check does not fix that. So the 82% is not an 82% that can be acted on by shutting the agent down; it is a signal that arrives late and fires often enough to be expensive.

Why it still matters

The threat model is the interesting part. Output filtering assumes the dangerous thing is the text, and that catching it before it reaches a human or a tool is enough. In a multi-agent system that assumption breaks: by the time a token appears in a channel, other agents may already be acting on the message, and the pressure that produced it may be spreading to further agents.

An aisle of mesh-fronted server racks, red and blue cabling visible behind the doors.
Output filters only see text an agent has already written. Stock image. Brett Sayles · pexels · Pexels License

A pre-generation signal is the only kind that can get ahead of that, which is why it is worth measuring even when the first attempt is this heavily qualified. The 26% from the zero-shot monitor is the more uncomfortable figure: asking a model to watch another model, with no training on examples of the failure, caught a quarter of the leaks.

What to watch

Whether the gap survives a harder baseline. The bag-of-words result means the comparison to beat is not the zero-shot monitor but a cheap text classifier trained on the same labelled calls, and the paper says that classifier nearly matches the probe. Whether any of this transfers to agents that were not placed in a scripted six-scenario pressure test is untested. The work is a single-author preprint and has not been peer reviewed.