Int Passer

Int Passer does nothing. It takes an integer in and hands the exact same integer out. And "does nothing" is precisely why people install packs like Eclipse - because a workflow that's too tangled to read is a workflow you'll eventually break. A passer is a labeled relay: it lets you route an INT value across a busy canvas without dragging a wire through ten nodes, and it gives that wire a name so the graph stays legible.

The mechanism

One input socket (INT, default 0), one output socket (INT), a straight pass-through. There's no conversion, no clamping, no math - the value that goes in is the value that comes out. The whole job is spatial and organizational: you can wire an integer from the top of your graph down past a wall of nodes, or bounce it through a passer placed right next to the node that consumes it, so the connection is short and visible. In a busy workflow, a wire that spans the canvas is a wire that gets accidentally rerouted when you move something; a passer shortens the run.

The key detail for ComfyUI beginners: this is a typed passer, so it only carries INT. That's a feature, not a limitation. Because the type is fixed, ComfyUI will type-check your connections and refuse to wire a string into it - which is exactly the error-catching behavior that keeps workflows debuggable. Eclipse's Router category ships a whole family of these, one per type (Float, String, Image, Latent, Model, and more), and they exist so you can keep wires typed instead of reaching for a type-erasing any-node. The community has a documented allergy to nodes that erase types for convenience - they make graphs impossible to debug - and typed passers are the responsible alternative.

Inputs and output

• input - the integer to pass through, default 0.
• output - the same integer, verbatim.

When you'd actually use it

Two common cases. First: a seed or steps value generated at the top of the workflow that needs to reach a sampler buried in a subgraph - drop a passer beside the sampler, route to it, done. Second: when a primitive value needs to feed a node in a different group, a named passer acts as a visible milestone so you can see what is flowing where at a glance. If your workflow is small and tidy, you don't need it. If it's the usual sprawling multi-model graph, you'll be glad the pack includes it.

Install

Part of ComfyUI_Eclipse - install the pack once:

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

Or search ComfyUI_Eclipse in ComfyUI Manager and restart. Zero dependencies beyond the pack. If you find yourself thinking "I just need this number over there," this is the node. If you find yourself thinking "I need this anything over there," the Router category's generic passers cover that too - but start with the typed ones.