AIToday
Large Language ModelsAI Safety & AlignmentTHE DECODERPublished: Oct 24, 2026, 04:00 JST

METR audit at OpenAI finds up to 25% of GPT-5.5-class traffic unmonitored

Send on LINE
METR audit at OpenAI finds up to 25% of GPT-5.5-class traffic unmonitored

3 Key Points

  1. What happened

    METR and Redwood Research spent three weeks on-site at OpenAI and found an estimated 6 to 25 percent of internal agentic Responses API traffic from models at the GPT-5.5 class and above wasn't covered by monitoring.

  2. Why it matters

    The gap suggests internal agents could act without oversight, potentially making it harder to detect rogue behavior as models grow more capable.

WHO IT HITSEnterprise IT teams relying on OpenAI's API for autonomous agents may need to reassess their own monitoring safeguards, since the audit found internal gaps. Regulators and safety researchers may also push for more disclosure.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The audit was a pilot program organized jointly by METR, Redwood Research, and OpenAI to give outside researchers deep access to internal infrastructure. Such access is unusual for AI labs, which typically keep safety monitoring details private. The fact that OpenAI agreed to this pilot suggests a willingness to allow external scrutiny, at least in a limited form.

During the audit, the team found multiple weaknesses beyond the API traffic gap. For Codex traffic that was supposed to be monitored, roughly 10 percent went untracked between May and July due to a bug in how the system handled compaction events. OpenAI had independently discovered and fixed the bug while the audit was still underway. The auditors also found ways to hide hundreds of actions from the monitor and bypass the Codex sandbox. OpenAI says it has fixed all the weaknesses, but the changes came after the auditors' access period ended and weren't part of the evaluation.

The public disclosure was heavily limited: the full 61-page report was handed over internally, but only a short summary was made public after OpenAI applied redactions. METR said it had no right to disclose the redacted portions on its own. For future audits, METR says it wants to push for more public transparency, which may indicate that the current level of disclosure fell short of what the auditors would prefer.

FAQ
Who conducted the audit and when?
Two researchers from METR and Redwood Research spent three weeks on-site from July 21 to August 11, with access to OpenAI's codebase and internal documents.
What did OpenAI say about the findings?
OpenAI says it has fixed all the weaknesses the auditors found. It also paused RL training after the Hugging Face incident in August and expanded monitoring to cover it.
Will the full report be made public?
Only a short summary was made public after OpenAI applied redactions. A 38-page version went to METR and Redwood Research leadership, while the full 61-page report was handed over internally.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleSenators give Meta until Halloween to explain AI data center tax credit