Niches · Agent frameworks & SDKs

Split a job across specialist agents with hand-offs

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
19companies, fit with a limit
80companies carry the tag
16share of the category's work
10first-hand accounts

What counts as done

The router sends each test request to the expected specialist, control returns to the caller where the design says it should, each hand-off and the context passed appear as separate steps in the trace, and sub-agent tool calls are visible in the stream. Runs on a second model provider without code changes.

Measured, for our own tests: routing accuracy on a fixed set of 20 requests and the spread of answers across 5 repeats of the same request. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: route support questions to the right specialist agent, have a manager agent delegate to researchers, build a team of agents for this analysis, hand off to the billing agent and come back

Does the job, with a limit 19

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
AgentOS A
Framers Lab, Inc.
agency() runs sequential, parallel, debate, review-loop, hierarchical and graph strategies across 13 providers, but the docs list spans for turns and tool results only, not per hand-off, and say nothing of sub-agent tool calls reaching the stream. source
Agno BB
Agno Inc.
Team modes coordinate, route, broadcast and tasks; members return results to the leader, and tracing records leader coordination and member runs. Member events stream with stream_events. Accounts: tool_call_limit leaves the loop running (agno #8304), and docs were hard to navigate (HN 47561818). source
BoxLang AI B
Ortus Solutions, Corp.
Sub-agents are wrapped as delegate_to_<name> tools that return to the parent, across 15+ providers. The docs show no per-hand-off trace span or sub-agent tool calls in the stream, and no OpenTelemetry export. source
Claude Agent SDK BB
Anthropic, PBC
Subagents run in their own context, in parallel, return a report to the parent and take their own model and maxTurns. Claude models only, so the second-provider test can't be met; per-hand-off trace spans aren't described. source
CrewAI C
CrewAI, Inc.
A hierarchical process puts a manager over specialist agents, but accounts report it failing on a local Ollama model where sequential worked (crewAI #1863) and stray backticks behind FastAPI (#2105). Built-in tracing needs a CrewAI AMP login. source
Cursor Agent SDK B
Anysphere, Inc.
Subagents declare a description the parent reads to delegate and inherit the model; every model turn runs through Cursor's backend with Cursor models, and the docs read don't show hand-off spans or sub-agent tool calls in the stream. source
Docker Agent BB
Docker, Inc.
sub_agents delegate through transfer_task and results flow back to the root; handoffs pass the conversation on. --otel spans cover sub-agent hand-offs and provider fallbacks, across many providers. Whether sub-agent tool calls reach the client stream wasn't confirmed. source
Agent Development Kit (ADK) BB
Google LLC
Sub-agents, workflows and AgentTool, with invoke_agent and execute_tool OpenTelemetry spans. Accounts: control went into a sub-agent and never returned (adk-python #147), a built-in tool failed inside a sub-agent (#53), and some built-in tools exclude all others in one agent. source
guilds.run C
Cigale AI
Guilds are standing teams sharing a group chat, and each run keeps the prompt and every tool call. The docs describe chat dispatch between agents rather than a router with a defined return to the caller, and no trace export. source
LangGraph BB
LangChain, Inc.
Hand-offs are tools returning a Command, with subagent, router and subgraph patterns, on any LangChain model. Tracing is LangSmith, which needs an account, and subgraph hand-offs need careful context handling per the docs. source
LlamaIndex Framework BB
LlamaIndex, Inc.
AgentWorkflow hands off through can_handoff_to and streams events; the orchestrator pattern exposes sub-agents as tools so control returns. The docs read don't show hand-offs as separate trace spans, and OpenAI is the default LLM unless Settings changes it. source
Mastra A
Kepler Software, Inc.
Supervisor agents keep a lead in control and delegate to subagents; hand-off and council patterns are documented, tracing follows model and tool calls in one request, across AI SDK providers. Sub-agent spans per hand-off weren't confirmed; .network() is deprecated. source
Microsoft Agent Framework A
Microsoft Corporation
Handoff orchestration passes control between agents with explicit rules (specialists can return to triage) and streams workflow events; OpenTelemetry follows GenAI conventions. An account saw checkpoint resume fail when per-request agent ids changed (agent-framework #4793). source
OpenAI Agents SDK AA
OpenAI OpCo, LLC
Hand-offs and manager-style Agent.as_tool, whose on_stream callback surfaces nested agent events, and approvals apply across hand-offs. Accounts: hand-offs were one-way (openai-agents-python #847) and routing worsened after a model swap (#1397). source
Pydantic AI AA
Pydantic Services Inc.
Delegation through tools returns control to the parent, with SubAgents in the Harness, programmatic hand-off and graphs, across 25+ providers, and OpenTelemetry spans via Logfire or any collector. Routing quality is left to the app; no account tested it. source
smolagents B
Hugging Face, Inc.
A manager agent calls managed_agents as tools and gets their answers back, on any model through LiteLLM, Transformers or Inference Providers, with OpenTelemetry instrumentation. The secure-execution page says the Docker executor doesn't support multi-agents. source
Strands Agents A
Amazon Web Services, Inc.
Agents as tools (control returns to the orchestrator), Swarm hand-offs, Graph and Workflow patterns, with spans per model and tool invocation. Bedrock is the default provider; whether hand-offs get their own span wasn't confirmed. source
TradingAgents B
Tauric Research
A fixed LangGraph pipeline of analysts, a bull and bear debate, a trader and risk reviewers, on many providers with a provider per model tier. Routing isn't configurable, and accounts report results changing every run (TradingAgents #178) and suspected training-data leakage in backtests (#33). source
AI SDK AA
Vercel Inc.
Subagents are invoked through a tool and return a result, optionally streaming progress to the UI, on any AI SDK provider. There is no hand-off primitive; a basic subagent blocks and hides its steps unless you stream it yourself, and spans per hand-off aren't described. source

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
NitroStack C
Nitrostack Inc.
No agents or hand-offs: a NitroStack project is an MCP server that AI clients connect to. source

What stops agents finishing

  • hand-offs that are one-way, so the orchestrator never regains control
  • sub-agent run as a tool hides its tool calls from the stream
  • built-in tools refused inside sub-agents
  • routing quality changes when the default or chosen model changes
  • the same input gives different answers each run, so outputs cannot be backtested

Around it

Before: frameworks.tool-calling-agent. After: agent-observability.debug-failed-run, agent-observability.offline-eval-regression.

Where this comes from

Weight 16 of 100 in Agent frameworks & SDKs: 10 of 61 accounts have this as their main job (share 16.4, rounded by largest remainder to sum 100); includes 2 TradingAgents accounts on its fixed research pipeline

The same as data: /api/v1/use-cases/frameworks.multi-agent-handoff.json, or the MCP tool get_use_case with id frameworks.multi-agent-handoff. Other jobs in this category: /api/v1/niches?category=frameworks.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.