The case against multi-agent shopping bots
Anthropic's companion guide, 'The anatomy of effective commerce agents,' makes a specific, falsifiable claim: across enterprise commerce deployments, a single agent equipped with modular Skills consistently beat both a monolithic one-prompt design and a multi-agent/subagent design, often at lower cost and latency per task. [2]The reasoning is structural rather than stylistic. A commerce conversation is one tightly coupled session across multiple intents and turns - a shopper might ask about a return policy, pivot to comparing two products, then check whether a promo code still applies - all of it needing the same cart, order history, and product-catalog context. Handing that conversation off between specialized subagents (a search agent, then a cart agent, then a checkout agent) is what Anthropic calls a state-lossy operation: the receiving agent doesn't inherit the full thread, so quality degrades, and each handoff adds meaningful token cost and latency compared to loading a Skill directly in-context. [2]Skills sidestep that by loading directly into the one agent that already holds the conversation, rather than routing to a separate process. It's a notable reversal for an industry that has largely treated multi-agent orchestration as the default pattern for complex enterprise workflows - Anthropic is explicitly arguing that pattern is the wrong one for commerce specifically.


