Yellow Bus - klinter

Yellow Bus - klinter is a routing node, and it solves the most visible problem in big ComfyUI graphs: the wire spaghetti. When a workflow has ten nodes all feeding into one downstream consumer, the canvas turns into a nest of lines that are impossible to trace. A bus node collapses that - inputs on one side, matching outputs on the other, and the wires travel through it like a switchboard instead of tangling across the whole canvas.

The mechanism is the "adaptive typing" part, and it's what separates a bus from a dumb pass-through. Each of the up to 10 input/output pairs (pairs sets how many you use, default 2, max 10) adapts its type to whatever you connect - connect an IMAGE and that pair becomes an IMAGE wire; connect a MODEL and it carries a MODEL. That means you can route different data types through one node without type conflicts, and if an input isn't connected, its output just returns None instead of erroring. The schema declares all 10 outputs (out_1 through out_10), and the JS side expands/contracts the node to match your pairs setting.

Where it genuinely helps: segmenting a large workflow into clean zones. Route your conditioning stuff through pairs 1–2, your image stuff through 3–4, and you can read the graph's structure at a glance. It's in the same family as reroute nodes and other "wire organizers," but the fixed-pair bus model is a coherent pattern - you always know out_3 corresponds to input 3.

Now the practical reality, because it matters for this pack: Yellow Bus is written against the newer io.ComfyNode schema API (comfy_api.latest), and its dynamic-input wiring depends on the pack's JavaScript. That means it only works on a reasonably recent ComfyUI, and if the node misbehaves, your first move is updating ComfyUI core, not reinstalling the pack. The pairs input is the only thing you set - everything else adapts.

Install is the pack standard: search "Klinter_nodes" in ComfyUI Manager, or cd ComfyUI/custom_nodes && git clone https://github.com/klinter007/klinter_nodes then restart. No requirements.txt, no models, just the bundled comfy_api and the yellow_bus.js UI file.

Is it essential? No - you can live without it. But if your workflows have started looking like a bowl of noodles, this is one of the cheapest ways to restore your sanity.