Theo on the June 2026 Fable and Mythos Suspension

Theo reads Anthropic’s account of a US directive, examines the company’s security response and reflects on the policy questions it raises.

ThTheo登壇者
チャンネル
Theo - t3․gg
公開日
2026年6月13日
動画
14:20
読了時間
3 分
スライド
4
原文
英語
YouTube で開く
スクロールすると動画は右下に小さくなって再生を続けます。字幕は閲覧言語に合わせて切り替わります。
閲覧言語2 言語で読めます
この記事はまだ日本語に翻訳されていないため、英語の原文を表示しています。
要約

30 秒でわかる

In this June 2026 breaking-news video, Theo discusses Anthropic’s statement that it would suspend Fable 5 and Mythos 5 access after a US export-control directive. He reviews the company’s explanation of a potential narrow jailbreak and its defense strategy, while the details and outcome remained uncertain at recording time.

  1. 1The directive as described by AnthropicThe company said foreign-national access was restricted and it would suspend access for all customers to comply.
  2. 2The disputed demonstrationAnthropic said the demonstrated findings were minor and comparable capabilities existed in other models.
  3. 3Defense in depthThe company described red-teaming, layered safeguards and monitoring, while acknowledging that no safeguards are perfect.
  4. 4A call for a transparent processAnthropic said it would comply but disputed the decision and called for a transparent, fair, technically grounded process.
  5. 5An unverified motiveTheo raises retaliation as a possibility without evidence; it remains speculation.

ポイント

  1. Anthropic said it would suspend the two models for all customers to comply with a directive concerning foreign-national access.
  2. The company said the government’s letter lacked specific details of the national-security concern.
  3. Anthropic characterized the described jailbreak as narrow and argued that similar capabilities existed in other models.
  4. The company said it would comply while calling for a transparent and technically grounded process.
  5. Theo’s suggestion of a retaliatory motive was speculation unsupported by evidence in the video.
全文

チャプターごとに整えた全文を読む

文字起こしのみ
01

The sudden suspension

Theo describes the impact and reads Anthropic’s account of the directive. He distinguishes the affected models from other Anthropic products.

Fable suddenly became unavailable after only a few days. I had been using it heavily and had paid for subscriptions for my team, so the disruption affects us directly. I am frustrated by how quickly this happened and concerned about the precedent.

Anthropic said the US government issued an export-control directive concerning access to Fable 5 and Mythos 5 by foreign nationals, whether inside or outside the United States, including Anthropic employees. The company said it would disable both models for all customers to comply and that its other models were unaffected.

02

The security explanation

Anthropic describes a narrow potential bypass and its safeguards. Theo weighs the company’s claims and the limits of the available information.

Anthropic’s statement on access
スライド 1 / 4Anthropic’s statement on accessThe statement describes the directive and the decision to disable both models for all customers.

Anthropic said it received the directive at 5:21 p.m. Eastern time on June 12 and that the letter did not give specific details of the national-security concern. Its understanding was that the government had learned of a potential method of bypassing Fable’s safeguards.

Anthropic’s account of the demonstration
スライド 2 / 4Anthropic’s account of the demonstrationThe company describes the potential bypass and its assessment of the demonstrated vulnerabilities.

The company said it reviewed a demonstration involving a small number of previously known minor software vulnerabilities. It said the issues appeared relatively simple and that other publicly available models could find them without the same bypass. Those are Anthropic’s assessments of the demonstration, not an independent determination of the government’s full evidence.

Anthropic described extensive red-teaming before release with government, outside organizations and internal teams. It said testers had not found a universal jailbreak, while acknowledging that narrow bypasses remained possible and that perfect resistance was unlikely.

The stated defense strategy
スライド 3 / 4The stated defense strategyAnthropic describes red-teaming, limits of jailbreak resistance and layered monitoring.

Its defense-in-depth approach combined safeguards with monitoring to detect and respond to potential bypasses. Anthropic also connected its 30-day customer-data retention requirement to investigating and mitigating jailbreaks, while acknowledging that this policy had costs for customers.

Anthropic argued that disclosed narrow findings did not demonstrate a harmful result unique to Mythos and that comparable capabilities existed in other models. I agree with the company’s concern about the response, though we only have its account of the evidence at this point in the story.

The company said the government had supplied verbal evidence of a potential narrow jailbreak involving reading a codebase and fixing flaws. It said similar capability was available elsewhere, including in GPT-5.5, and emphasized that defenders also use such tools to keep systems safe.

03

Policy and uncertainty

Anthropic calls for a transparent process; Theo considers Dario Amodei’s policy essay. He closes with a developing picture and an unverified speculation about motive.

Compliance and disagreement
スライド 4 / 4Compliance and disagreementThe company says it will comply while disputing the action and requesting a transparent process.

Anthropic said it was complying but disagreed that this potential narrow jailbreak justified removing access to commercial models. It argued that government intervention should follow a transparent, fair and technically grounded statutory process, and said it was working to restore access.

I turn to Dario Amodei’s essay on AI policy. He argues that legislation moves slowly while AI capabilities may develop quickly, making it difficult both to prepare for risks and to design rules before their effects are clear. He describes transparency measures, chip export controls and labor-impact data as partial steps.

Amodei also argues that advanced models can have strategic cybersecurity consequences and that biological or autonomy risks could follow. These are his risk assessments and projections. I find the essay relevant because it discusses the policy machinery now affecting the company’s own model.

As I record, access still appears to work in one interface, and people are building status pages to watch when the API stops responding. The situation is developing; an announcement, a user interface and actual availability may not change at exactly the same time.

I wonder aloud whether the action could be retaliation related to Anthropic’s position on AI laws. I have no evidence establishing that motive, so it is speculation rather than a finding. At this point I am working from the company’s official statement and expect more information later.

For now, I hope access can be restored and feel for people who depend on the model, including colleagues outside the United States. The story was still developing when I recorded this, and my reaction reflects the uncertainty of that moment.

同じチャンネルの記事

スライド 5 枚38:47EN
Theo - t3․gg· 2026年10月28日Theo’s Long-Running Agent Experiments: Verification, Compute and CostTheo Browne · Ping LabsA skateboard game and two compiler projects show how repeated checks and flexible compute can sustain agent work—and how expensive those loops can become.コーディングエージェントエージェント工学AI cost & performance+2
スライド 5 枚36:07EN
Theo - t3․gg· 2026年10月27日Theo on Token Costs, Coding Agents, and the Price of AI CapabilityTheo Browne · Ping LabsA viral estimate of Lauren's AI spending prompts a closer look at cache pricing, benchmarks, and the changing work of coding agents.AI cost & performanceコーディングエージェントInference+1
スライド 5 枚30:37EN
Theo - t3․gg· 2026年10月26日Theo’s Three Skills for Reviewing and Shipping with Coding AgentsTheo Browne · Ping LabsHow sol-loop, full-send and full-stop encode review, verification and different levels of merge authority.Agent skillsコーディングエージェントCode review & verification+2
スライド 2 枚0:43EN
Theo - t3․gg· 2026年10月23日Theo Distinguishes Security Vulnerabilities from Active AttacksTheo Browne · Ping LabsA short explanation of why disclosed software flaws and reported attacks are different kinds of security news.CybersecuritySoftware engineering
スライド 6 枚29:22EN
Theo - t3․gg· 2026年10月22日Theo on Security Vulnerabilities, Stolen API Keys and AITheo Browne · Ping LabsA look at the gap between vulnerability disclosure and patching, and a speculative account of why stolen inference keys may be valuable.CybersecurityAI securitySoftware engineering+1
スライド 4 枚31:13EN
Theo - t3․gg· 2026年10月20日Theo on Why Smarter Models Help More Than DevelopersTheo Browne · Ping LabsFrom game modifications to compiler experiments, Theo revisits his assumptions about who benefits from more capable AI.コーディングエージェントDeveloper productivityHuman-AI Collaboration+1