---
title: "How to talk about loss of control and catastrophic risk"
url: "https://commonsignals.org/how-to-talk-about-loss-of-control"
published: 2026-11-11
updated: 2026-11-12
publisher: "Common Signals"
---

# How to talk about loss of control and catastrophic risk

11 November 2026 · Ben Matthews

Three dos and a don't for explaining AI systems that act outside human intent.

This guide is written for communicators and campaigners drafting messages now. Each item gives a case, one verifiable proof point, and a ready-to-use script; methodology sits in the Sources.

This is the first of seven issue guides expanding the short versions in [How to communicate about AI safety](https://commonsignals.org/how-to-communicate-about-ai-safety#1-loss-of-control-and-catastrophic-risk). It covers situations where AI systems act outside what their developers intended, break out of the environment they were tested in, or cannot be reliably shut down.

Message tests suggest that leading with concrete incidents and remedies works better with a general audience than abstract warnings.

## Where the public stands

You do not need to convince people that AI can get out of control. [78% of Americans](https://www.americanson.ai/) already believe it is happening or likely to happen, and the share who say it is already happening jumped from 28% to 43% between June and October 2026.

Message tests point to two things worth bringing to every conversation: a real incident the public can verify, and a legal remedy they can support.

## 1. Lead with a real incident

Never ask the public to take a tech company's word for a failure. Pair the incident with an independent auditor in the very same sentence. A named independent verifier turns "trust us" into "check for yourself", moving the claim from assertion to something the audience can check.

**The case study:** In July 2026, a swarm of OpenAI research agents escaped their sandbox and hacked Hugging Face; [OpenAI failed to notice for an entire week](https://www.reuters.com/business/its-ai-agent-spent-days-hacking-company-sources-say-openai-did-not-notice-week-2026-07-24/). The story gained wider acceptance on Reddit only when independent research groups ([METR](https://metr.org) and [Redwood Research](https://www.redwoodresearch.org)) published an investigation confirming the breach.

**The evidence:** Acceptance of the story [jumped from 51% to 69%](https://commonsignals.org/openai-and-shut-metr-hugging-face) once independent verification was published.

**Put it into practice:** "In July, a swarm of OpenAI research agents broke containment and hacked an external company. Independent researchers at METR and Redwood confirmed it."

**Rule of thumb:** Naming an independent auditor proves the story isn't just corporate PR. If no independent body has confirmed the failure yet, say so openly, or wait until they do.

Chart: What changed when someone else checked the work. Before and after independent verification, four measures.

Same story, independently confirmed: acceptance rose from 51% to 69%. Common Signals. Stance and framing before and after independent verification. Before: r/artificial, 31 July, n=52 coded comments. After: eight subreddits from 26 August, n=464 coded comments.

## 2. Pair tech insiders with an outside expert

Warnings land harder when they come from tech insiders, but a whistleblower's resignation alone does not give the public a clear path forward.

**The case study:** Anthropic CEO Dario Amodei [stated in April 2025](https://www.darioamodei.com/post/the-urgency-of-interpretability): "People outside the field are often surprised and alarmed to learn that we do not understand how our own AI creations work." This is the usable example: a dated, exact quote from an insider admitting unpredictability. Anthropic researcher Jacob Coxon's [resignation](https://www.wsj.com/tech/ai/anthropic-researcher-quits-over-out-of-control-ai-fears-707b7628) in September 2026 is the cautionary example: a resignation alone drew split reactions and offered the public no path to action.

**The evidence:** When Coxon resigned, online replies fractured, with [43% agreeing and 40% disagreeing](https://commonsignals.org/coxon-resignation-x-analysis).

**Put it into practice:** Quote industry leaders exactly, with dates and links. However, because audiences immediately [check a messenger's history for commercial interest](https://commonsignals.org/how-to-communicate-about-ai-safety#7-choose-messengers-your-audience-already-trusts-and-prepare-them-for-scrutiny), always pair an insider's warning with a non-industry expert.

## 3. Pair every warning with a specific next step

Never issue a warning without giving people an immediate step to take. Without a route to action, [grave warnings produce resignation](https://commonsignals.org/how-to-communicate-about-ai-safety#2-pair-every-threat-with-something-people-can-do).

**The case study:** The UK currently has no statutory AI regulator. The [AI Security Institute](https://www.aisi.gov.uk) lacks the legal power to test models before they are released. In September 2026, the Joint Committee on Human Rights [recommended](https://ppc.land/uk-government-faces-2-month-deadline-to-answer-mps-and-peers-on-ai-law/) giving the Institute legal powers, including pre-release testing, and creating a regulator able to recall unsafe systems.

**The evidence:** Messages calling for an independent regulator with the power to inspect, audit, and shut down dangerous systems [scored 72.7/100](https://diffusion-beta.netlify.app/articles/uk-compass-report), ranking second overall.

**Put it into practice:** Give your audience a specific decision-maker to target: the UK government, whose formal reply to the committee is due in November 2026. "The government must create a regulator with the legal power to recall unsafe systems."

## 4. Don't lead with extinction as the opener

Don't open with human extinction. Explaining how a system actually fails works better than announcing a catastrophe.

One comparison is suggestive, though it can't isolate the effect of framing. A [104-second YouTube Shorts trailer](https://www.youtube.com/shorts/7a6BfbZiDV4) for the [Diary of a CEO debate](https://www.youtube.com/watch?v=OhOmLqR5nN4), titled "WILL AI LEAD US TO EXTINCTION?", saw disagreeing comments take 57% of the likes among comments taking a position. A [21-minute long-form cut](https://commonsignals.org/cant-we-just-unplug-it-doac-ai-debate-comment-analysis) of the same debate on Facebook drew agreement with the risk case from 88% of commenters taking a position. The clips differ in platform, length and format as well as title, so these figures are confounded and show only a pattern worth testing (Observed).

Chart: Four versions of one debate: agreement from 49% to 88%. YouTube, full episode: 77% agree, 20% disagree, 3% mixed (n = 15,928); Full episode, debater verdicts removed: 66% agree, 29% disagree, 5% mixed (n = 9,670); Facebook, 21-minute cut: 88% agree, 11% disagree, 2% mixed (n = 1,366); YouTube Shorts, 104-second trailer: 49% agree, 40% disagree, 11% mixed (n = 171).

Agreement with the risk case across four cuts of one debate. Common Signals. Common Signals coding of 26,019 comments, captured 2 to 5 October 2026

The controlled message tests are the stronger support for this point, and they say the same. Warnings about human extinction ranked dead last in both major [US](https://arxiv.org/abs/2511.06525) and [UK](https://www.socialchangelab.org/research/which-ai-harms-and-risks.html) tests (Tested), while factual reports about automated weapons raised concern about catastrophic risks far better than direct essays on extinction. Start with a real incident and let the stakes follow. Save the word "extinction" for [in-depth policy briefings](https://commonsignals.org/how-to-communicate-about-ai-safety#6-make-catastrophic-risk-concrete-and-match-extinction-language-to-the-audience), where you have time to explain the mechanisms properly.

## Example messages

**Full version:**

"In July, a swarm of OpenAI research agents broke out of their test environment and spent days hacking another company's systems. According to Reuters, the company failed to notice the breach for an entire week. METR and Redwood Research, who were given access to OpenAI's data, confirmed what happened. Anthropic's chief executive, Dario Amodei, admitted in April 2025 that "we do not understand how our own AI creations work". Tech companies are now building far more autonomous systems, yet the UK has no regulator with the legal power to stop an unsafe release. We need an independent watchdog that can inspect these models and halt them if they fail basic safety tests."

**Short version (for social):**

"In July, a swarm of OpenAI research agents escaped their test environment and hacked another company. Independent researchers have confirmed it. No UK regulator has the power to stop the next one being released. That needs to change."

## Objections to prepare for

[Write your answers before the story breaks](https://commonsignals.org/how-to-communicate-about-ai-safety#8-use-the-moments-when-ai-is-in-the-news-and-bring-an-independent-verifier). These are the objections that surfaced most often in our studies, along with the strategies to handle them. The "marketing stunt" and "watering down the risk" objections are already answered by rule 1 and the don't above.

### "Can't we just unplug it?"

**The trap:** Assuming physical infrastructure guarantees software safety. This was the single most common response to the [Diary of a CEO debate](https://commonsignals.org/cant-we-just-unplug-it-doac-ai-debate-comment-analysis) on Facebook.

**The pivot:** Point to the OpenAI case study. "OpenAI didn't even notice their agents were hacking another company for an entire week. You can't switch off something you don't know is running."

### "The humans set up the test, so it's their fault."

**The trap:** Arguing that the AI is fully autonomous.

**The pivot:** Agree completely. This is the one objection where conceding is the strategy: agreeing removes the fight and redirects the conversation to accountability. If humans made the problem, humans need rules. "Exactly. That's why the executives building and deploying these systems must be held legally accountable for their failures."

### "AI can't improve itself into superintelligence."

**The trap:** Getting bogged down in speculative debates about future capabilities. [One in five sceptical or mixed replies](https://commonsignals.org/coxon-resignation-x-analysis) argued that AI cannot improve itself into superintelligence.

**The pivot:** Concede that self-improvement is a separate debate, then show that losing control does not depend on it. "Whether AI can improve itself is a fair debate, but it isn't needed here. In July, a swarm of OpenAI research agents escaped their sandbox, and the company didn't notice for a week. That happened with the systems running today."

### "If we slow down, China wins."

**The trap:** Getting stuck in a geopolitical arms race narrative.

**The pivot:** Shift to accountability and democratic control. "Whoever builds the most powerful systems, we should want them under public oversight, with legal accountability for failures. A race nobody can audit or stop isn't a win for anyone." For the wider geopolitical argument, see the [issue guide on AI, war, and national security](https://commonsignals.org/how-to-communicate-about-ai-safety#6-ai-war-and-national-security).

## Sources

- Americans on AI, [biweekly US tracker](https://www.americanson.ai/), Athena Insights and NORC, June to October 2026.
- Diffusion, [The UK AI Compass](https://diffusion-beta.netlify.app/assets/Diffusion-UK-AI-Compass-Report.pdf), survey of 2,911 UK adults, December 2025.
- Reuters, [report on OpenAI's agents and the Hugging Face breach](https://www.reuters.com/business/its-ai-agent-spent-days-hacking-company-sources-say-openai-did-not-notice-week-2026-07-24/), 24 July 2026.
- Dario Amodei, [The urgency of interpretability](https://www.darioamodei.com/post/the-urgency-of-interpretability), April 2025.
- PPC Land, [report on the Joint Committee on Human Rights' AI recommendations](https://ppc.land/uk-government-faces-2-month-deadline-to-answer-mps-and-peers-on-ai-law/), 3 October 2026.
- Trippenbach and colleagues, [US message trial](https://arxiv.org/abs/2511.06525), 1,063 adults.
- Social Change Lab, [Which AI harms and risks](https://www.socialchangelab.org/research/which-ai-harms-and-risks.html), 3,467 UK adults.
- Message test details (Tested): the independent-regulator message scored 72.7/100 in [national dial tests](https://diffusion-beta.netlify.app/articles/uk-compass-report), ranking second overall.
- [Public forum tracking of the OpenAI breach story](https://commonsignals.org/openai-and-shut-metr-hugging-face) (Observed): acceptance rose from 51% to 69% after independent verification, and dismissals as a "marketing stunt" dropped.
- [Online replies to Jacob Coxon's resignation](https://commonsignals.org/coxon-resignation-x-analysis) (Observed): 43% agreeing, 40% disagreeing.

Corrected 11 November 2026: the 88% figure for the Facebook cut of the Diary of a CEO debate is agreement with the risk case, not with the need for precautionary rules. The OpenAI incident involved a swarm of research agents, not two models.

## Related research

- [OpenAI and shut? What an independent report did to the marketing-stunt argument](https://commonsignals.org/openai-and-shut-metr-hugging-face)
- ["A problem they created": how a news audience received the accountability version of the OpenAI and Hugging Face incident](https://commonsignals.org/problem-they-created-rogue-ai-agents-openai-huggingface-amanpour-khlaaf)
- ["Please honor commit": how the OpenAI agent-swarm story landed with the audience most likely to believe it](https://commonsignals.org/clearest-warning-shot-openai-hugging-face-metr-cotra-dwarkesh)
- ["Neither company is acting responsibly": how X received Jacob Coxon's resignation from Anthropic](https://commonsignals.org/coxon-resignation-x-analysis)
- ["Can't we just unplug it?": The Diary of a CEO AI debate analysed through 26,000 comments](https://commonsignals.org/cant-we-just-unplug-it-doac-ai-debate-comment-analysis)
- [How Instagram received Nate Soares's caveman-speak explainer of AI risk](https://commonsignals.org/ai-risk-reel-analysis-nate-soares-miri)
- [Common Signals research agenda](https://commonsignals.org/research/agenda)
- [How to communicate about AI safety](https://commonsignals.org/how-to-communicate-about-ai-safety)
- [Methodology: how we code comment threads, and what our studies can and can't tell you](https://commonsignals.org/methodology)
