LecturaInvestigaciónRadarMarco de inversión
Iniciar sesión / Registrarse
← Volver a la lectura
NoticiasTema · AnthropicMaterial2 min de lecturaEditorial de DisconfirmAI

Anthropic Advises Enterprises to Reduce AI Subagents: Single Agent with Skills Often Outperforms Multi-Agent Architectures

An official Anthropic article states that in many enterprise projects, a single agent paired with skills often delivers better quality, lower costs, and faster speeds than complex multi-agent architectures, providing specific migration steps and boundaries.

2026-10-26 13:41 GMT+8

US-based AI company Anthropic published an article on the official Claude website on October 22, advising enterprises to reduce the use of subagents when building AI agents, and instead fold some specialized agents back into the main agent loop. The article claims that based on observations from multiple enterprise projects by its Applied AI team, a 'single agent plus skills' design often yields better quality than both 'one prompt for everything' and multi-agent architectures, typically at lower cost per task and faster speed.

The article lists five common risks when large enterprises adopt a 'coordinator plus team-specific subagents' architecture: loss of detail during handoffs, proliferation of subagents, conflicting prompts as teams continuously add rules, siloed evaluation where each team only tests its own subtask, and increased latency. Anthropic also observed that agent architectures often end up mirroring the company's org chart. Additionally, when the system prompt of an AI agent contains more than 30 to 50 tool definitions, the model's ability to select tools tends to degrade.

As a comparison, Anthropic noted that the system prompts for advanced models in its coding assistant Claude Code have been reduced by over 80%, shifting to a progressive disclosure approach for skills and tools. The article cited an example where a client saw roughly 2x speedup after switching from a multi-agent architecture to a single agent loop. However, this data comes from Anthropic's own observations and unnamed clients; the 2x speed is a single-client case and may not apply universally, so enterprises still need to validate with their own evaluations.

Iniciar sesión / Registrarse
LecturaInvestigaciónRadarMarco de inversión

Regarding when subagents remain appropriate, Anthropic did not dismiss them entirely, noting they are still suitable if: a single loop shows measurable quality degradation due to overly long context; multiple tasks require parallel processing with disposable new context windows for each; or a single agent struggles to select tools or faces contradictory instructions in the system prompt.

The suggested migration steps include: first, establish evaluations (even just 10 standard examples are enough to start); next, have the main agent call subagents as tools; then merge closely related specialists; finally, rewrite one subagent at a time into skills and tools, comparing before-and-after evaluation results. Anthropic's rule is to keep it as a subagent only if merging causes the score to drop.

Fuentes

  • inside.com.twINSIDE↗
Tema

Anthropic

Anthropic 近日发布工程指南,建议企业在构建 AI 代理时减少子代理(subagent)的使用,转而采用“单一主代理加技能”的架构。这一转变基于其应用 AI 团队在多个企业项目中的观察:随着模型能力提升,单一代理配合按需加载的技能在…

5 pasos1 piezasActualizado 2026-11-07 21:23

Cómo llegó hasta aquí

  1. 2024-12-19Anthropic 发布《Building effective agents》,初步确立工作流与代理的区别,强调从简单方案开始。anthropic.com ↗
  2. 2025-06-13Anthropic 发布研究文章,详细阐述多代理系统在广度优先搜索任务中的优势,指出其能显著扩展 token 处理能力。anthropic.com ↗
  3. 2026-01-23Anthropic 更新博客《Building multi-agent systems: When and how to use them》,明确界定多代理仅适用于上下文隔离、并行处理和专业化选择三种场景,其余情况建议回归单代理。r.jina.ai ↗

Lo que aún está pendiente

  • 具体哪些行业或任务类型被证实仍必须保留多代理架构以避免性能下降?
  • Anthropic 提供的迁移工具包(migration kit)在实际企业部署中的采纳率和反馈如何?
Leer el tema completo →
Continuar investigando →