Sonder Cluster

Sonder Switch handles "pick one of N values." Sonder Cluster handles "pick one of N sets of values" - it routes a shared branch selection across multiple lanes, where each lane can carry a different type. Think of it as several switches stacked behind a single selector knob: flip the knob once and every lane swaps to the matching branch at the same time.

The concrete case that made me reach for it: a video workflow where each "style" branch needs three different things at once - a checkpoint, a conditioning, and a prompt text. A single Cluster with three lanes gives you one select that switches all three in lockstep. Without it you'd wire three separate switches and hope you never forget to flip one, which is exactly how you end up with an SDXL checkpoint running against a Flux prompt. One knob, no mismatch.

How it works

Like Sonder Switch, it's built on the V3 schema and lazy evaluation: only the selected branch is evaluated, per lane. The branches input sets how many branches the cluster shows (2 to 32), lanes sets how many parallel rows (1 to 8), and select picks the active branch index across all lanes. Every input is named b<branch>_l<lane> - so b0_l0 is branch 0, lane 0 - and each lane has its own output (labeled A through H).

The type rule is the useful constraint: each lane can be any type, but all branches within a lane must match that lane's type. Lane A can carry models while lane B carries strings - the cluster is heterogeneous across lanes, homogeneous within them. That's the exact middle ground between a single-type switch and the wildcard chaos of routing everything through *.

Install and gotchas

ComfyUI Manager search Sonder Editor, or git clone https://github.com/SonderSaid/ComfyUI-Sonder-Editor.git into custom_nodes, pip install -r requirements.txt, restart. V3-schema node, so it requires a recent ComfyUI build - on older installs it simply won't register, while the rest of the pack keeps working.

The things that trip people up:

• All branches in a lane must match type. The tooltip says it, the validator enforces it, and it will refuse to wire a mismatched socket. Lane types are discovered from the first connection, so connect one full lane first to teach the cluster what it's routing.
• Laziness is per-branch, not per-lane. The selected branch evaluates; unselected branches don't - but shared upstream nodes feeding multiple branches still run.
• Output letters don't equal branch numbers. The A–H outputs are lanes, not branches. Lane 0 is output A, lane 1 is output B, and so on. The select value picks the branch, the letter names the lane you're reading.

It's the node to grab when your switch needs a partner. If you're only swapping one value, Sonder Switch is simpler; the moment you're swapping a whole stack, the Cluster is the thing that keeps the graph honest.