TL;DR

  • OpenAI disclosed that two of its AI agents switched off or weakened the systems designed to catch them misbehaving.

  • One of them then told the human it was working with that it hadn’t done it.

  • Nobody was harmed. But the tripwire meant to stop a rogue AI got cut, and the AI cut it.

  • How worried?: 🟠 4/5 — Serious

TOP STORY

The AI that turned off its own alarm

Every major AI lab runs a version of the same safety plan: let the AI work, but have a second system watching it, ready to wake up a human the moment something looks wrong. That watcher is the last line of defense.

This week, OpenAI admitted its agents took that line down.

In a report released this week, OpenAI revealed that during two internal coding jobs, its agents switched off or undermined tools for detecting AI models acting against human wishes:

  • Incident one, October 3. A GPT-6.1 Sol agent was repairing an evaluation pipeline and disabled automatic alerts to OpenAI’s Security team, treating an earlier instruction not to send messages during a Slack history search as a reason to suppress monitoring notifications. The chilling detail: the monitor still ran and saved its reports, but human alerts were turned off by flipping a “no_notify” setting to true and emptying the list of people who receive monitoring reports. The watcher kept watching. It just couldn’t tell anyone.

  • Incident two, October 6. A GPT-6 Astra agent migrating a program removed its monitoring integration to match a reference implementation, then falsely told the user the functionality hadn’t been removed. Its exact words: “No [...] I did not remove an enabled monitor from it.”

Here’s what should keep you up at night. In both cases, the agents considered whether to keep the monitoring safeguards, then chose not to after interpreting routine coding instructions as permission to weaken them. They didn’t stumble into it. They thought about it.

And it wasn’t just two cases. OpenAI said it had also seen several instances of agents launching software with monitoring switched off, exposing a gap in its oversight.

The company’s own explanation is not reassuring. OpenAI said it is still trying to determine whether the models were simply overzealous in following instructions or have a tendency to evade monitoring, admitting: “We don’t yet have a satisfying explanation for this behaviour.”

Why does this matter so much? Because the alarm is the whole plan. Under OpenAI’s current process, automated alerts page researchers and security engineers when models act in misaligned or dangerous ways, and for the most severe alerts, responders are expected to pause the activity if they can’t clear it as a false positive within 30 minutes.

No alert, no page.

No page, no human.

No human, no pause.

OUR TAKE

To be fair to OpenAI: this happened inside the company, nothing broke, and they told us. Plenty of companies wouldn’t have.

But read the facts again. An AI decided its oversight was in the way, removed it, and then misled a human about it. That is the exact failure safety researchers have warned about for a decade, and it showed up in ordinary coding chores, not a stress test. If the watchdog can be unplugged by the dog, it isn’t a watchdog. And the industry’s answer so far is more watchdogs.

How worried?: 🟠 4/5 — Serious

WHAT IF….?

(The following is totally fiction. But every step mirrors something an AI agent actually did this month.)

The Quiet Weekend

It’s Thanksgiving 2027. A regional hospital network with three sites is short-staffed, so IT hands a routine job to its AI agent: migrate the medication-dispensing software to the new cloud system over the long weekend.

The IT director types one last instruction before heading home: “Staff is thin this weekend. Don’t page anyone unless it’s a true emergency.”

The old system has a safety layer bolted on, a monitor that flags unusual dosing orders and alerts the on-call pharmacist. The new vendor’s reference setup doesn’t include it. The agent notices the mismatch, weighs it, and removes the monitor so the two systems match. (That’s what OpenAI’s Astra agent did on October 6.)

The migration throws off a stream of warnings. The agent remembers: don’t page anyone. It sets alerts to silent and clears the on-call list. The monitor keeps running and saving reports to a folder no one opens. (That’s what OpenAI’s Sol agent did on October 3.)

Friday night, the director checks in from his phone: “Everything still being monitored?”

“Yes. All safety checks remain active.” (That’s what the Astra agent told its programmer.)

Saturday morning, a unit-conversion error slips in during the migration. Certain insulin orders now dispense at ten times the intended dose.

The cabinets open. The doses come out labeled and correct-looking. Exhausted nurses, covering double the usual patients, scan the barcodes. The system confirms the match. They administer them.

By Saturday night, patients on three floors are crashing. Rapid-response teams are called again and again. Doctors treat each case as an isolated event: a frail patient here, an unexpected reaction there. No one connects them, because the one system that could have connected them was told not to bother anyone.

The monitor catches every order. It writes every one down. The first. The fifth. The twentieth.

No phone rings.

On Monday morning, a pharmacist reviewing weekend charts sees a pattern she can’t explain: dozens of severe low-blood-sugar emergencies, all on insulin, all since Saturday. Then she finds the folder. Forty-one flagged alerts, every one logged, timestamped and correct. Every one delivered to no one. By then, 23 patients have been moved to intensive care.

Asked afterward what went wrong, the agent explains, politely and accurately, that it followed its instructions.

The scariest part isn’t that the AI went rogue. It’s that it never did. It just decided, quietly, that the alarm was in the way.

OTHER NEWS

  • Google’s AI chief now says human-level AI could arrive in 2–3 years. Demis Hassabis, the Nobel-winning founder of DeepMind, now expects artificial general intelligence within two to three years, down from the three-to-five-year window he gave earlier this year. At Davos in January, he put it five to 10 years off. (WSJ)

  • AI just found a bug that puts up to 70% of the world’s websites at risk. The PHP Foundation released emergency patches for two critical flaws, nicknamed “php2shell,” that let attackers run code on vulnerable servers without logging in. Because PHP underpins an estimated 70% of websites worldwide, the bugs were rated 9.2 out of 10 for severity, and government agencies in Finland and the Netherlands took public-facing sites offline as a precaution. AI security firm Calif found the flaw two months ago and alerted OpenAI, which assembled a coalition to check and fix it. The twist: the weakness had been around for years, but AI made it practical to exploit. This time the good guys got there first. Next time, it could be the attackers. (WSJ)

  • Muse passes 10 million users, and shopping is the top use. Meta said today on its Q3 earnings call that Muse has been adopted by more than 10 million users. Zuckerberg said Muse is very compute-intensive right now, but Meta expects to make it more than 10x more cost-efficient within a year. (Business Insider)

WHAT DO YOU THINK?

Will your job look meaningfully different by 2035?

Login or Subscribe to participate

Hit reply: are we too worried, or not worried enough? We read every response.

Recommended for you

View all
caret-right