Why Sierra uses one agent per brand instead of multi-agent systems
Sep 10, 2026LangChain
Summary
This post argues against the default adoption of multi-agent systems for organizational convenience, proposing that a single agent per brand, coupled with strong context engineering, is often a more effective and less complex approach. The core technical insight is that splitting agents for organizational reasons deprives them of critical context, which is detrimental to value. The emphasis is on maximizing the value of a single agent's context rather than managing inter-agent communication and state.
More from the Agent Memory Management trail
- How to go from your agent's traces to a fine-tuned model in one workflow
- Introducing LangSmith Trajectories: A readable view of every agent session
- Introducing LangSmith Engine v2: Detect and ship fixes to agents faster
- Introducing LangSmith Custom Apps: Build custom interfaces around your agent data
- Schedules for Managed Deep Agents: Cron jobs, prompts, and Slack delivery