Three Eras of AI Coding Agents: Tool Calls, Long Tasks, and Orchestration

Theo Browne uses three model releases to explain how he sees coding agents developing.

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

30 秒でわかる

Theo Browne describes three eras of agentic coding through Sonnet 3.5, Opus 4.5 and Mythos 5. In his view, the progression runs from reliable tool calls to longer tasks and then to orchestrating and verifying delegated work.

  1. 1Tool callsSonnet 3.5 was not the first model with tool calls, but Theo found them reliable enough for daily coding work.
  2. 2Long-running workTheo says Opus 4.5 could work for longer without losing track of its task.
  3. 3OrchestrationHe describes Mythos 5 as a jump toward delegating parts of a task to other models and verifying their work.

ポイント

  1. Theo associates Sonnet 3.5 with reliable tool calls for everyday coding.
  2. He sees Opus 4.5 as a step toward longer-running tasks.
  3. He associates Mythos 5 with breaking work up, delegating it and verifying the results.
全文

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

文字起こしのみ
01

Three eras of coding agents

Theo connects three model releases with tool calling, long-running work and orchestration. This is his framework for understanding their progress.

I think of these as eras. Sonnet 3.5 represents the tool-call era: it was not the first model able to call tools, but, in my experience, it was the first to do so consistently and reliably enough for everyday coding.

Three stages of coding agents
スライド 1 / 1Three stages of coding agentsTheo’s slide pairs Sonnet 3.5 with tool calls, Opus 4.5 with long-running work, and Mythos 5 with orchestration.

Then came Opus 4.5, which could work on much longer-running tasks without losing track of what it was doing.

Mythos 5 feels like another jump, this time to orchestration. In my experience it understands not only the codebase but how to use other models: it can split up work, spawn additional agents, and have the results verified afterward when asked.

同じチャンネルの記事

スライド 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