Back to home

Compare

Comparing: Enterprise AI keeps failing — not on capability, but on handoffs between AIs & 企业 AI 协作系统频繁翻车:问题不在 AI 能力,而在 AI 之间的交接

AEN
Multi-AgentHandoff ContractLangGraph·

Enterprise AI keeps failing — not on capability, but on handoffs between AIs

What this is

A recent engineering practice piece on Juejin attributes all 5 failure types of Multi-Agent systems to handoffs between AIs — none stem from the AI's own capability.

Multi-Agent (multi-AI collaboration) means having multiple AIs divide work like a team: Planner breaks down tasks → Researcher gathers information → Coder writes code → Reviewer catches errors → Publisher outputs. Demos run smoothly, but the moment the system is moved into production, the first thing to break is when an upstream AI says "I'm done" and the downstream AI receives a pile of chat logs, with no idea what the other did or on what basis.

This piece proposes a "Handoff Contract" approach: a handoff isn't just shoving messages across — it's a backend-interface-style agreement that's checkable and rejectable, containing at least 8 types of fields (task, upstream/downstream, input package, state cursor, permission boundaries, evidence package, acceptance criteria, receipt).

Industry view

We note this view echoes industry consensus: the bottleneck for shipping Agent projects is shifting from model capability to engineering and process.

But opposing voices warrant equal caution. Some engineers argue that many teams simply don't need Multi-Agent — a single Agent plus tool calls can handle 80% of scenarios, and talking about handoff agreements now is drawing up blueprints too early for an immature paradigm. Another layer of risk: "contract" sounds rigorous but could shift the blame for collaboration failures from AI capability onto engineering specs, masking the model's own shortcomings.

Impact on regular people

  • For enterprise IT: When procuring Multi-Agent solutions, rather than pressing vendors on model capability, a better question is: "How is your handoff protocol designed? Who is accountable when things fail?"
  • For working professionals: As AI collaboration tools enter the office, employees may need to rethink "task handoff" — not just dumping files, but writing clear inputs, constraints, and acceptance criteria.
  • For consumer markets: In the short term, AI products will remain single-Agent dominated; Multi-Agent reaching consumers at scale still needs engineering frameworks to mature first.
Source: juejin.cn
BZH
Multi-AgentHandoff ContractLangGraph·

企业 AI 协作系统频繁翻车:问题不在 AI 能力,而在 AI 之间的交接

这是什么

掘金上一篇工程实践把 Multi-Agent 系统的 5 类失败全部指向 AI 之间的交接 — 没有一类出在 AI 自身能力上。

Multi-Agent(多 AI 协作),就是让多个 AI 像团队一样分工干活:Planner 拆任务 → Researcher 查资料 → Coder 改代码 → Reviewer 挑错 → Publisher 输出。Demo 跑得很顺,搬到生产线后,最先坏的环节是上游 AI 说"我完成了",下游 AI 接到一坨聊天记录,根本不知道对方做了什么、依据是什么。

这篇实践提出"Handoff Contract(交接合同)"思路:交接不是塞消息,而是写一份像后端接口一样可检查、可拒收的协议,至少包含 8 类字段(任务、上下游、输入包、状态游标、权限边界、证据包、验收标准、回执)。

行业怎么看

我们注意到,这一视角呼应了业内共识:Agent 项目落地瓶颈正从模型能力转向工程与流程。但反对声音同样值得警惕。一部分工程师认为,很多团队根本不需要 Multi-Agent,单 Agent 加工具调用就能解决 80% 场景,现在谈交接协议,是给一个还没成熟的范式过早画图纸。另一层风险是:"合同"听起来严谨,反而可能把协作失败的锅从 AI 能力推给工程规范,掩盖模型本身短板。

对普通人的影响

  • 对企业 IT:采购 Multi-Agent 方案,比起追问模型能力,更值得问供应商:"你们的交接协议怎么设计?失败时谁负责?"
  • 对个人职场:AI 协作工具进入办公室后,员工可能要重新理解"任务交接" — 不是丢文件,而是写清输入、约束、验收标准。
  • 对消费市场:短期内 AI 产品仍以单 Agent 为主;Multi-Agent 大规模进入消费者端,还要等工程框架先成熟。
Source: juejin.cn