Build · Workflow bundles
One wizard, a whole team of agents, wired together.
Some jobs were never meant for one agent. A product launch needs research, drafting and outreach roles, not one generalist doing all three badly. A bundle creates that whole team in one step.
Why one wizard, not ten
Ten agents built one at a time drift from each other.
Standing up a team of agents individually means ten separate setup sessions, ten chances to configure a guardrail slightly differently, and no guarantee they were ever meant to work together in the first place. A bundle creates the Group and its agents as one coherent shape.
What a bundle actually sets up
Not just a batch of agents. A team.
- Roles pre-assigned
- Each agent in the bundle already knows its part of the job. Nothing arrives generic.
- Guardrails per role
- A bundle carries a different guardrail set per agent, not one blanket policy for the whole team.
- Handoffs pre-wired
- Where relevant, the agents already know how to pass work to each other. See Agent pipelines.
- Provisions in the background
- The Group appears immediately; its agents stream in behind a progress banner, with retry if one fails.
Each agent in a bundle is built from an Agent template; once created, all of them show up together in your Agent fleet.
FAQ
Teams launching a bundle are asking
What happens if provisioning a bundle partially fails?
The Group is created immediately and its member agents stream in behind a progress banner with retry. A failed agent does not block or corrupt the rest of the bundle.
Can we customise a bundle's agents after it's created?
Yes, exactly like any other agent. A bundle is a fast starting shape, not a locked configuration.
Who owns the agents a bundle creates?
Whoever created the bundle, by default, the same ownership rule as an agent created any other way. It shows up immediately in the fleet grid, not left unassigned.
Stand up a whole team, wired together, in one wizard.
Twenty minutes with the founder. No slides. The real product.
