热度观测:最近观测 126 赞,达到本渠道热门门槛 100;4.00089 小时内增加 23 赞,平均 +5.7/小时。

← 返回内容列表
𝕏X采集材料

Anthropic 的单代理工作流建议

10-26 22:44 · 北京时间

智能体应用

命中应用场景,需阅读原文判断

原文与观测指标

1 个来源
𝕏X

Anthropic 的单代理工作流建议

Prasenjit Sarkar
查看原文
点赞126采集时的累计值
每小时增长+5.7赞 / 小时 · 观测区间平均值
观测增量+23两次有效记录之间的变化

发布时间:2026-10-26 22:44 · 北京时间

指标采集:10-27 20:00

对比区间:10-27 16:00 至 10-27 20:00 · 4.00 小时 · 净增量 +23

摘要

材料介绍一种以单个代理和共享上下文替代多层子代理的设计:将子代理职责转为技能、API 调用转为 MCP 工具,并由运行框架控制轮次和成本。文中也提到合并可能导致检查遗漏,建议逐项调整并用真实案例评估。

摘要由 AI 生成,请以原文为准。
观测历史 · 最近 3 条 展开 / 收起

缺失不计为零;增长只比较同一指标来源的有效记录,按实际间隔折算每小时。上游缓存可能延迟数值更新。

采集时间 · 北京时间指标数值来源状态
10-27 20:00:50点赞126多 Agent 协作已取得
10-27 16:00:46点赞103多 Agent 协作已取得
10-27 15:44:26点赞99多 Agent 协作已取得
采集原文 展开 / 收起

Anthropic's applied AI team spent the last year watching enterprise customers build agent systems that look like org charts: a router on top, a ...

Anthropic's applied AI team spent the last year watching enterprise customers build agent systems that look like org charts: a router on top, a planner underneath, one specialist subagent per function. Their new guidance, out this week, says most of that should come apart. One customer ran roughly twice as fast after collapsing their setup into a single agent with a shared context window. The failure mode Anthropic names is specific: every subagent handoff returns a summary, and every summary drops detail. They call it a telephone game. The replacement pattern is one model, one context window, an open ended tool loop with turn and cost budgets enforced by the harness rather than the prompt. Each subagent's job becomes a skill. Its API calls become MCP tools. Approval gates move into the tools themselves. None of this works without progressive disclosure, loading instructions only when a task actually needs them. Anthropic says that technique alone cut Claude Code's system prompt by more than 80% on their newer models. It's also why the pattern couldn't have shipped two years ago: the models weren't reliable enough to manage that much ambiguity in one context window. Worth noting this isn't a totally new argument. Cognition built Devin on a single sequential agent back in 2024 explicitly because they'd watched multi-agent swarms produce confident, coordinated nonsense. LangGraph and CrewAI still default most users toward multi-agent graphs. Anthropic is now telling its own enterprise customers the opposite of what half the agent tooling industry sells by default. The honest caveat in their own writeup: folding one subagent lowered latency but broke a process in one of two test runs, because the agent skipped a shipping check it used to delegate out. Their fix isn't "don't fold," it's "fold one at a time and eval every change with real examples." That's a less exciting takeaway than the speed number, and probably the more important one. https://x.com/Arindam_1729/status/2114696945772249550 Arindam Majumder 𝕏: Anthropic just told teams to delete most of their subagents! (one customer ran ~2x faster after moving to a single agent loop) for a year, the default agent design looked like an org chart. a router on top, a planner, then one specialist subagent per team. anthropic's applied