Sonder Guides Bridge End

Sonder Guides Bridge End is the quiet half of the guide loop. Sonder Guides Bridge Start opens the loop and emits one guide per iteration; this node closes it. It reads the guide list from the paired Start, recurses via ComfyUI's Node Expansion when more guides remain, and on the final iteration returns the loop-carried values it was handed. You almost never touch it beyond connecting the wires - but it's the node that makes "a variable number of guides per run" work at all.

That variable-count problem is the reason the pair exists. A selected timeline range might contain three guide frames or eleven, and a fixed chain of guide nodes can't express "however many there happen to be." The Start/End loop expands to the actual count at execution time: Start feeds guide N into the loop body, End decides there's another one and recurses, until the list is exhausted and End passes the accumulated values out the back.

How it works

Two required inputs: project (the Sonder project, so it sees the same execution window as the Start) and flow_control (wired from the Start's flow_control output). The eight value_0 … value_7 inputs and matching outputs are the loop-carried passthrough - anything you thread into the body before the loop survives to be read after it. If your loop body accumulates state across iterations - say, building a combined latent or counting processed frames - that's what these are for.

The mental model to keep straight: Start is where the work happens (new image, new index, new strength each iteration); End is where the loop stops and hands the final state onward. On intermediate iterations End recurses and your body runs again; on the last iteration it just passes value_i through untouched.

Install and wiring

Same pack, same install: 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.

Practical notes from people actually running this:

• Wire both halves or neither. A lone Start or End leaves the loop open and the graph won't behave; the pair is one unit. The pack's example workflow shows them surrounding the guide-processing nodes.
• The value_i sockets are optional. If your loop body doesn't need to carry state, leave them unconnected - they're there for when they're needed, not a toll you pay.
• Don't double-inject guides. The README is explicit: Sonder has the bridge path and the editor's CSV export path, and feeding the same project guides through both double-applies them.

It's the most "if it works, you never think about it" node in the Sonder pack - and that's a compliment. It exists so the Start node can do its job without you managing loop counters by hand.