Repeat (Close)

Repeat (Close) is the other half of the pack's counted loop, and on its own it does nothing you'd ever wire up by hand - you're meant to let the 🔗 Add / link Close button on Repeat (Open) create it for you. So think of this page as "what the Close node is doing while your loop runs," because that's where the interesting machinery lives.

What it does

You wire the matching Open's flow into Close's flow input and its index output into Close's index input (the Auto-pair button does both), then feed your per-iteration state into the wildcard value_* inputs. Each pass, Close checks the count:

• If the current iteration is still below count on the Open node, it expands the graph: it clones the whole loop body - every node feeding Close, plus the Open node itself - into a fresh subgraph, advances the Open's carried state (loop_index and the value_* slots) to the next iteration, and wires the clone's results back into a copy of itself. One queue run executes the whole loop.
• Once index reaches count, it stops expanding and hands the final value_* state downstream.

That's the entire contract: Close is the loop's "is there another pass?" check plus the graph-expansion engine, all in one node. It's a stateful loop with feedback - iteration N's output becomes iteration N+1's input - which is different from For Each, where each element is independent.

The inputs that matter

There are only two required: flow (the internal link that identifies which Open this Close belongs to) and index (which iteration we're on - wire it from Open's index output). The value_0..value_19 inputs are the carried state, and they're wildcard: images, latents, strings, lists, whatever your loop body needs to thread forward. Outputs mirror the inputs - the final state after count passes.

Two gotchas that bite people

count on the Open node must stay a widget value, not a wired input - it's read when the loop expands, before execution, so a dynamic count won't work. And keep in mind every pass clones the body: the graph you see in the editor is a template, not the executed graph, so a 100-iteration loop is 100 copies of your body stitched together. It works, but it's why the tooltip warns to keep count sane - and why the pack's own docs call a runaway loop "a polite way to burn an afternoon."

Installing it

Same pack, same story: ComfyUI Manager → search "Kinburg-Nodes", or git clone https://github.com/Kinburg/Kinburg-Nodes into ComfyUI/custom_nodes, restart. No dependencies. If the Close node ever seems to do nothing, check the wiring of flow and index - a Close without its Open's flow is a node with no loop to close.