Assigns the work
Decomposes one objective into parts and hands each to the right agent.
Conclave · Orchestration
Conclave
Orchestrate a team of agents.
One agent fills a seat. Conclave runs a team. It coordinates many agents through a shared objective by assigning the work, routing the handoffs, and keeping the whole effort moving toward one outcome instead of scattering into parts.
The problem
One agent has a ceiling.
Real work spans roles, depends on order, and needs the output of one step to become the input of the next. A single agent can only reach so far before the shape of the work outgrows it.
Stand up several agents to cover that and you trade one problem for a harder one: who does what, in what order, with whose output, and what happens when a step fails. Most attempts are brittle scripts that break the moment the work does not run in a straight line.
Coordinating a team is its own discipline. It should not be reinvented for every workflow.
What it does
It runs the team, so you don’t wire it.
Conclave takes one shared objective and drives a team of agents to finish it. You describe the outcome; it handles the coordination that a team demands.
Routes the handoffs
The output of one agent becomes the input of the next, with no human moving it by hand.
Holds it together
When a step stalls or fails, the run keeps moving instead of falling over.
It is multi-tenant and managed, built from the ground up to run real workflows rather than demos. The coordination is the product: you get the team, not the plumbing.
Resilience
A stalled step doesn’t sink the run.
The fragile part of any multi-agent effort is the seam between steps. One agent goes quiet, one output arrives malformed, one call times out, and a hand-wired script takes the whole run down with it. Conclave is built the other way around: the work in progress is durable, so a failure is a step to recover, not a run to restart.
The effort survives the parts. When one step falters, the rest keeps moving.
Works with Tapestry
Put a governed remote worker in any role.
Conclave fills each role from its provider catalog. Assign a role to Tapestry and that role is filled by a governed remote worker. It works without supervision, its output is independently checked against rules you set before it ships, and what comes back carries the evidence behind it.
Conclave coordinates the team. Tapestry is what you put in the roles that have to stand up to review.
Your data
Every run is isolated to you.
Each workflow runs in its own sandboxed, per-customer environment. That environment is dormant by default. It only exists while your work is running, and it is torn down when the run completes. One customer’s workflow is never reachable from another’s.
Coming soon
See Conclave on your own workflows.
Conclave is open for early access. Tell us the work you need a team to run, and we’ll show you what coordinated, accountable agents look like on it.
Request early access