← All posts
SOOT · BLOG

One conversation, a whole team: give the goal to one Soot

With orchestration you give the goal to one Soot. It calls the teammates it is allowed to call and returns a merged result in the same conversation. You do not pick Radar or Editor.

A small team of Soots raises an obvious question: *which one do I ask this time?* One Soot finds signals, one writes, one reviews. If every task means opening a separate conversation and choosing the right one first, the "team" is just a list of separate tools.

According to the Soot orchestration docs, you do not have to work that way.

Give the goal to one Soot

You hand the goal to one Soot. That Soot calls the teammates it is allowed to call and returns a merged result in the same conversation. You do not have to decide whether a task goes to Radar or to Editor. Choosing teammates is the job of the Soot that received the goal.

You → one Soot → allowed teammates → merged result, one conversation

For example: instead of opening three conversations for three jobs, you write one goal for one Soot and read the result in one place.

"Allowed" comes from the host

Which teammates a Soot can call is set by host grants. A group name or a role description in a prompt does not create that permission. For an operator, that is where to look when you want to know which Soot may ask which: read the grants, do not guess from names.

A group template is not a pack

Keep two things apart. According to the docs, a group template is different from a pack, and downloading a group template does not run tools or create a session. Having the team's files does not mean the team is running.

In short

  • One goal, one Soot receiving it, one conversation with the result.
  • The right to call teammates comes from the host's grants, not from descriptions.
  • A team template is not a running team.

Read the source in the orchestration docs. To start with something smaller first, see the Soot docs.