Team parallel branches assigned by a step

  • Desktop app
  • All plans

What it does

Two or more connections without a condition out of one team step run their targets as parallel branches, which rejoin on a common next step. By default every branch starts with the same handoff: three reviewers drawn in parallel read the same summary and each one decides alone what to look at.

With Parallel branches ticked on the step before the split, that step becomes the dispatcher (an analyst, a lead). It is told which branches it can start, and when it finishes it decides which ones run and writes each one its own brief: "security: check the new upload endpoint", "performance: profile the list page". Only those branches start, each with its brief at the top of its prompt. A branch it leaves out does not run, and the step after the split waits only for the branches that started. If the step assigns nothing, every branch starts with the same handoff, exactly as without the option.

This is how a team gets several specialised instances of the same role (three reviewers, two developers, the same saved agent twice), each with its own job for this run: draw them as parallel branches, give each one its own name and step instructions, and let the step before them decide who works on what.

Duplicate step makes those instances quickly: it copies a step (same agent, role, model, prompt and options) so you only change its name and instructions.

Where to find it

  • Teams window > select a team > click the step right before a split > properties panel > Parallel branches > "This step picks which parallel branches start and briefs each one". The field only shows on a step followed by two or more parallel branches (and on a step where it is still ticked after its split was removed, so it can be unticked).
  • On the canvas, a step with the option shows a split badge ("Picks and briefs the parallel branches").
  • Duplicate step: the copy icon next to the bin, at the top of a step's properties panel. Not offered on read-only templates.
  • During a run, the run timeline shows each branch's brief under the handoff to it, labelled Assignment.

How to use it

  1. Draw the specialists after the analyst step: one step per specialty, each connected from the analyst without a condition, and each connected to the same next step (the join). Duplicate step copies a step; the copy is named "<name> 2" when the original has a name, lands next to it and is selected. Its connections are not copied: wire it yourself.
  2. Give each branch its own Display name and Step instructions (what that specialist is for). Tick Own checkout on the branches that write or measure, so they do not overwrite each other's files.
  3. Select the analyst step and tick Parallel branches. Write its instructions as usual ("analyse the ticket"): the app adds, by itself, the list of branches it can start and how to brief them.
  4. Run the team. When the analyst finishes, only the branches it briefed start; the timeline shows what each one was asked to do.

If the analyst's flags take a conditional connection elsewhere instead of the split, its assignments are ignored and the run follows that connection.

Settings

  • assignsBranches (step field; team editor > the step before a split > Parallel branches; off by default; since 2026-10-27): the step chooses which parallel branches start and writes each one its brief when it completes. A step without the split after it gets a graph warning and the option does nothing.

Agent tools (MCP)

  • teams_save: assignsBranches: true on an agent node (also through nodePatches). A ticked step with no split after it is saved with a warning. capabilities_get({topic: "teams"}) describes the option under parallelFanOut.
  • Inside a run, the dispatching step sees the branches it can start in team_get_context under parallelBranches (id, name, role and the opening of each branch's own instructions).
  • It passes assignments: [{ branch, brief }] to team_complete_step, one entry per branch to start. branch is the id listed (an exact step name is accepted too), brief is up to 2000 characters. A branch it cannot start, the same branch twice, or assignments on a step without the option is refused with the list of valid branches, and the receipt says which branches it started ("Branches you assigned (2 of 3): Security, Performance. The others do not run.").
  • Each started branch finds its brief at the top of its prompt and in team_get_context (assignment in the payload it received).

Providers

All providers, no difference: the choice is made through the team tools every CLI of a run receives, and the brief is part of each branch's prompt whatever its CLI.

Mobile

Nothing to set on the phone: the team editor, Parallel branches and Duplicate step are on the desktop. A run started from the phone applies the option exactly like the desktop: the step picks and briefs its branches, and only those start. The phone shows the run's steps as usual; the briefs are shown in the desktop run timeline.

Limits

  • The step chooses among the branches drawn after it: it cannot create new branches while the run works. The most agents a split can run at once is the number of branches drawn, so draw one per specialty you may need; the step leaves out the ones a task does not need.
  • Branches stay one step deep and rejoin on the same next step, like every parallel split.
  • A loop back to the dispatching step lets it assign again on the next cycle, possibly other branches.
  • A branch that was left out stays Pending in the run box, like a step on a route the run did not take.
  • Since 2026-10-27.

Common questions

  • Can one step analyse the task, then launch several specialised agents in parallel, each with its own instructions? Yes: that is this option. Draw the specialists as parallel branches after it, tick Parallel branches on it, and it starts the ones the task needs with a brief for each.
  • Can a team hold several agents of the same role, or the same saved agent twice? Yes: add the step again or use Duplicate step, and give each one its own Display name. In Team mode, once every step of that role has a name, each one is reached by its own address (Agent Teams).
  • What happens if the analyst forgets to assign? Every branch starts with the same handoff, as a plain split; the step is told so when it completes.
  • Does a branch that was left out cost anything? No: no agent is launched for it and no cycle is counted.
  • Agent Teams: the team editor, parallel splits, Own checkout and the run box.
  • Team step entry check: a command that decides, before a step starts, whether it runs at all.