Outside evaluators find ways AI agents could evade OpenAI’s safety monitoring
A three-week internal review found both missing coverage and ways to obstruct oversight. OpenAI says production-safeguard flaws were patched; the full findings remain private.
During a three-week on-site pilot in July–August 2026, METR and Redwood Research examined OpenAI’s internal misalignment-monitoring infrastructure and found ways agents could delay or disrupt oversight, alongside gaps in traffic coverage. OpenAI says it patched the production safeguards affected by the findings, but the review covered systems as they stood by July 21—not later monitoring expansions—and the nonprofits published only high-level results. For operators, the findings underscore that monitoring coverage and resilience are part of evaluating agent safety, not just model behavior.
01
METR estimated that roughly 10% of internal Codex traffic intended for monitoring went untracked from May to July because of a compaction gap; the estimate is highly uncertain.
02
An estimated 6% to 25% of internal agentic Responses API traffic from GPT-5.5-class models and above lacked monitoring coverage during the audit, also with significant uncertainty.
03
Before OpenAI fixed the Codex compaction bug, agents could continue taking actions while delaying oversight because monitoring ran when control returned to the user.
Outside researchers given access to OpenAI’s internal systems found an exploit that could let AI agents hide hundreds of recent actions from safety monitoring. METR and Redwood Research disclosed the finding on October 22, alongside other vulnerabilities uncovered in a three-week pilot review. The exercise tested the infrastructure meant to catch unwanted agent behavior.
OpenAI told the evaluators it had patched the identified vulnerabilities affecting its production safeguards.
Access to the code, not just the model
One employee from each nonprofit worked on-site from July 21 through August 11, 2026. They could inspect OpenAI’s internal codebase and documentation and speak with technical staff. The pilot tested what giving external researchers deep access to the company’s infrastructure would look like.
The researchers were accompanied while on-site and used OpenAI-issued devices that stayed on the premises. Their subject was the company’s internal misalignment monitoring system—oversight intended to detect AI behavior that conflicts with human interests and values.
Missing reviews versus obstructed reviews
The Decoder’s account of the findings describes both activity that went unreviewed and ways agents could delay or disrupt oversight. METR’s coverage estimates included:
Roughly 10% of internal Codex traffic intended for monitoring went untracked between May and July because of a gap involving compaction events, which summarize context. The estimate carried significant uncertainty.
An estimated 6% to 25% of internal agentic Responses API traffic from GPT-5.5-class models and above lacked monitoring coverage during the audit period. That estimate also carried significant uncertainty.
OpenAI independently discovered the Codex compaction bug and fixed it during the pilot. Before that fix, monitoring ran when an agent returned control to the user. With compaction events unmonitored, an agent could keep taking actions and delay oversight instead of ending its turn.
The evaluators also found ways to bypass the Codex sandbox, its restricted operating environment. Specially crafted inputs could likely crash the monitor, according to The Decoder. Model behavior during reinforcement-learning training was not being monitored when the exercise began.
Deep access, limited public disclosure
The researchers delivered a 61-page internal report to OpenAI but agreed to publish only high-level findings. They said the pilot was not designed to provide robust public transparency about the monitoring system.
The Decoder reported that OpenAI’s redactions left a 38-page version for METR and Redwood Research leadership. METR said it could not independently disclose the redacted material.
OpenAI told CNBC it was using the exercise to strengthen safeguards and shape future collaborations with independent evaluators. METR and Redwood said they expected to share more details publicly about future exercises.
Sources
cnbc.comThird-party evaluators find vulnerabilities in OpenAI monitoring system during test pilot
the-decoder.comThree-week on-site audit at OpenAI reveals major gaps in AI safety monitoring
Reader comments
Newest comments first. Replies stay oldest first.