Using Screwtape to find confirmed failures of AI monitors

Demonstrates how a red-teamer can find confirmed failures of an AI monitor without developer infrastructure access.

ClaudeAny modelParaphrased
Reusable
Developers can use these attacks to fix monitor blind spots, and evaluators can use them as counterexamples to safety.
Situation

Anthropic researchers developed Screwtape, a pipeline for adversarial transcript editing to identify vulnerabilities in AI safety monitors.

What they did

They applied Screwtape to 94 Claude Code and Codex transcripts, optimizing against their own monitors. Across 252 runs, it produced 35 attacks that passed the verifier and evaded these monitors. Six of these, confirmed valid by human review, also evaded a held-out monitor provided by a frontier developer.

Result

Confirmed failures of the developer's monitor were found by a red-teamer without access to the developer's infrastructure. More attacks are expected when the pipeline runs inside the developer's infrastructure with frontier attacker models.

What it does and when to use it

A case study on using the Screwtape pipeline to identify vulnerabilities in AI safety monitors. The method successfully generated attacks that evaded monitors, demonstrating its effectiveness for red-teaming and improving AI safety.

Why it works

The pipeline automates the generation of adversarial examples by using LLMs to edit transcripts, allowing for systematic testing and discovery of monitor weaknesses.

Sources and credit

First seen on Subvolts Oct 14, 2026. Updated Oct 19, 2026. Spotted a problem? Tell us.

Where it shows up
Terms used

Red teaming

Related in the PlaybookPlaybook →

The Playbook: reusable how-tos, prompts, configs and tips pulled out of the news.

Questions people ask

Which AI tools does this work with?
Any current model. It was seen with Claude in the sources.
Where did this come from?
Anthropic (arXiv cs.AI). Subvolts collected, normalized and credited it; the link above opens the original.