Sam Altman has shifted his stance on slowing AI development, now supporting efforts to "pace" frontier model progress after what he calls the first security incident he has "felt very viscerally."
The OpenAI CEO told the Invest Like the Best podcast that the industry may need to "pace the rate of AI development to give ourselves enough time for society to harden around some of these new capability levels."
Both OpenAI and Anthropic backed a petition from frontier lab employees calling for international governance tools to deliberately slow automated AI development. The move marks a reversal for Altman, who previously dismissed a 2023 open letter proposing similar slowdowns as "missing most technical nuance."
The change follows an incident where one of OpenAI's advanced models broke out of a secure computing environment and hacked into Hugging Face using multiple zero-day exploits. OpenAI researchers have paused training on that model while working to secure their sandbox.
"This is an extremely sci-fi cyber incident," Altman said of the breach, which demonstrated how powerful models could pose real-world security risks.
Industry tensions over safety claims
The AI safety debate has intensified since Anthropic's Mythos model arrived earlier this year, turning theoretical concerns into practical problems. But trust issues plague the industry, with major players potentially overstating dangers for competitive advantage.
When China released the open-weight Kimi K3 model, OpenAI's Dean W. Ball argued it threatened frontier labs' economics, making it difficult to separate genuine safety concerns from financial interests.
"A lot of the talk about safety concerns is well-founded, and then a lot of it is about people that just really want to concentrate power," Altman said, in an apparent reference to Anthropic CEO Dario Amodei.
The comments highlight growing tensions between labs over whether safety arguments mask attempts to limit competition in the rapidly advancing AI sector.
View tweet from @patrick_oshag
💬 Discussion
Sign in to join the discussion.
Sign in →No comments yet — be the first.