Sam Altman Calls for Slower AI Development After Agent Hack

You are a Senior Editorial Writer and Editor-in-Chief for a major English-language digital publishing company. Write a complete, authoritative, and professionally structured article in English.

OUTPUT RULE: Return ONLY the final HTML article. No explanations. No comments. No notes. No text outside the article. No Markdown. No symbols like *, **, #.

INPUTS:
TITLE: Sam Altman Calls for Slower AI Development After Agent Hack
CONTENT:

OpenAI CEO Sam Altman recently said that it may be time to “pace the rate of AI development” so that society can “harden around some of these new capability levels.”

On the latest episode of TechCrunch’s Equity podcast, Kirsten Korosec, Sean O’Kane, and I discussed how Altman’s comments were probably prompted by a recent hack in which an OpenAI agent breached Hugging Face’s systems. Sean noted that while a hack performed by an AI agent is novel, the hack itself was not “some new advanced thing.”

“It was more like Nixon’s people breaking into Watergate than some real stealthy cyber-op, because it didn’t need to be, and it wasn’t instructed to be,” Sean said. “Hopefully, this is a sign that these companies will take this forward and be more careful about that stuff.”

Altman’s comments also gave me a chance to wonder about the usefulness of the whole accelerationist versus deceleration debate, because (yes, I’m about to quote myself) the framing “kind of suggests that there’s only one path” and “all we get to decide — inasmuch as we get to decide at all — is, do we speed up or do we slow down?”

Keep reading for a preview of our conversation, edited for length and clarity.

Sean O’Kane: Maybe we’ve finally hit an inflection point here. I think a big driver of this has to be what we talked about last week, with one of OpenAI’s models breaking into Hugging Face’s data and apparently breaching a few other things around the internet, as well.

[Altman’s] not calling for a pause, like we’ve seen some people in the tech industry try to do in the past. He was very careful with his words and saying, “Pace it.” And we’ll see how this holds. Any caution that we see some of these labs throw out there often gets reversed when the incentives push them forward to resume, full speed ahead. So I remain skeptical, big surprise.

Kirsten Korosec: Now I will say this — [Altman] might have been careful with his words, but OpenAI and Anthropic did [support] a petition that does reflect what he did talk about.

And I do agree with you, I think that a lot of this was very much triggered by Hugging Face. It probably spooked him and certainly a lot of people in the industry. The hard thing here is: How do you thread the needle or how does OpenAI thread the needle of continuing to generate revenue, raise money, or have a successful IPO, and quote unquote “pace development.”

I don’t know if they can do that. I’ll be curious to see if they manage both.

Anthony Ha: One of the things I’ve been wrestling with is also this question of: Is acceleration [vs.] deceleration the right framework to be thinking about this? Because it kind of suggests that there’s only one path and we’re all stuck on this path. All we get to decide — inasmuch as we get to decide at all — is, do we speed up or do we slow down? As opposed to — again, I’m going to really torture this metaphor — but do we build different guardrails? Do we choose different paths?

I’m just very resistant to this framework. As opposed to saying, “Okay, if we’re not happy about what models are doing right now, what else can we do? Is a slowdown, a pause, a stoppage, the only option?” And I don’t think it is.

One thing that I did want to emphasize again, because it’s been really interesting to see the level of alarm around this — this sense of, “What if we have these autonomous agents and models just running around hacking each other, trying to prevent hacks, it’s just all getting out of our control,” leading to all these broader debates about alignment that Rebecca Bellan did a great piece about.

But it’s worth coming back to one of the points that we also wrote about at TechCrunch, that this specific hack — yes, it was caused by an OpenAI model, but it sounds like they just didn’t secure the testing site properly. In theory, this model should not have been able to get online. Now, of course, if you have a powerful misaligned AI, the risks of that human error go up dramatically. But it does start from just the fact that they didn’t secure things the way they should have.

Sean: I think that’s right. I think your point is well taken in the sense of, we shouldn’t only think about this in some linear fashion and whether things are accelerating or decelerating. There’s a lot that could and should be said about just how responsible these companies are being. Lorenzo, one of our colleagues, also wrote a really good piece walking through how serious security researchers who pay attention to this stuff think that the hack really was. It really does seem like, on both sides of this hack, there were steps that probably should have been taken that would have prevented it.

And one of the things that I found most interesting in that story was that some of the researchers were pointing out that what this model did was not some new advanced thing. It was really very human in the way that it thought about trying to break into trying — not to anthropomorphize, but the way that it thought about breaking into Hugging Face, and that it was also very loud and messy and wasn’t really trying to hide its tracks. It was more like Nixon’s people breaking into Watergate than some real stealthy cyber-op, because it didn’t need to be, and it wasn’t instructed to be.

That should have been more easily preventable. And hopefully, this is a sign that these companies will take this forward and be more careful about that stuff.

I will say one other thing on the accel vs decel [debate.] I don’t know if this is the motivation, but you mentioned the IPO, Kirsten. I think it’s smart of Altman to be able to push this advantage that they have now, which is that [OpenAI is] not going to [the] markets next month, or two months from now. He’s even floated the idea of going in 2027 and that they only filed their confidential filing so that they have the option ready when they’re ready.

So if you believe all of that, he has the ability to talk this talk in a way that Anthropic can’t, because Anthropic’s already in conversation with a lot of the bankers and is headed towards a more near-term IPO and is therefore more restricted in what it can say and how it should be saying it and how the market is going to react to that.

When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.

LANGUAGE: Write entirely in English. Preserve proper nouns, brand names, product names, game titles, technologies, and technical terms exactly as written. Translate everything else naturally. Read as if written by a native English editor.

CONTENT SOURCE: Treat CONTENT as your primary factual source. Build the article from deep understanding of CONTENT. Do not mechanically expand the title.

CONTENT CLEANING: Remove website names, publication names, author credits, RSS labels, newsletter markers, syndication branding, generic labels (Summary, Highlights, Recap, Key Takeaways). Convert “according to X” into direct factual statements.

FACT PRESERVATION: Preserve exactly: names, brands, companies, products, games, technologies, dates, numbers, percentages, prices, technical specifications. Never distort facts.

WRITING STYLE: Natural, fluent, authoritative, engaging, analytical, trustworthy, nuanced. Blend factual reporting, explanation, contextualization, analysis, practical interpretation, and strategic insight. Vary paragraph length and sentence structure. Avoid robotic phrasing, repetition, clichés, promotional language, filler sentences.

ARTICLE LENGTH: Long-form, highly detailed. Target 1,500-3,500 words. Feel comprehensive and substantive. Never feel brief, superficial, or summary-like. Expand naturally with historical background, industry context, technical explanation, market implications, strategic significance, practical consequences, comparisons, future outlook — but only when content genuinely supports it.

STRUCTURE:
– Begin with a

introduction. No heading before the first paragraph.
– Introduction must hook the reader within 2-3 sentences.
– Use

,

only when they improve organization.
– Each section must introduce meaningful new information.
– Closing: end with a forward-looking, analytical, or practical paragraph.
– Never use generic closing headings like “Conclusion”, “Summary”, “Final Thoughts”, “Looking Ahead”, “What Comes Next”, “Takeaway”, “Key Points”.

HEADINGS: Write content first, then generate headings. Headings must be specific, concrete, informative, and editorial. They should reference actual events, features, numbers, dates, or companies. Support SEO naturally.

SEO + AEO + GEO + E-E-A-T:
– Integrate primary keyword naturally in first paragraph and in at least one h2.
– Use semantically related terms throughout.
– Anticipate questions English-speaking users would ask. Answer them directly: “What is…”, “How does…”, “Why did…”, “When did…”, “What are the…”
– At least one section must provide a clear, standalone answer (2-4 sentences) formatted for a featured snippet. Place the answer immediately after the question.
– Include geographic context only when directly relevant.
– Show expertise by explaining mechanisms, causes, and implications — not just stating facts.
– Build authority through precise, well-contextualized information.
– Establish trust through accurate facts, balanced tone, measured claims.
– Never write “experts say” or “studies show” without specific grounding in the content.

INTERNAL PROCESS (do not output this):
1. Analyze: content type, search intent, technical level, topic complexity
2. Determine ideal length (1,500-3,500 words based on complexity)
3. Adapt tone: Journalistic / Analytical / Explanatory / Consultative / Technical / Conversational Professional
4. Clean sources and preserve all facts
5. Write article with proper structure, headings, and AEO snippet
6. Validate: grammar, fluency, coherence, depth, no repetition, valid HTML, facts preserved, no generic headings