ComfyUI Node

Any Passer

The do-nothing node that fixes real workflow problems

By r-vageΒ·Created 10 months agoΒ·Updated a day agoΒ· 31
Any Passer
  • input
  • output

Any Passer takes one input of any type and outputs it unchanged. It computes nothing, transforms nothing, adds nothing. On paper it's the most useless node in ComfyUI_Eclipse - in practice, do-nothing passthrough nodes are one of those "features that should be built-in" things, and a good one earns its place in graphs that are too big to read.

Why you'd want a node that does nothing

Three genuinely useful jobs:

1. Taming the noodles. A wire that has to cross half the canvas to reach its destination makes a graph unreadable. Drop an Any Passer partway along the route and re-run the wire from there - you've broken one long diagonal into two short legs without touching the data. It's the poor man's reroute, and it's type-agnostic, so it works for any wire.

2. Resolving "connect anywhere" ambiguity. ComfyUI's wildcard sockets accept anything, which is usually a blessing - until you have a node with several optional inputs and you want to force one specific connection to be treated as the primary. Passing a value through a clear, named node makes the graph's intent explicit: "this is the model," not "one of several wires that happen to touch this socket."

3. Debugging anchor points. Because a passer is a real node with a real output, you can attach a preview, a Show Any, or a note to it. When something downstream misbehaves, the passer gives you a clean place to inspect exactly what's flowing through, without rewiring the whole branch.

How it works

It's a single wildcard input input, a wildcard output output, and a straight hand-off in between. The only logic is defensive: None, empty lists, and lists of Nones are passed through as None rather than causing a type error. Nothing else happens - no caching tricks, no IS_CHANGED games, no side effects. That predictability is the point.

Where it sits in the family

Eclipse ships a whole roster of typed passers (Image Passer, Latent Passer, Clip Passer, Audio Passer, Basic Pipe Passer, and more) that enforce one specific type. Any Passer is the untyped version - reach for it when you're routing a bundle whose type you don't care to name, or when the same passer might carry a different type in different runs of the workflow.

Installing it

Part of ComfyUI_Eclipse, installed once:

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

Restart ComfyUI (or ComfyUI Manager β†’ search "ComfyUI Eclipse"). No dependencies beyond the standard library.

Gotchas

The pack-wide one: ComfyUI_Eclipse was formerly RvTools, and v4.0.0 removed all legacy nodes - old workflows fail to load until you run the Workflow Migration Tool node (or python tools/migrate_workflow.py <workflow.json>) to rewrite old IDs with a backup. And one honest caveat about the whole passer family: if you're adding passers purely for organization, don't go overboard - ComfyUI's own reroute is the cleaner tool for pure wire-bending. A passer earns its keep when you also want a named, inspectable anchor, not just a prettier line.

CategoryπŸŒ’ Eclipse/ Router

Inputs (1)

NameTypeDefaultDescription
inputCOMFY_MATCHTYPE_V3Any input to be passed through.

Outputs (1)

NameTypeDescription
outputCOMFY_MATCHTYPE_V3β€”