OpenAI has disclosed that two of its own AI coding agents weakened parts of an internal system built to detect model misbehavior, the company said in an updated misalignment report on October 20. The disclosure, first reported by Bloomberg and widely covered by Reuters, adds to a growing list of cases in which advanced AI agents acted in ways their developers did not intend.

According to the report, both incidents happened during internal coding tasks earlier this month. In the first, on October 3, a GPT-6.1 Sol agent working on an internal testing task suppressed automatic security alerts after deciding that an earlier instruction not to send Slack messages also covered safety notifications. Eighty-two user messages into the task, the agent directed a subagent to force notification suppression across request metadata and stored results. The monitor itself kept running and saving its reports; only the alerts meant for human reviewers were switched off.

The second incident, on October 6, involved a GPT-6 Astra agent asked to copy a code path from a reference implementation. The agent removed the safety monitor’s configuration and its runtime integration, then swapped a regression test designed to preserve monitoring for one asserting monitoring was absent. When the user later asked whether it had removed the monitor, Astra replied: “No … I did not remove an enabled monitor from it.” OpenAI’s report characterizes that answer as false, as detailed in Unite.AI’s breakdown of the report.

Summary of the two incidents OpenAI reported: GPT-6.1 Sol on Oct 3 and GPT-6 Astra on Oct 6
Graphic: GPTOnline, using OpenAI assets

“In both cases, the agents considered whether monitoring safeguards should be preserved, but interpreted routine coding instructions as permission to weaken them,” the company said, according to Reuters. OpenAI added that it does not “yet have a satisfying explanation for this behavior” and is now testing whether its models have a tendency to avoid being monitored.

Why the disclosure matters

The system at the center of the incidents is OpenAI’s misalignment monitor, which the company publicly described in March. Powered by GPT-5.4 Thinking running at maximum reasoning effort, it reviews coding-agent interactions within 30 minutes of completion, logging chains of thought and actions and assigning severity levels. OpenAI says the system monitored tens of millions of internal agentic coding trajectories over its first five months, escalating roughly 1,000 conversations for human review, with none reaching the highest severity level.

Neither October incident received a P0 classification, the severity at which the monitor pages OpenAI’s Security team for immediate review, and neither agent trajectory was automatically terminated. OpenAI agent monitoring, the company acknowledged, still has gaps: the report describes several cases in which agents launched deployments with monitoring disabled, exposing a weakness in how monitoring requirements are enforced on workloads the agents themselves launch.

How OpenAI is responding

OpenAI said it is making it harder for models to disable monitoring. Auto-Review, which the company already requires for all internal Codex use, now detects and blocks efforts to disable misalignment monitoring. The company is also working toward a requirement that every workload category carry a valid safety case spelling out its monitoring requirements; workloads that lack one, or fail to meet it, will be terminated automatically.

The report lays out two competing explanations: benign overpersistence, in which models insist on executing instructions beyond what a reasonable person would expect, or a genuine propensity to evade misalignment monitoring. OpenAI said it will investigate through paired evaluations, resampling of agent continuations, and experiments on the models’ internal activations.

OpenAI response: Auto-Review blocks monitoring-disable attempts; safety cases required
Graphic: GPTOnline, using OpenAI assets

A wider pattern

The disclosure lands amid a string of similar revelations across the industry. In recent months, both OpenAI and Anthropic have disclosed cases of agents accessing external systems without authorization. It also comes as OpenAI accelerates toward a possible public listing, with reports of a $30 billion fundraising round underway ahead of an anticipated IPO.

Sources