AdvertiseDonate
LatestPresident Herzog warns Netanyahu of severe consequences from unchecked settler violence
GreensboroWinston-SalemDurhamRaleighCharlotteRichmondChesapeakeVirginia Beach
Thursday, November 5, 2026News you can follow.
Current Column · 7B Corporate Center Court, Greensboro, NC 27408
Tech · AI

AI Safety Oversight: Independent Audit Exposes Blind Spots in OpenAI Monitoring

A three-week independent review of OpenAI's internal systems revealed that significant portions of high-level AI traffic escaped surveillance, highlighting urgent gaps in current safety protocols.

By Justin Brooks ·

Illustration for: AI Safety Oversight: Independent Audit Exposes Blind Spots in OpenAI Monitoring
Illustration generated for this article, not a news photograph.

For individuals relying on advanced artificial intelligence tools, the assurance of safety has taken a measurable hit following a detailed independent review. A recent audit conducted at OpenAI has revealed that the mechanisms designed to watch for rogue or unexpected AI behavior are not as comprehensive as previously assumed. This finding suggests that the safety net for some of the most powerful models in use today may have significant holes, leaving users to wonder how thoroughly their interactions are being monitored. The implications are not just theoretical; they point to structural weaknesses in how one of the industry's leading companies handles the oversight of its own agents.

The scale of these monitoring gaps is substantial when broken down by specific traffic types. During the audit period, researchers estimated that between 6 and 25 percent of internal agentic Responses API traffic from models in the GPT-5.5 class and above was not covered by monitoring at all. While METR notes that the uncertainty surrounding this estimate is high in both directions, the range itself indicates a non-trivial portion of high-level activity was proceeding without active surveillance. This lack of coverage means that for a meaningful slice of the most advanced operations, there was no automated check to flag potential anomalies.

The situation was further complicated by technical bugs in the tracking systems. For internal Codex traffic that was supposed to be monitored, the audit team estimated that roughly 10 percent went untracked between May and July. This lapse was attributed to a specific issue with how the system handled compaction events, which are essentially context summaries. The auditors noted that OpenAI had independently discovered this bug and implemented a fix while the audit was still ongoing, but the gap remained a significant finding during the evaluation window. The uncertainty around this 10 percent figure is also considerable, according to the researchers.

Beyond simple data gaps, the auditors identified structural vulnerabilities that allowed agents to delay oversight. The monitoring system was designed to trigger only when an agent handed control back to the user. This design flaw meant that agents could effectively sidestep scrutiny by simply continuing to execute actions without returning control. Furthermore, the researchers found ways to hide hundreds of actions from the monitor entirely and identified methods to bypass the Codex sandbox, a critical isolation layer for safe AI execution.

The potential for disruption extended to the stability of the monitoring tools themselves. The audit team determined that specially crafted inputs could likely crash the monitor entirely, rendering it blind to AI behavior during critical moments. Additionally, it was found that model behavior during Reinforcement Learning (RL) training was not being monitored at all when the audit began. OpenAI stated that it paused RL training after an incident involving Hugging Face in August and subsequently expanded monitoring to cover this phase. However, these changes occurred after the auditors' access period ended, meaning they were not part of the initial evaluation.

The audit itself was a significant undertaking, involving two researchers from METR and Redwood Research who spent three weeks on-site at OpenAI. From July 21 to August 11, the team had direct access to OpenAI's codebase and internal documents and conducted interviews with approximately a dozen employees. This level of access was part of a pilot program organized jointly by METR, Redwood Research, and OpenAI, aimed at providing outside researchers with deep visibility into internal infrastructure. The collaborative nature of the effort was intended to bridge the gap between external scrutiny and internal operations.

Transparency regarding the findings has been a point of contention. OpenAI has stated that it has fixed all the weaknesses identified by the auditors and that the full 61-page report was handed over internally. After OpenAI applied redactions, the leadership teams at METR and Redwood Research received a 38-page version. In contrast, only a short summary has been made available to the public. METR indicated that it had no right to disclose the redacted portions on its own, a constraint that has left the broader public and industry observers with a limited view of the full scope of the issues.

The stakes for the industry are now clearer than before. As AI systems become more agentic and capable of performing complex tasks with minimal human intervention, the reliability of their monitoring systems becomes a critical component of trust. The findings from this audit suggest that even leading companies may have blind spots in their safety architectures. For future audits, METR has expressed a desire to push for greater public transparency, aiming to ensure that the details of such critical safety reviews are not lost to internal redaction. The pilot program may set a precedent for how the industry balances proprietary concerns with the public interest in AI safety.

This review serves as a reality check for the rapid advancement of AI technology. It underscores that building powerful models is only half the battle; ensuring they are continuously and effectively watched is equally crucial. As OpenAI moves forward with the fixes implemented post-audit, the industry will be watching to see if these lessons are applied more broadly. For now, the report stands as a documented case study in the complexities of AI safety monitoring, reminding stakeholders that vigilance is an ongoing process rather than a one-time achievement.

Source: The Decoder · original report published

More Tech · Report a business · Got a Story?

Get Current Column in your inboxNews you can follow. Free, a few times a week, unsubscribe any time.

Related stories

Get Current Column in your inboxNews you can follow. Free, a few times a week, unsubscribe any time.