RErouter <=

If the other nodes in this pack are small utility pieces, RErouter is the one the whole pack is named after - and it's also the one that needs the most explaining, because there's nothing quite like it in a vanilla ComfyUI install. Its whole job is unpacking: you feed it one wire carrying a bundle of values, and it hands you back fifteen separate typed sockets to pick from.

The single input is _bus, typed BUS_BASE - a type you won't find on any stock ComfyUI node. That's the tell: RErouter is the receiving end of a bus convention this pack defines for itself, not a general-purpose reroute you can drop anywhere. Somewhere upstream in a graph built around this pack, something packs a base checkpoint's model/clip/vae, a refiner checkpoint's model/clip/vae, an empty latent, an upscale model, your positive and negative prompt strings, a seed, three spare integers, and a spare string all onto that one BUS_BASE wire - the README's own usage example, a big styled prompt-grid workflow built alongside Comfyroll Custom Nodes, Impact Pack, and sdxl_prompt_styler, is exactly the kind of sprawling graph this is for. RErouter is what you drop at the point where you actually need one or two of those fifteen values back, instead of dragging that many individual wires across your canvas from the source.

The idea itself isn't new - it's the same problem rgthree-comfy's Context nodes solve, carrying a bundle of connections down one wire so that a workflow too big to read into one screen stays a workflow you can still work in. RErouter is an90ray's own version of that pattern, shaped specifically around an SDXL base-plus-refiner pipeline rather than being general-purpose.

The outputs - what you're actually picking from

Fifteen sockets come out of one bus wire, grouped by what they're clearly meant for:

• MODEL, CLIP, VAE - your base checkpoint's trio.
• MODEL_R, CLIP_R, VAE_R - the refiner checkpoint's equivalents, kept separate from the base trio.
• EMPT_LAT - an empty latent.
• UPSC - an upscale model.
• PRT_p, PRT_n - positive and negative prompt strings.
• SEED - a seed value.
• INT1, INT2, INT3, STR1 - spare integer and string slots for whatever else the workflow needs to carry through.

Each one is typed normally (MODEL, CLIP, VAE, LATENT, UPSCALE_MODEL, STRING, INT), so once it's out of RErouter it wires into anything else in ComfyUI the same way it always would - a KSampler, a checkpoint-dependent node, a save-image filename field, whatever the graph needs at that point.

How to install it

Same repo as the whole pack. ComfyUI Manager: search ComfyUI_RErouter_CustomNodes, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/an90ray/ComfyUI_RErouter_CustomNodes.git

Restart ComfyUI. No models, no extra dependencies.

Common issues & troubleshooting

Nothing to plug into _bus. This is the issue almost everyone hits first, because it's genuinely not obvious from the node alone. BUS_BASE is a custom type this pack defines; a stock ComfyUI install has no node that outputs it, and ComfyUI's type checker won't let you force a MODEL or CLIP wire into it just because you're stuck. If you dropped RErouter into an otherwise-normal workflow expecting it to behave like a generic reroute, that's why it's sitting there disconnected - you need the rest of this pack's bus-packing side feeding it first.

Wondering if this is worth installing just for the reroute idea. If what you actually want is "carry a bunch of connections down one wire so my workflow's readable," rgthree-comfy's Context nodes do the same job with a far larger install base and don't require committing to an90ray's specific fifteen-slot shape. Reach for RErouter specifically if you're following a workflow that already uses it, or you're building the same base-plus-refiner-plus-prompt-grid shape this pack was clearly written for.

Barely any outside documentation. This node has close to no footprint in the wider ComfyUI community - no wiki, no threads breaking down how people use it, nothing beyond one screenshot and two workflow images in the pack's own README. Treat the source in custom_nodes/ComfyUI_RErouter_CustomNodes as the real documentation if you need to go deeper than what's here.