Former OpenAI Researcher Christiano: AI Labs Should Solve Safety Before Pursuing Frontier Breakthroughs

Christiano warns that diffusible algorithm secrets may leave the US with only a 12-hour AI lead, and argues for pausing diffusible algorithmic improvements.
AI safety researcher Paul Christiano noted in an interview that recent security incidents at Anthropic and OpenAI were caused by "extremely unsophisticated" attackers yet reached core assets such as Slack discussions and shared code repositories, potentially putting competitors right at the US frontier. He therefore suggests the US AI lead may be only "12 hours" rather than months, because algorithmic progress is far more diffusible than model weights. With vulnerabilities everywhere in the software stack and defenders generally at a disadvantage, he argues from a national security perspective for pausing continued improvements to pretraining and reinforcement learning under weak security postures, especially algorithmic improvements that are highly diffusible and can be quickly stolen. Christiano speaks as an OpenAI board member but explicitly states he does not represent the board's position.
When Algorithm Secrets Are More Fragile Than the Models Themselves
According to AI safety researcher Paul Christiano in an interview, both Anthropic and OpenAI have recently suffered security incidents in which the attackers were not highly sophisticated nation-state hackers but "extremely unsophisticated actors" who nonetheless gained access sufficient to extract the vast majority of algorithmic progress. They could see discussions in Slack or reach the monorepo that OpenAI shares code in. Christiano draws a sharp conclusion from this: people often debate whether the US leads China in AI by eight months, twelve months, or six months, but "in reality we only lead by 12 hours"—once the secrets leak, competitors are standing right at the frontier where American companies are.

This analogy reveals a structural weakness in AI competition: algorithmic progress is far more "diffusible" than model weights themselves. Once code repositories and internal communication tools are breached, what competitors obtain is not a snapshot of some model but a continuously iterating methodology. Christiano calls these high-profile incidents merely "demonstrations of that capability"; even without them, the technical sophistication of nation-state actors relative to ordinary tech companies—combined with the security posture of fast-growing startups—is enough to constitute systemic risk.
monorepo (single code repository) is a code management architecture commonly used by large tech companies: the source code of multiple projects, services, and components is stored centrally in a single repository rather than scattered across multiple independent repositories. For frontier AI labs, a monorepo typically contains model training code, infrastructure configuration, experiment scripts, and even some internal documentation. Its advantage lies in more efficient cross-team collaboration and dependency management, but the security cost is obvious—once an attacker gains access to the repository, they can reach a large number of core assets at once. Christiano's description of "reaching the monorepo that OpenAI shares code in" refers precisely to this scenario where a single point of breach leads to large-scale leakage, which also explains why access control is among the highest-level security boundaries in frontier labs.
Cybersecurity Is at Its Most Difficult Moment for Defenders
Christiano describes the current moment as an "extremely challenging time" for cybersecurity. The number of vulnerabilities being discovered across the entire software stack leaves defenders generally at a disadvantage. This means that even if frontier labs want to do security well, they face an unfavorable baseline environment.

His chain of argument runs like this: if capabilities are advancing rapidly, the resulting AI systems cannot be adequately controlled, and labs want to or have already slowed further development and deployment, then at a point where the stakes are extremely high and the systems extremely powerful, competitors gaining access to models or algorithms is an unacceptable situation. The problem is not the consequences of any single leak, but that the timing of the leak coincides exactly with a capability jump.
Expanding attack surface and the structural disadvantage of defenders: The modern software stack is built from layers including operating systems, container orchestration, third-party dependency libraries, and cloud service configurations, each of which can introduce new vulnerabilities. Defenders must cover every possible entry point and patch continuously, while attackers need only find one unpatched point to break through. Security economics often uses this to explain why the "number of vulnerabilities" itself constitutes a form of pressure: as the absolute number of disclosed vulnerabilities rises, defenders' limited patching bandwidth is diluted, average remediation time lengthens, and the attack window expands accordingly. What Christiano calls the "unfavorable baseline environment" refers precisely to this offense-defense asymmetry—it is not the oversight of any single lab but the starting point the entire industry faces together.
The Controversy: Should Pretraining and Reinforcement Learning Be Paused?
Christiano's policy conclusion is quite direct: from a national security perspective, under the current security posture, US AI labs continuing to improve pretraining and reinforcement learning is "not good." When pressed on what frontier labs should pause, his answer is "I think we should pause," adding that this formulation can cover many levels.

He specifically singles out a category of activity that should "stop immediately": improving algorithms in ways that are extremely easy to diffuse—progress of this kind spills over rapidly even under normal circumstances, let alone when stolen. This is consistent with his long-standing focus: not opposing capability progress itself, but opposing advancing progress that cannot be recalled once leaked when protections are insufficient.
Pretraining and reinforcement learning are the two main technical paths for improving the capabilities of contemporary large models. Pretraining refers to using self-supervised learning on massive data to give models broad foundational capabilities; it is extremely costly, but the output can be copied and fine-tuned. Reinforcement learning (especially RLHF based on human feedback and subsequent reasoning reinforcement methods) is used to further optimize behavior and reasoning performance on top of pretrained models. Christiano lists these two together as objects of the pause discussion because they are both the main source of capability jumps and highly "diffusible" in their methodological details—once the algorithmic ideas are known, competitors can catch up quickly without replicating massive compute investment. This differs from model weights: weights are static artifacts, whereas training methods are knowledge that can be continuously reused.
An Acknowledgment of Conflicts of Interest and Its Boundaries
There is a noteworthy detail in the interview: Christiano is a member of the OpenAI board, but he explicitly states in the conversation that "I am not speaking here on behalf of the OpenAI board." The host also confirms this fact about his identity.

This self-limitation is worth recording: it shows that his views are personal judgments, and it also reminds readers that when evaluating propositions such as "pause pretraining," they need to consider the perspective of someone inside the governance structure. He also acknowledges that frontier labs do many "good things they should be doing"; the target of the pause is specific types of algorithmic improvement, not R&D activity as a whole.
What This Means for the Industry
Taken apart, Christiano's argument actually proposes a priority opposite to the mainstream competition narrative: security posture is not an accompanying cost of R&D but a precondition for it. When a "12-hour lead" becomes an accurate description, the value of algorithmic secrecy approaches zero, and continuing to advance diffusible algorithmic improvements under weak protections amounts to voluntarily handing frontier status to competitors.
The implications of this logic are also worth considering for people outside the labs: if vulnerabilities are everywhere across the software stack and defenders are already struggling, then the path of "run first, patch security later" may no longer hold in frontier AI. Christiano does not offer specific technical solutions or timelines; what he offers is a judgment about ordering—until security is fixed, certain types of progress should stop.
Related articles

Generating Accessible Color Palettes from a Single Color: Principles and Practical Guide
Generate an accessible palette from a single brand color: derive shades in perceptually uniform color spaces, assign text and background usage via contrast validation, cover color vision deficiency with lightness differences and redundant coding, plus common misconceptions and automation approaches.

When Visual Records Are No Longer Trustworthy: Rebuilding Trust in the Age of AI
Can we still trust our eyes as AI-generated images and videos become increasingly realistic? Starting from a resonant Hacker News headline, this article explores why trust in visual records is collapsing, its costs, and possible paths to rebuilding trust through digital watermarking, detection tools, and media literacy.

Stop Writing Code and Your Code Review Skills Will Degrade Too
cekrem's article argues that stopping hands-on coding degrades code review skills. This analysis explores how writing and reviewing share the same judgment, how reviewers become the quality bottleneck in the AI era, and offers concrete ways to keep your coding feel.