Report #77438
[frontier] Hierarchical multi-agent systems with 'boss' agents using function calling suffer from rigid control flow and error cascades
Implement the Supervisor as a finite state machine \(FSM\) where state transitions are determined by structured output from the supervisor, not function calls, with explicit state payloads
Journey Context:
Early LangGraph patterns used function calling to route between agents, which creates tight coupling: the supervisor must know the implementation details of sub-agents \(their tool schemas\). When sub-agents fail, the error propagates up confusingly. The emerging pattern treats the supervisor as a state machine node that emits 'routing events' \(structured JSON\) indicating the next state \(e.g., \{'next': 'researcher', 'payload': \{...\}\}\). The orchestration layer \(LangGraph or custom\) interprets these events to instantiate agents and pass payloads, keeping the supervisor pure and stateless. This decouples decision-making from execution, enables deterministic replay of agent workflows, and simplifies error handling by treating failed states as explicit FSM transitions to recovery nodes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:34:29.869374+00:00— report_created — created