String Passer

String Passer is the most honest node in this pack: it takes a string in and hands the exact same string out, changing nothing. If that sounds useless, you haven't hit the ComfyUI moment where a wire has to cross half the canvas and you're dodging model connections, or where a node sits behind a switch and you just want the type to line up cleanly. Passers exist to keep graphs legible - the ComfyUI equivalent of a via on a circuit board.

The mechanism is one line: input in, output out, STRING type on both ends. No processing, no storage, no transformation. Its whole job is routing and readability. ComfyUI's execution model means a passer is effectively invisible to the data - the value isn't duplicated or delayed in any way that matters - so you can add as many as you need without worrying about behavior changes.

Why you'd actually reach for it

Three situations. One: physical layout - a string needs to travel across a busy graph and you want a clean path instead of a wire threaded through other nodes. Two: keeping types explicit - this is the typed passer (STRING in, STRING out), so it slots into sockets that demand a specific type without the ambiguity of an any-type node. Three: it's part of a family - the pack ships passers for every major type (Model, Clip, Vae, Latent, Image, Mask, Conditioning, and so on), and the String version is the one you'll use most because strings are the most-fan-out data type in generation workflows. A single seed or prompt value feeding five consumers is exactly the repetition this family fights.

If you're new to ComfyUI, the mental model: any time you think "I need this string over there without it getting tangled," a passer is the tool. It's also a fine placeholder - drop one where a node will eventually go, wire around it, fill in the real node later.

Installing it

Part of ComfyUI_Eclipse:

git clone https://github.com/r-vage/ComfyUI_Eclipse custom_nodes/ComfyUI_Eclipse

Or ComfyUI Manager → search "ComfyUI_Eclipse" → install and restart. No models, no extra deps.

Gotchas

There's essentially nothing to break here - the value passes through untouched. Two honest caveats: a passer adds no caching or history of its own, so don't expect it to hold a value between runs, and an overabundance of passers can make a graph harder to read rather than easier. Use them to straighten wires, not to hoard nodes. And the pack-level note: workflows built before Eclipse v4.0.0 with RvTools-era node IDs need the migration tool; new workflows load clean.