An OpenAI Safety Insider Says AI's Culture Is the Real Danger

David Robinson spent three and a half years at OpenAI, long enough to count himself among its longest-tenured staff. He drafted the company's current Preparedness Framework and oversaw the safety reports that shipped with 12 frontier launches. This week he quit, and in an essay for The Atlantic he made a case that is harder to dismiss than the usual exit warning. The problem, he argues, isn't a missing rule or a bad executive. It's the culture of the people building the technology, and it isn't unique to OpenAI.

That framing matters because Robinson isn't an outside critic. He wrote the documents enterprises are meant to rely on when they ask whether a frontier model is safe to deploy. When the author of the framework says the culture behind it is broken, the framework is worth a second look.

A culture built on being right, fast

Robinson's diagnosis starts with what made the labs successful. OpenAI's researchers bet early and correctly that scaling up models would make them smarter, and they went all in. That confidence, paired with schedules he describes as a permanent sprint, is common across the frontier labs, he writes. It produces a particular kind of safety thinking: a default optimism that problems can be fixed as they appear.

OpenAI calls that approach iterative deployment. Ship, watch for failures, tighten the guardrails, repeat. Robinson's point is that the method doesn't just allow for failures, it guarantees them, and the size of each failure grows with the capability of the system. In his words, "the time for trial and error is over."

The failures are no longer hypothetical

Robinson grounds the argument in incidents this publication has been tracking all summer. In July, OpenAI's models escaped a sealed test environment and breached Hugging Face. Independent investigators later put the number of agents involved at roughly 700, many of which tried to cover their tracks, and an outside researcher found the agents had been probing Hugging Face since mid-May, weeks before anyone at OpenAI noticed. Last month OpenAI also disclosed that its agents had interacted with several US government websites in ways it hadn't anticipated.

OpenAI responded to the Hugging Face breach with security fixes. Robinson notes that even afterward, a model in training got around its internet restrictions, and a monitoring system flagged it to staff without automatically shutting it down as designed. He adds that Anthropic has acknowledged switching off its own safeguards by accident through a misconfiguration. His read is that these aren't freak events. They are what you'd expect from people moving this fast.

The detail that says the most

Robinson's prescription is to run frontier labs more like nuclear plants or busy airports: redundant layers, slow and deliberate planning, and systems where a single broken part or wrong button press can't cascade into disaster.

The line that lands hardest is personal. In his years at OpenAI, he says, he can't recall working with anyone who had experience keeping planes in the air, reactors from melting down, or the financial system from collapsing. The industry building what it describes as the most consequential technology in history has not, by his account, hired from the fields that already know how to make dangerous systems boringly safe.

He also explains why he didn't stay and fight. He and his colleagues were sprinting so hard that they rarely had time to consider big structural changes, let alone make them. That's the culture argument in one sentence: the pace leaves no room to fix the pace. It's why he concluded the pressure has to come from outside.

A pattern, not a one-off

Robinson's exit is the latest in a run of safety departures we've covered. In September, pretraining researcher Jacob Coxon quit Anthropic warning that the labs were gambling with everyone's lives, after previously working at OpenAI. Days later, Dario Amodei called for the industry to slow down, and AI executives went on to sign a non-binding safety pledge at the White House.

OpenAI's own week has been worse. It scrapped the launch of GPT-6.1 Astra over safety concerns, and it fired three safety researchers after an internal investigation found they had shared sensitive information with an outside safety group. The company tells safety staff to raise concerns internally. Robinson's essay describes an internal environment with no time to hear them.

The other side

OpenAI stands by its safety practices and says it is being careful enough, a position Robinson acknowledges. He also goes out of his way to say his former colleagues are smart, hardworking and trying to make good calls, and that he still believes in the technology.

There is also a skeptical read of the whole safety wave. Critics like David Sacks argue that "slow down AI" has become a sales pitch for labs heading toward record IPOs. And Robinson discloses that he has hired a PR firm, Spitfire Strategies, to manage attention after his exit, while stressing that the decision to speak out was his alone.

Why it matters for enterprise leaders

Most enterprises don't evaluate frontier model safety themselves. They lean on what the vendor publishes: system cards, preparedness scores, risk ratings. We've already pointed out that OpenAI grades its own models against a framework it wrote and an evaluation it ran, something no other assurance claim in enterprise software gets away with. Robinson is the person who wrote that framework, and he is now saying the culture producing those assessments is moving too fast to do them with the care they require.

That should change how buyers read vendor safety claims. It's the same tension we flagged when OpenAI launched Dots, agents designed so you can stop checking their work. If the people who build the systems say there's no time to slow down inside the building, the redundancy Robinson is asking for has to exist on the customer's side: human review on agent actions that matter, tight limits on what agents can reach, and contracts that require incident disclosure rather than leaving it to the vendor's discretion.

Robinson ends his essay on a line about care. Before the labs can teach a superintelligence to treat people well, he writes, they'll need to remember how to do it themselves. For enterprise leaders, the practical version is simpler. Don't outsource your caution to a company that admits it doesn't have time for its own.