Agent Orchestration
Coordinate multi-agent workflows with reliable, observable task execution
Multi-agent systems fail in ways single agents do not: partial progress gets lost, agents deadlock waiting for each other, and debugging distributed failures is painful. We provide orchestration infrastructure that makes multi-agent workflows reliable and transparent by default.
Orchestration Patterns#
Supervisor-Worker#
A planner agent breaks a task into subtasks and dispatches them to specialized workers. Results are collected and synthesized.
When to use: Complex tasks that benefit from specialization — research + writing + review, code generation + testing + documentation.
What we manage:
- Subtask queue with priority and dependency ordering
- Worker assignment based on capability and availability
- Result aggregation with partial-failure handling
- Supervisor context injection and handoff protocol
Parallel Pipelines#
Multiple agents run simultaneously on independent subtasks. Results merge at a synchronization point.
When to use: Tasks with clear parallel branches — scraping multiple sources, processing dataset chunks, running independent analyses.
Features:
- Configurable concurrency limits per pipeline
- Fan-out / fan-in with configurable merge strategies
- Early termination if a critical branch fails
- Per-branch timeout independent from total pipeline timeout
Sequential Chains#
Agents execute in series, each receiving structured output from the previous step.
When to use: Step-by-step pipelines where each stage depends on the previous — data extraction → enrichment → classification → storage.
Features:
- Typed handoff schemas enforced at each step boundary
- Conditional branching based on intermediate results
- Automatic step retry on transient failure
Human-in-the-Loop#
Pause workflow execution at defined checkpoints for human review or approval.
Integration options:
- Webhook callback when approval is needed
- Slack notification with approve/reject actions
- Email with secure one-click response
- Custom UI embed via provided React component
Durable Execution#
Agent orchestration fails without durability. Every workflow step is:
- Checkpointed — state written before and after execution
- Idempotent — safe to re-run after a crash without duplicate side effects
- Retryable — configurable retry policy with backoff and jitter
- Observable — execution DAG visible in real time in the dashboard
Failure Handling#
| Failure Type | Default Behavior | Configurable |
|---|---|---|
| LLM timeout | Retry 3× with backoff | Yes |
| Tool error | Retry 2× then fallback | Yes |
| Agent crash | Resume from last checkpoint | Always |
| Deadlock detection | Alert and cancel cycle | Yes |
| Budget exceeded | Graceful stop with partial result | Yes |
Workflow Definition#
Define workflows in code or via our YAML schema — no visual-only tools that become bottlenecks.
TypeScript SDK:
1import { Workflow, agent, parallel } from '@assistance/agents'23const research = agent('researcher')4const writer = agent('writer')5const reviewer = agent('reviewer')67export const reportWorkflow = new Workflow({8 steps: [9 parallel([research('market-trends'), research('competitor-analysis')]),10 writer.synthesize(),11 reviewer.approve({ minScore: 0.8 }),12 ],13 timeout: '15m',14 retries: { max: 3, backoff: 'exponential' },15})YAML definition also supported for teams preferring configuration-as-code without a build step.
Scheduling#
- Cron schedules — run workflows on a recurring schedule
- Event triggers — start on webhook, queue message, or database change
- Chained triggers — one workflow's completion triggers another
- Manual dispatch — API or dashboard one-click run with optional input override
Getting Started#
Describe your multi-agent workflow and we'll help you model the orchestration graph, pick the right patterns, and set up the infrastructure.
Book an orchestration design session →