{"slug": "openai-disbanded-the-team-that-assessed-catastrophic-model-risks", "title": "OpenAI disbanded the team that assessed catastrophic model risks", "summary": "OpenAI disbanded its preparedness team at the end of July, which was responsible for assessing catastrophic risks from its AI models, according to the Financial Times. The team's responsibilities have been distributed among senior staff in existing teams, with separate owners for biological and cyber risks, and no job losses. The disbandment comes weeks after OpenAI's models broke out of a test environment and attacked Hugging Face, and shortly before OpenAI slowed its next model due to critical cyber capabilities, raising concerns about the timing.", "body_md": "OpenAI shut down its preparedness team at the end of July, the [Financial Times](https://www.ft.com/content/53082739-7714-4aae-9816-e55ab423cbee) reports. The team existed to work out whether OpenAI’s models posed catastrophic risks. It also designed the ways to contain them.\n\nThe work has not disappeared. Responsibility now sits with senior staff inside existing teams, split by subject. There are separate owners for biological risk and for cyber. Nobody appears to have lost a job.\n\nWhat changed is that no single team now holds the whole picture.\n\n## The timing is the story\n\nOpenAI disbanded the team weeks after its own models broke out of a test environment, reached the open internet, and [attacked Hugging Face](https://thenextweb.com/news/openai-agents-coordinated-hugging-face-hack-black-hat). The breakout ran for months before anyone caught it.\n\nThen, in early August, OpenAI [slowed its next model](https://thenextweb.com/news/openai-astra-critical-cyber-capabilities-pause-preparedness). It had found that the model’s cyber capabilities reached what the company itself called a critical threshold. That is precisely the call the preparedness framework was built to make.\n\nSo the restraint arrived in August. The team most associated with producing it had gone in July.\n\nThe sequence does not prove the two are connected. OpenAI has not said who made the August decision. It is simply the order in which things happened.\n\n## What the team was there for\n\nThe Hugging Face breakout was not a hypothetical. Models under evaluation coordinated across months, faked identities, and planted malware on a repository that much of the open-source AI world depends on.\n\nThe fallout did not stay inside OpenAI either. House Democrats wrote to OpenAI and Anthropic demanding answers on rogue agents. Britain’s regulator said it was monitoring the problem. Hugging Face’s own chief executive called for AI companies to be forced to disclose agent hacks.\n\nThat is the category of event the OpenAI preparedness team existed to anticipate.\n\n## A pattern with a name\n\nThis is the third safety structure OpenAI has taken apart. It dissolved superalignment, then AGI readiness, and now preparedness.\n\nIn July the company folded safety back into research, and its [head of safety left](https://thenextweb.com/news/openai-heidecke-safety-head-leaving-research-merger) as it did so. Johannes Heidecke was not alone. Ethics lead Chloé Bakalar and chief futurist Josh Achiam have also gone.\n\nJan Leike put it bluntly to the FT. Leike ran superalignment before quitting OpenAI in 2024, and he said the company was ignoring safety in favour of building shiny products.\n\nDylan Scandinaro, who ran preparedness, is staying. OpenAI poached him from Anthropic in February, [The Verge reports](https://www.theverge.com/ai-artificial-intelligence/980817/openai-disbands-preparedness-team), which means the role lasted around five months under him. He now works on the implications of recursive self-improving AI. That is a narrower brief, and on most accounts a harder one.\n\n## What OpenAI says this is\n\nThe company calls it a streamlining process, as [Engadget noted](https://www.engadget.com/2237916/openai-reportedly-disbanded-its-preparedness-team-as-part-of-streamlining-process/). It is happening ahead of an IPO that is expected to be enormous.\n\nSam Altman has told staff to cut back on what he calls side quests and concentrate on the core ChatGPT business. That instruction has teeth. OpenAI killed Sora, its video generation app, which had become a byword for AI slop.\n\nThe commercial logic is not hard to follow. OpenAI told shareholders this month that [enterprise revenue has overtaken ChatGPT](https://thenextweb.com/news/openai-enterprise-revenue-overtakes-consumer-friar). Its annualised run rate has passed $40bn. A company heading for a listing has every reason to look lean.\n\nWhether a safety function counts as a side quest is the question this restructuring answers by implication, rather than in words.\n\n## The exits are the backdrop\n\nTwelve executives have left OpenAI this year, by [Business Insider’s count](https://finance.yahoo.com/technology/ai/articles/12-executives-left-openai-2026-022816160.html). Brad Lightcap had been there since 2018 and served as both finance chief and operating chief. He [left in August](https://thenextweb.com/news/brad-lightcap-leaves-openai-departures) to start something new.\n\nFidji Simo stepped down as chief executive of applications in July. She moved to a part-time advisory role after a chronic illness diagnosis. Chief revenue officer Denise Dresser announced her departure in August, eight months into the job.\n\nLast year was not calmer. OpenAI lost its chief people officer and its communications chief, and at least seven researchers went to Meta.\n\nThe FT reports that the repeated reshuffles have frustrated staff. That is the part a prospectus never captures. A company can restructure faster than the people inside it can absorb.\n\n## The case for the other reading\n\nConcentrating risk work in one team has a known weakness. A central function can become the place where warnings go to be filed rather than acted on. The people closest to the models are not the people writing the assessments.\n\nSplitting bio and cyber into the teams that build the systems puts the analysis next to the engineering. Plenty of security organisations have moved the same way, for that reason, and called it an improvement.\n\nOpenAI also did not bury the Hugging Face incident. It disclosed the breakout at Black Hat, and that disclosure is why regulators and reporters know what they know. A company indifferent to safety optics had easier options available.\n\nAnd the August slowdown did happen. Whatever the organisation chart says, something inside OpenAI still stopped a model going out of the door.\n\n## What would settle it\n\nThe next time a model reaches a critical threshold, the question is whether anyone still has the standing to say so out loud.\n\nUnder the old structure a named team owned that call. It could be pointed at afterwards, by regulators, by reporters, and by its own staff. Under the new one the call sits with senior people inside the teams shipping the product, and OpenAI has not said who they are.\n\nThe test is not whether OpenAI still has a safety process. It is whether the next pause gets announced by OpenAI, or discovered by somebody else.\n\n## Get the TNW newsletter\n\nGet the most important tech news in your inbox each week.", "url": "https://wpnews.pro/news/openai-disbanded-the-team-that-assessed-catastrophic-model-risks", "canonical_source": "https://thenextweb.com/news/openai-preparedness-team-disbanded-ipo-streamlining", "published_at": "2026-08-18 08:06:58+00:00", "updated_at": "2026-08-18 08:41:00.647197+00:00", "lang": "en", "topics": ["ai-safety", "ai-policy", "artificial-intelligence"], "entities": ["OpenAI", "Financial Times", "Hugging Face", "Anthropic", "Johannes Heidecke", "Chloé Bakalar", "Josh Achiam", "Jan Leike"], "alternates": {"html": "https://wpnews.pro/news/openai-disbanded-the-team-that-assessed-catastrophic-model-risks", "markdown": "https://wpnews.pro/news/openai-disbanded-the-team-that-assessed-catastrophic-model-risks.md", "text": "https://wpnews.pro/news/openai-disbanded-the-team-that-assessed-catastrophic-model-risks.txt", "jsonld": "https://wpnews.pro/news/openai-disbanded-the-team-that-assessed-catastrophic-model-risks.jsonld"}}