◎ Radiance Reroute

Reroutes exist for one reason: to bend a wire so your graph doesn't look like a plate of spaghetti. ◎ Radiance Reroute does that and then goes one step further - it lets you put a name on the wire, right on the node, so a month from now you know that pink cable is the refined mask and not the base latent.

This is a legibility node, not a logic node. It does absolutely nothing to your data - which is the entire point, and worth saying twice because people keep expecting reroutes to do something. It's a named junction. If your workflow is small, skip it. If you're building the kind of graph where wires cross three times and you can't remember which latent goes where, this is the cheapest readability upgrade available.

How it works

It's a pass-through on ComfyUI's * wildcard type, so it accepts any data - image, latent, model, conditioning, string, whatever you throw at it - and returns exactly what it was given. The route function is literally return (data,). The label is stored as a widget and drawn on the node; it's purely informational and optional, so old workflows that connected only data keep working untouched.

Two details worth knowing. First, the node marks itself as never-cacheable (IS_CHANGED returns NaN), so it always executes and always passes fresh data - no stale-reroute surprises mid-workflow. Second, it's deliberately minimal compared to its sibling ◎ Radiance Reroute+, which adds color coding, icons, styles, and group tags. The docs are explicit about the split: use this plain one when you just want a labeled junction without visual weight; reach for Reroute+ when you want the full annotation treatment.

The inputs that matter

There are exactly two, and one of them is optional:

• data - required, wildcard. Connect whatever you're routing.
• label - optional string. A short name for the wire, shown on the node. The tooltip's examples tell the story: 'base latent', 'refined mask', 'cfg scale'.

One output, data - the same thing you put in, unmodified.

How to install it

It ships with the radiance pack. Install the pack via ComfyUI Manager by searching "Radiance", or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/fxtdstudios/radiance.git
cd radiance
pip install -r requirements_windows.txt

Restart ComfyUI, and it's under FXTD Studios/Radiance/Layout. If you only want the reroute, you're still installing the whole 80-node suite - that's the pack structure, and it's not worth fighting.

Common issues

Honestly, there isn't much to go wrong with a pass-through node. The realistic failure mode is conceptual: people wire a reroute expecting it to filter or transform, then get confused that the output is identical. It's a wire, not a tool. The other gotcha is placement - if you name every wire in a graph with this node, the canvas fills with labels and you've recreated the clutter you were trying to remove. Label the wires that matter (the ones that cross or feed a fork) and leave the rest alone.

It won't save you from needing a context bus or a group muter when the graph genuinely outgrows wire-routing (that's a different problem, covered by the plumbing of the ecosystem). But as the first step in taming a graph, a labeled reroute is hard to beat.