trRouterLonger

If you've read about trRouter, this is its longer cousin, and "longer" means exactly one thing: it has two more sockets. Where trRouter ferries model, clip, vae and two conditionings, trRouterLonger adds an image and a latent to the bundle - seven pass-through connections in a single node, useful when the thing crossing your canvas isn't just the checkpoint plumbing but also a preview image and a working latent.

Like its sibling, it's a pure pass-through. It loads nothing, computes nothing, and has no settings. Every input is optional, and every output mirrors its matching input in order: model, clip, vae, conditioning1, image, latent, conditioning2. You can wire in just the two or three sockets you need and ignore the rest.

When you'd actually use it

trRouter covers the common case of "get the checkpoint stuff across the canvas." trRouterLonger earns its extra sockets in the less common one: a graph where an image and a latent travel alongside the model bundle - for instance, a pipeline with a sampling stage in the middle, where you want to keep a preview image and its latent within easy reach of a decode-and-display section further down. Instead of drawing seven individual cables past everything else, you drop one router node, run the wires into it once, and tap the tidy cluster downstream.

There's no mechanism to explain beyond that - the node's execute returns its inputs unchanged (plus a debug print to the console, which is harmless). All-optional means a partially wired router is fine, not an error.

Installing it

Comes with the trNodes pack, and like trRouter it needs zero extra Python packages:

cd ComfyUI/custom_nodes
git clone https://github.com/trojblue/trNodes

then restart ComfyUI. ComfyUI Manager (search "trNodes") clones the same repo. If you already installed the pack for trColorCorrection or trLayering, this node is already there - nothing else to do.

The honest take

This is the definition of a marginal utility node. If you didn't need trRouter, you definitely don't need this - ComfyUI's native Reroute and especially rgthree's Context (which carries a whole bundle down a single wire) cover the same organizational problem more elegantly. But if your workflow genuinely ferries an image and a latent alongside the model trio, a seven-socket pass-through is a tidy way to keep it readable, and it costs you nothing since it ships in the same pack. Reach for it when the alternative is seven cables across a wall of nodes, and not a moment sooner.