◎ Radiance Reroute+

ComfyUI reroutes exist for one reason: to keep a graph a human can read. They bend wires so they don't cross the canvas diagonally, and they do nothing to your data. Radiance's Reroute+ is that, plus the fix for the reroute's eternal weakness - most reroutes are mute little dots that give you no idea what's flowing through them. This one is a labeled, colored, iconed pill that tells you.

It's a "professional labeled reroute," per the pack, rendered as a styled pill by the pack's radiance_layout.js extension. Everything about it is legibility: you name the wire, tag it, color it, give it a description tooltip, and optionally show the runtime type right on the pill. For anyone who's spent an evening untangling a "wall of spaghetti" - the corpus is full of people who hate messy noodles - this is the tidy-cable-management answer.

The inputs

• data - a * wildcard input, meaning it passes anything: image, latent, model, string, whatever. It comes out unchanged on the data output. That passthrough is the whole mechanical contract of a reroute - the node adds nothing and removes nothing.
• label - 1–3 words shown on the pill ("base latent", "cfg 7.5", "refined mask").
• group - a section tag ("Encode", "Decode", "ControlNet", "Post") that the JS extension can highlight or fold by.
• description - a multiline tooltip for collaborators; explain the non-obvious wiring decision here.
• color - Auto (inherits from the data type: IMAGE=green, LATENT=pink, MODEL=orange, CLIP=yellow, VAE=red, STRING=gray) or any of ten explicit colors. The auto-color alone is worth it - you can scan a graph and instantly see which wires are models and which are latents.
• icon - a pipeline-stage emoji prefix (flow, signal, image, grade, model, branch, output, input, …).
• style - Pill (default), Tag, Arrow, Dot, or Banner. Banner is the one that doubles as a section divider.
• show_type (default off) - appends the runtime Python type or tensor shape to the label. Flip it on during development to confirm data is flowing as expected, off for clean production graphs.

Outputs: data (passed through unchanged) and type_info (a STRING describing the runtime type - wire it to a ShowText node if you want the type visible without decorating the pill).

Where it fits, and the honest alternative

This is a layout node - in the plumbing taxonomy it sits squarely in the legibility layer alongside rgthree's reroutes, bookmarks, and group muters. It does not generate anything and it will never be what's wrong with your workflow. The catch: the fancy rendering depends on radiance_layout.js, so if you're on a frontend where the extension misbehaves (the Nodes 2.0 frontend broke third-party rendering for several packs), you may see a plainer node - the data passthrough still works regardless.

If you only need a plain reroute, ComfyUI's core one is free and battle-tested. Reroute+ earns its place when your graph is big enough that labeled, color-coded wires save you real minutes per session - which, at 79 Radiance nodes, is a crowd that exists.

Install

Part of Radiance - ComfyUI Manager → search Radiance, or:

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

Restart. Under FXTD Studios/Radiance/Layout.