Compose, don't repeat.
Nest agents inside agents.
Save any workflow as a sub-agent. Call it from anywhere as a single node with typed inputs, typed outputs, and a version pin. Build a private team library of reusable building blocks. Recursive composition with cycle detection. The agentic equivalent of well-named functions.
Build a private library. Reuse, don't duplicate.
Edit freely. Callers never break.
Sub-agents compose with
Frequently asked
A sub-agent is a saved workflow that can be called from another workflow as a single node. It has typed inputs, typed outputs, an independent version history, and a contract that downstream agents depend on. Sub-agents make complex pipelines composable instead of copy-pasted.
Functionally they're the same workflow. The difference is in how they're consumed - a sub-agent has a defined input/output schema, is callable as a node, and supports version pinning so changes don't break callers. Promote any agent to a sub-agent in one click.
Yes. Recursive composition is supported, with cycle detection and depth limits. A typical pattern is a 'utility' sub-agent layer (formatters, classifiers, validators) that gets called by many higher-level workflows.
Every save creates a new version. Callers pin to a specific version (or :latest, or a stability tag like :prod). Editing the sub-agent doesn't break callers pinned to an older version. You bump callers explicitly when you're ready.
Build your first sub-agent
Book a strategy session and we'll factor one of your messier workflows into reusable sub-agents.