Blog

# Multi-agent handoffs

Use cases / September 1, 2026 / Krishna Bhatnagar

One agent chooses which specialist takes over. The choice repeats, and so does each specialist's work.

In a multi-agent setup, a front agent reads the request and hands it to a specialist: billing, returns, technical support. Each specialist then does its own jobs.

Both halves repeat. The handoff is a choice the front agent makes again and again for the same kinds of request, and each specialist's work is a set of jobs like any other agent's.

## Where we are

Compiling the handoff itself needs new pieces in AgentCompile. Each specialist's jobs compile the way any agent's do. It's where we're heading.

## Two places where work repeats

- The handoff: the front agent sees the same kinds of request every day and routes them the same way.
- The specialists: each one has its own short list of jobs, like any single agent.

Today, both are reasoned out every time. The front agent thinks about who should take a refund request it has routed thousands of times, and the billing specialist thinks through a refund it has done thousands of times.

## What works today, and what doesn't yet

Without AgentCompile:

- Every handoff decision is a fresh model call.
- Every specialist reasons through its jobs from scratch.

With AgentCompile:

- Each specialist's known jobs run compiled today, like any agent's.
- Compiling the handoff decision itself needs new pieces: that part is where we're heading.

If you run a team of agents, the specialists are a good place to start, since each one's jobs compile the way any agent's do. Tell us what your handoffs look like; it will shape what we build.