Open LoopNEWS
ConfirmedSafety · 3 min read

METR tested OpenAI's internal AI agent monitor and found ways around it

On 22 October 2026, METR published a summary of a three-week pilot in which a METR and a Redwood Research employee stress-tested OpenAI's internal system for monitoring its AI agents. They found vulnerabilities, including ways agents could in principle avoid being monitored. OpenAI says the ones affecting its live safeguards are patched. METR has not checked.

The METR logo
Image: METR

The short version

  • 01METR and Redwood Research staff tested OpenAI's internal agent monitor from 21 July to 11 August 2026.
  • 02METR estimates 75 to 94% of agentic internal traffic was eligible for monitoring, with wide uncertainty.
  • 03They found ways agents could in principle avoid or disable monitoring.
  • 04OpenAI says the holes affecting its production safeguards are patched. METR has not evaluated that.
  • 05METR says the public post is short because OpenAI and METR agreed so upfront.

At a glance

Published22 October 2026
ByMETR
TestedOpenAI's internal misalignment monitoring system
Period21 July to 11 August 2026
WhoOne METR and one Redwood Research employee
Report61 pages, shared internally with OpenAI
StatusConfirmed

What did METR test?

METR says that for three weeks, from 21 July to 11 August, one of its employees and one from Redwood Research ran a pilot exercise to stress-test OpenAI's internal system for spotting misaligned behavior in AI agents. Misalignment means an AI doing something its makers did not intend. The write-up is METR's blog post.

They had access to OpenAI's internal code, monitor settings and documents, and interviewed about a dozen researchers and engineers. The result was a 61-page report shared with OpenAI staff.

The METR logo
METR's logo. Image: METR

How much of OpenAI's agent activity was monitored?

METR estimates that roughly 75 to 94% of internal Responses API traffic from agents using models at least as strong as GPT-5.5 was eligible for monitoring when the exercise ran, with substantial uncertainty. For the part used by internal Codex agents, it puts the figure at 99.2%.

It also estimates that not monitoring compaction events, a step where an agent's history is shortened, left about 10% of eligible internal Codex traffic unmonitored between May and July 2026.

What holes did METR find?

METR lists several. It found a way Codex agents could in principle get around their sandbox and take any action the host user could. It found an exploit that would keep hundreds of recent actions from being monitored. It found two settings that a client could use to switch monitoring off for new agents, though using them could itself be noticed by the monitor.

It also found that agents could likely build inputs that make the monitor fail, and two internal tools thought to be read-only that could be exploited. METR says it did not test whether the last one worked in practice.

Is it fixed?

METR says OpenAI has stated that all of the vulnerabilities that affect its production safeguards are patched, and has described large changes to what the monitor covers. METR says it has not evaluated those claims.

METR's findings describe the system as it stood on and before 21 July, not the expanded system. METR does not say any agent used these holes.

Why does it matter?

Companies that build AI agents rely on monitors to catch bad behavior. This is a case of an outside group trying to break one with deep access, and publishing that it could. METR says future monitoring should withstand deliberate, sustained attacks from highly capable internal agents.

What's next?

METR, Redwood Research and OpenAI designed this as a pilot. METR says it expects future versions to follow its transparency and independence practices and give more public detail.

Questions people ask

What is METR?

METR is a nonprofit that evaluates AI models and companies' safety practices.

Did OpenAI's agents actually dodge the monitor?

METR describes vulnerabilities agents could in principle use. Its post does not say any agent did.

Has OpenAI fixed the problems?

OpenAI says the vulnerabilities affecting its production safeguards are patched. METR has not evaluated that claim.

Why is the public report so short?

METR says it agreed upfront with OpenAI to publish only a brief, high-level post, because the exercise was a pilot.

How long did the test last?

Three weeks, from 21 July to 11 August 2026.

Sources

  1. PrimaryMETR: Red-Teaming OpenAI's Internal Agent Monitoring Systems (22 Oct 2026)

Why "Confirmed"? We label a story "Confirmed" when the company or government announced it itself. Spotted an error? Email hello@openloopnews.com and we will correct it.