AI

California's Governor Wants a Kill Switch for Frontier AI Models

(7 days ago) · 5 min read · By Future Technology

Key takeaways

  • California Governor Gavin Newsom signed an executive order that could mandate a kill switch for frontier AI models
  • The order also establishes an AI safety council and new accountability standards for state contractors using AI in critical infrastructure
  • Newsom vetoed SB 1047 in 2024, making this a notable shift in his position on AI regulation
  • A practical kill switch for globally distributed AI models would be technically complex, likely limited to California-based access and state systems

California Governor Gavin Newsom signed an executive order on Friday that positions the state to take a more aggressive stance on AI oversight, including the potential to mandate a kill switch for frontier AI models. If you have been following the back-and-forth between California's legislature and its tech industry over AI regulation, this is a significant escalation. Newsom vetoed SB 1047 back in 2024, the bill that would have imposed safety requirements on large AI models, citing concerns about innovation. Two years on, he appears to have shifted his position considerably.

The executive order instructs state agencies to begin developing frameworks for AI oversight, including mechanisms that could allow authorities to shut down or constrain AI systems that pose risks to public safety. The kill switch language is the most eye-catching element, but the order also moves to create an AI safety council and requires state contractors using AI in critical infrastructure to meet new accountability standards.

What a Kill Switch Would Actually Mean

The term kill switch sounds dramatic, and it is designed to. But the practical implementation of such a mechanism for frontier AI models is genuinely complicated. Unlike a piece of hardware or a specific software deployment, frontier models are distributed across inference infrastructure, accessed via APIs, and increasingly embedded in downstream products that the original developer does not control. Switching off a model at the source does not necessarily stop every application built on top of it.

There is also the question of jurisdiction. California can regulate companies operating within the state and impose conditions on state contracts, but it cannot unilaterally shut down a model deployed globally via cloud infrastructure. What the kill switch provision likely means in practice is something more targeted: the ability to require companies to disable access for California-based users or state government systems in the event of a declared safety incident. That is less cinematic than the headline suggests, but it is still a meaningful lever.

Why This Matters After the SB 1047 Veto

The 2024 veto was a watershed moment for AI policy in the US. Newsom's decision to block SB 1047 was widely read as California siding with the tech industry over safety advocates, and it took significant wind out of the state-level AI regulation movement at a time when federal action was still stalled. The executive order does not undo that, but it does signal that the political calculus has shifted.

The future, in 3 minutes a day. The biggest tech story explained every morning, free. Get the briefing →

Several factors have changed in the past two years. AI systems have become meaningfully more capable and more widely deployed in consequential settings. Public awareness of AI risks has grown. And there have been enough high-profile AI-related incidents, including the military hallucination story that broke this week, to make the abstract risk arguments feel more concrete. Newsom has also reportedly been briefed extensively by both AI safety researchers and frontier lab executives, and the executive order reads like an attempt to thread a needle between those two groups rather than simply picking a side.

The Industry Response

Tech companies have so far responded with the predictable mix of cautious welcome and quiet lobbying concern. The AI safety council element is something many labs have said they support in principle. The kill switch language is more contested. Critics within the industry argue that vague emergency shutdown powers create regulatory uncertainty that could drive investment out of the state and that the mechanism is technically unworkable without clearer definitions of what constitutes a triggering safety incident.

Those are legitimate concerns, but they are not new. The same arguments were made during the SB 1047 debate, and they carry less weight in a political environment where even the companies themselves are publishing safety frameworks and proposing their own governance structures. The argument that regulation is premature becomes harder to sustain when the industry is simultaneously telling the world its own products need careful oversight.

What happens next depends largely on whether the legislature picks up the kill switch provision and translates it into actual statute. Executive orders set direction; laws create enforceable requirements. Watch this space.

Sources

More from Future Technology