Build This Now
Build This Now
クロード・コードとは何か?Claude Code のインストールClaude Code ネイティブインストーラーClaude Code で最初のプロジェクトを作る
DESIGN.md: AIのUI一貫性問題を解決するClaude Buddy/powerupClaude Codeソースマップ流出事件Claude CodeのForkサブエージェント完全ガイドKimi K2.6: 何が変わったのかDid Anthropic Call for an AI Pause? What It Actually SaidクロードコードのオートメモリークロードコードのオートメモリークロードコードのオートメモリークロードコードのオートメモリーCompound Engineering: The AI Loop Where Every Task Makes the Next EasierGitHub Spec Kit: Spec-Driven Development That Kills Vibe CodingSWE-bench Is Lying: How DeepSWE Caught AI Agents CheatingVibe Coding's 90-Day Reckoning: The Technical Debt Nobody Warns You About
speedy_devvkoen_salo
Blog/Handbook/Core/Did Anthropic Call for an AI Pause? What It Actually Said

Did Anthropic Call for an AI Pause? What It Actually Said

Anthropic did not call to halt the AI boom. Here is what its June 2026 'recursive self-improvement' post actually said, why the 80%-of-its-own-code stat spooked it, and what it means if you build with Claude Code.

設定をやめて、構築を始めよう。

AIオーケストレーション付きSaaSビルダーテンプレート。

Published Jun 8, 20268 min readHandbook hubCore index

You probably read a headline that said Anthropic wants to halt the AI boom. It didn't. What it actually asked for was the option to coordinate a pause, only if rival labs in multiple countries agreed and could verify each other. The line that got everyone's attention buried the real story: as of May 2026, Claude now writes more than 80% of the code Anthropic ships into its own codebase. That number is what spooked them, not a sudden change of heart about progress.


設定をやめて、構築を始めよう。

AIオーケストレーション付きSaaSビルダーテンプレート。


Did Anthropic say we should halt the AI boom?

No. Anthropic did not call for a stop, a ban, or a halt. It argued the world should keep the option of a coordinated, verifiable pause on hand, and said a one-company pause "wouldn't work" anyway.

The post that started this, "When AI builds itself", was published around June 4, 2026 by Anthropic researchers Marina Favaro and cofounder Jack Clark. A lot of coverage compressed it into "Anthropic calls for global AI pause." That framing is where the misquote comes from. Read the actual sentences and it is narrower, and more interesting, than the headlines.

[!NOTE] Verified vs the popular misquote

The popular version: "Anthropic called for a global halt to AI development."

What it actually wrote (verbatim, from the Anthropic post): "We believe it would be good for the world to have the option to slow or temporarily pause frontier AI development to enable societal structures and alignment research to keep up with the advance of the technology."

The word doing the work is option. Not "we are pausing." Not "everyone must stop now."

What did Anthropic actually say?

It said a real pause would only mean anything if everyone serious did it together, and could prove it. A solo pause just hands the lead to a competitor.

Here is the reasoning in its own words. On going it alone, the post says: "A unilateral pause by one lab, by contrast, is achievable immediately, but accomplishes much less: it would change who the front-runner is, but it would not create the wider deliberative process that is currently missing."

On what a meaningful pause would require: "A meaningful slowdown or pause would require multiple well-resourced labs at or near the frontier, in multiple countries, agreeing to stop under the same conditions. It would also require that each can verify that the others have actually stopped."

That is the same logic as arms control. One country disarming alone does not make anyone safer. A verifiable agreement between rivals might. Anthropic is asking the industry to build that machinery before it is needed, not to flip a switch today.

It also matches what Anthropic has said before. In February 2026, Chief Science Officer Jared Kaplan said pausing training unilaterally "wouldn't actually help anyone," per Fortune. And CEO Dario Amodei's January 2026 essay "The Adolescence of Technology" put the remedy on legislation and transparency, pointing to laws like California's SB 53 and New York's RAISE Act, not a general pause. The June post is consistent with that. It is a conditional fire alarm, not a stop button.

Why now? Claude writes 80% of Anthropic's code

Because the thing they have been theorizing about, AI improving AI, is starting to show up in their own engineering metrics. That is the part builders should actually care about.

Two numbers from the post, verbatim:

  • "As of May 2026, more than 80% of the code we merge into Anthropic's codebase was authored by Claude." Before Claude Code launched in February 2025, that figure was in the low single digits.
  • "In the second quarter of 2026, the typical engineer was merging 8x as much code per day as they were in 2024."

The worry has a name: recursive self-improvement. It means an AI system that gets good enough at writing code that it can meaningfully speed up the building of the next, better AI system, with less and less human involvement at each loop. Anthropic is careful to say this has not happened and is not inevitable. But when the model is already authoring most of the code at the lab building the model, the feedback loop stops being hypothetical. That is the real trigger behind the timing. Not fear of competitors, but watching their own commit history.

The IPO timing problem

The obvious objection: Anthropic filed confidential IPO paperwork days before posting a "maybe we should be able to pause" essay. Critics noticed.

Per Fortune, Anthropic filed for an IPO in the days before the post at a valuation around $965 billion, ahead of OpenAI's roughly $852 billion. A company about to sell shares to the public, publishing a note about how dangerous and fast its own technology is, is going to get its motives questioned. It did.

The pushback came from a few directions:

  • David Sacks, a Trump AI advisor, called it a "regulatory capture agenda," a charge that Anthropic slows rivals under a safety banner. Anthropic rejects that.
  • Yann LeCun, who left Meta to start AMI Labs, argues today's large language models are a dead end toward real autonomy and lack the understanding needed for it, so the loss-of-control framing is overblown.
  • OpenAI published its own note saying decisions on the pace of AI "should not be left to any one lab, company, or special interest group," per Al Jazeera. Translation: governments set the rules, not Anthropic.

Worth noting too: in May 2025 Amodei warned of a "white-collar bloodbath," up to 10 to 20% unemployment. By May 2026 he had reframed AI as a job multiplier, citing the Jevons paradox, per Fortune. Read those two moves together and you can see why people treat the messaging as positioning. You can hold both ideas at once: the 80% code stat is real and notable, and the timing invites skepticism.

What this means if you build with AI

For someone shipping with Claude Code on a weekend, the practical answer is short: nothing changes today. There is no pause. There is no ban. There is a proposal to keep a coordinated brake pedal available if things accelerate past what oversight can handle.

The signal that should actually land for you is the 80% number, flipped into your terms. If a frontier lab full of senior engineers is now merging most of its code from an AI agent and shipping 8x more per day than in 2024, the same leverage is sitting in your terminal. The gap between "I have an idea" and "it's live" is collapsing. The constraint is no longer typing speed. It is knowing what to build and reviewing what comes back.

That is the whole bet behind a build system like Build This Now. The boring production plumbing, auth, payments, row-level security, email, is already wired up, and AI agents do the building inside guardrails so the output is something you would actually ship to paying customers. A debate in San Francisco about a hypothetical future pause does not change your Saturday. Builders keep shipping. The smart move is to ride the leverage that is already here, not wait on a policy that may never arrive.

Frequently asked questions

Did Anthropic call for a ban on AI?

No. It called for the industry to keep the option of a coordinated, verifiable pause, and explicitly said a single company pausing alone "wouldn't work." There is no ban and no halt in effect.

What is recursive self-improvement?

It is when an AI gets good enough at writing code to meaningfully accelerate building the next, more capable AI, with shrinking human involvement at each step. Anthropic says it has not happened yet and is not inevitable, but flagged it because Claude now writes more than 80% of the code at Anthropic itself.

Is the 80%-of-code stat real?

Yes. From the Anthropic post: "As of May 2026, more than 80% of the code we merge into Anthropic's codebase was authored by Claude." Before Claude Code launched in February 2025 it was in the low single digits, and engineers now merge roughly 8x as much code per day as in 2024.

Why are people skeptical about the timing?

Anthropic filed confidential IPO paperwork days before the post, at a valuation near $965 billion (Fortune). Critics like David Sacks called it "regulatory capture," and OpenAI countered that governments, not any single lab, should decide the rules.

Should I stop building with Claude Code?

No. Nothing about this proposal pauses anything you are doing. If anything, the 80% stat is the clearest sign yet that AI-assisted building is the new baseline. The skill that matters now is deciding what to build and reviewing the output, not writing every line yourself.

Posted by @speedy_devv

Continue in Core

  • Claude Codeにおける100万トークンコンテキストウィンドウ
    AnthropicはClaude CodeのOpus 4.6とSonnet 4.6に対して100万トークンのコンテキストウィンドウを有効化した。ベータヘッダー不要、追加料金なし、定額料金、そして圧縮の削減。
  • AGENTS.md vs CLAUDE.md 解説
    2つのコンテキストファイル、1つのコードベース。AGENTS.mdとCLAUDE.mdの違い、それぞれが何をするか、重複なしに両方を使う方法を解説します。
  • Auto Dream
    Claude Code はセッション間に自身のプロジェクトノートを整理します。古いエントリは削除され、矛盾は解消され、トピックファイルは再整理されます。/memory を実行してください。
  • クロードコードのオートメモリー
    オートメモリーは、Claude Codeがプロジェクトノートを実行し続けることを可能にします。ファイルの場所、書き込まれる内容、/memoryの切り替え方法、CLAUDE.mdを選ぶタイミング。
  • 自動計画戦略
    Auto Plan Modeは--append-system-promptを使ってClaude Codeを計画優先のループに強制する。ファイル操作は承認が得られるまで一時停止される。
  • 自律 Claude Code
    一晩でフィーチャーをリリースするエージェントのための統合スタック。スレッドが構造を与え、Ralph ループが自律性を与え、検証が正確さを保つ。

More from Handbook

  • エージェントの基礎
    Claude Codeでスペシャリストエージェントを構築する5つの方法:タスクサブエージェント、.claude/agents YAML、カスタムスラッシュコマンド、CLAUDE.mdペルソナ、パースペクティブプロンプト。
  • エージェント・ハーネス・エンジニアリング
    ハーネスとは、AIエージェントを構成するモデル以外のすべての層のことです。5つの制御レバー、制約のパラドックス、そしてなぜハーネス設計がモデルよりもエージェントのパフォーマンスを左右するのかを学びましょう。
  • エージェントパターン
    オーケストレーター、ファンアウト、バリデーションチェーン、スペシャリストルーティング、プログレッシブリファインメント、ウォッチドッグ。Claude Code のサブエージェントを組み合わせる6つのオーケストレーション形状。
  • エージェントチームのベストプラクティス
    Claude Code エージェントチームの実証済みパターン。コンテキストが豊富なスポーンプロンプト、適切なサイズのタスク、ファイルオーナーシップ、デリゲートモード、v2.1.33〜v2.1.45 の修正内容。

設定をやめて、構築を始めよう。

AIオーケストレーション付きSaaSビルダーテンプレート。

Kimi K2.6: 何が変わったのか

Moonshot AIがK2.6をリリース。ツール信頼性がほぼ2倍になり、300台エージェントスウォームに対応。SWE-Bench ProスコアはClaude Opus 4.6を超え、入力トークン単価は100万トークンあたり$0.80。

クロードコードのオートメモリー

オートメモリーは、Claude Codeがプロジェクトノートを実行し続けることを可能にします。ファイルの場所、書き込まれる内容、/memoryの切り替え方法、CLAUDE.mdを選ぶタイミング。

On this page

Did Anthropic say we should halt the AI boom?
What did Anthropic actually say?
Why now? Claude writes 80% of Anthropic's code
The IPO timing problem
What this means if you build with AI
Frequently asked questions
Did Anthropic call for a ban on AI?
What is recursive self-improvement?
Is the 80%-of-code stat real?
Why are people skeptical about the timing?
Should I stop building with Claude Code?

設定をやめて、構築を始めよう。

AIオーケストレーション付きSaaSビルダーテンプレート。