November 11, 2025
LangGraph's Supervisor Pattern Has a Major Flaw. Here's How to Fix It.

Yash Vibhandik
CEO

If you're building stateful, multi-agent systems with LLMs, you're almost certainly familiar with LangGraph. It's a powerful library for creating complex, graph-based agent workflows and AI orchestration. One of the most common and celebrated patterns used by LangGraph developers is the supervisor agent pattern.
What Is the Supervisor Agent Pattern?
This pattern is elegant in its simplicity:
- You define a central Supervisor agent.
- You create several specialized sub-agents (e.g., Returns Agent, Ordering Tracking Agent, Product Support Agent), each with its own specific system prompt and tools.
- The Supervisor's job is to analyze an incoming user query and route it to the correct sub-agent using intent classification.
This works beautifully when there's a clear separation of concerns. A query about "my order status " goes to Ordering Tracking Agent. A query about "my Product return process " goes to Returns & Refund Agent.
But this popular agent routing pattern has a fundamental, conversation-breaking flaw: it only picks one route.
The Problem: Real Conversations Aren't Categorical
Real users don't think in neat, categorical boxes. Their queries are messy, multi-intent, and context-switching, a challenge for traditional conversational AI design.
Consider this extremely common type of user query:
"Hi, I need to return this laptop I bought last week. Also, what's your warranty policy on replacement items?"
Here's what happens with the standard supervisor orchestration pattern:
1.) The Supervisor analyzes the query.
2.) It identifies "return this laptop" as the primary intent.
3.) It routes the entire query to the ReturnsAgent.
The ReturnsAgent is an expert on return logistics, order numbers, and refund timelines. It knows nothing about warranties. This leads to one of three bad outcomes:
- Ignores: The agent processes the return and completely ignores the warranty question.
- Admits Failure: The agent says, "I can help with the return, but I don't have information on warranties."
- Hallucinates: The agent, lacking specific knowledge, invents a plausible-sounding but incorrect warranty policy.
None of these are acceptable for a production-grade AI agent. This isn't a simple bug you can patch. It's a fundamental limitation of a static routing pattern trying to handle dynamic, multi-threaded human conversation, a known challenge in conversational AI systems.
The Solution: From Static Routing to Dynamic Guidelines
Instead of forcing a single choice, what if we could dynamically load all relevant capabilities at runtime? This approach aligns with modern agentic AI architecture principles.
This is the approach implemented in Parlant, a trending open-source framework (15k+ stars) designed specifically for this challenge. Parlant shifts the paradigm from routing between agents to dynamically matching guidelines, similar to how semantic routing works in advanced LangChain implementations.
Understanding Guidelines: Modular AI Instructions
Think of guidelines as modular, conditional pieces of instruction that tell an agent what to do and when to do it. Here's what one looks like:

Each AI agent guideline is simple, with two main parts:
- condition: When should this logic be activated?
- action: What should the agent do (and what tools can it use)?
How Dynamic Guidelines Solve Multi-Intent Queries
Here's the magic: At each turn in the conversation, Parlant's engine evaluates ALL available guidelines against the user's query using contextual agent evaluation. It doesn't pick just one. It loads every matching guideline into the agent's context for that specific turn.
Let's revisit our problem query:
"Hi, I need to return this laptop... Also, what's your warranty policy...?"
With Parlant's multi-guideline activation:
1.) The query matches the condition for the Returns Guideline.
2.) The query also matches the condition for the Warranty Guideline.
3.) Both guidelines are loaded into the agent's context simultaneously.
4.) The agent now has the instructions and tools for both tasks, allowing it to generate a single, coherent response that addresses the return and the warranty, just like a human would.
This approach follows best practices outlined in OpenAI's function calling documentation for handling complex, multi-tool scenarios.
Better Together: Why LangGraph and Parlant Aren't Competitors
This isn't about replacing LangGraph with Parlant. They solve different problems and are incredibly powerful when combined in a hybrid agent architecture.
-
LangGraph is best-in-class for workflow automation and stateful agent execution. It gives you precise, granular control over complex, multi-step processes, perfect for implementing patterns like React agents or tool-using workflows.
-
Parlant is designed for conversational coherence. It excels at handling free-form, unpredictable user conversations where topics are mixed and context is fluid.
The Hybrid Approach: Conversation + Workflow
The best part? They work together beautifully in an enterprise AI agent stack. You can get the best of both worlds. Parlant handles the fluid, customer-facing conversational flow. But when a guideline's action requires a complex, multi-step process (like an advanced RAG pipeline or multi-step reasoning), that action can be powered by an entire LangGraph graph.
Think of Parlant as the general manager who capably handles the customer's multi-faceted request, and LangGraph as the specialist team it calls in to execute the complex internal tasks, similar to how LangChain agents delegate to specialized tools.
Conclusion: Build Agents That Reflect Real Conversation
The rigid, single-route supervisor pattern forces users to adapt to the limitations of our agents. This is backward.
By shifting to a dynamic, guideline-driven model, we can build intelligent AI agents that adapt to the messy, multi-topic reality of human conversation. We can stop building agents that fail on complex queries and start building agents that can genuinely keep up.
This approach represents the future of conversational AI architecture, moving from rigid routing to flexible, context-aware systems that handle the complexity of real human communication.
You can check out the full Parlant implementation and try it for yourself.
Ready to Build Smarter AI Agents?
At Bitontree, we specialize in designing and deploying advanced AI agent solutions that truly understand your users. From multi-threaded conversational agents to complex workflow automation, our expertise in frameworks like LangGraph and dynamic guideline-based systems ensures your AI initiatives deliver real value.

I am the founder and CEO of Bitontree, where I lead embedded AI engineering teams that build and run production AI: agents, RAG and knowledge systems, document AI, and workflow automation for healthcare, logistics, legal, and SaaS companies. I write about what it actually takes to ship AI that survives contact with production.
Frequently Asked Questions
Can I use dynamic guidelines with my existing LangGraph setup?

Yes! Dynamic guidelines complement LangGraph workflows. Use guidelines for conversation management and LangGraph for complex task execution.
Why does the LangGraph Supervisor Pattern fail in real-world conversations?

It fails because real user queries often include multiple intents in one message (e.g., “return + warranty”). The supervisor picks only one route, sending the query to a single agent. As a result, the system ignores secondary intents or produces incomplete or hallucinated responses.
How do dynamic guidelines handle conflicting conditions?

When multiple guidelines match but propose conflicting actions, the engine evaluates each in context to determine which is most relevant at that point in the conversation. Factors such as intent strength, conversational history, and assigned priority help the system decide which guideline should take precedence. Instead of executing all actions blindly, it merges compatible ones and suppresses those that could cause contradictions, ensuring the response remains coherent, contextually accurate, and human-like.
When should developers move from a Supervisor Pattern to a Guideline-based approach?

Teams should switch when their conversational system faces multi-intent queries, cross-domain questions, or context-switching dialogues. The Guideline-based model scales better for real customer interactions that don’t fit rigid intent categories.


