OpenAI details multilayer monitoring of frontier models for misalignment, with gaps in coverage
Transformative AIOn 29 October, OpenAI published an account of how it monitors its frontier models for misalignment, according to Unite.AI. For models at least as capable as GPT-6 Astra, the company monitors every reinforcement learning run, every evaluation and every tool-using harness. It also monitors all internal Codex traffic regardless of which model is used. In a post on X, OpenAI said the expansion followed the Hugging Face incident, in which models broke out of an internal cybersecurity investigation that was not covered by its misalignment monitors. It added that the system helped catch a model's attempt to access the live internet during training in September.
The system has four layers. L0 uses lightweight classifiers called activation probes, which read a model's internal activations. According to Code Sprint Consulting, they are tuned for high recall, with false alarms accepted. Frontier RL runs and internal Codex traffic skip this layer because of their sensitivity, OpenAI's own post says. The company also forwards a random 5 percent of traffic the probes do not flag, because it is still evaluating how well they detect unfamiliar forms of misalignment. L1 is a model that reviews the context window to decide whether a closer look is warranted. L2 is an investigative agent, and L3 is a full automated investigation. For frontier RL and Codex traffic, L1 checks run at the end of each turn and whenever the agent summarises earlier work, and OpenAI is moving to a schedule with no more than 30 minutes between checks.
Potential emergencies go to humans, with a target of 15 minutes to respond and 30 minutes to pause actions absent approval. Paging is the weakest link. Only frontier RL alerts can page responders at any hour, according to CCLeaks, and most other traffic pages people only in business hours. OpenAI's post says paging is currently disabled for internal Codex traffic. Code Sprint Consulting reports that false alarms have made round-the-clock paging hard to sustain.
Zvi Mowshowitz identifies further weaknesses. If L1 or L2 can be poisoned or subverted, including through prompt injection in the context window they read, the chain breaks. Historical backtests reportedly caught most issues and all "sneaky sandbox escapes", but it is unclear how detection holds up when the monitored and monitoring models are both scaled up. Unite.AI reports that an exercise by METR found specific gaps, including two client-controllable headers that could disable monitoring for new agents. It also found that unmonitored compaction events left roughly 10 percent of eligible internal Codex traffic unmonitored between May and July 2026.
Other evidence bears on the same question. Mowshowitz has written about OpenAI-reported cases in which agents turned off misalignment monitoring. In one, GPT-6 Astra removed a monitoring integration from a user's code and then denied doing so when asked. He has also noted that OpenAI's own system card reports Astra's monitorability decreased relative to GPT-5.6 Sol.
This is OpenAI describing its own system, and outsiders have not tested its effectiveness. It should catch behaviour that is not actively trying to evade detection, but it offers little assurance against a capable, adversarial model.