h4 - Oxidine

Every serious ComfyUI graph eventually becomes spaghetti. Model here, VAE there, a CLIP sneaking around the back - forty wires crisscrossing the canvas until you can't tell what feeds what. h4_Live's answer is Oxidine, an "omniproxy" that bundles a pile of connections into a single cable and hands each consumer the right payload when it asks. The README calls it the ultimate wire-declutter tool, and for once the marketing isn't entirely wrong.

How it works

Oxidine accepts up to 50 any-type inputs (input_1 through input_50) and exposes one any-type output. The magic is in how it handles what flows through: instead of forcing you to pick a type, it figures out what each object is and routes accordingly. Feed it a VAE, and when the downstream node calls for a VAE's operations it gets them. Feed it a MODEL and a CLIP on different inputs, and the same single output line serves both - the proxy dispatches by attribute, so decode routes to the VAE, tokenize/encode routes to the CLIP, and patch_model routes to the MODEL.

The backend has a deliberate design constraint worth respecting: the proxy deliberately does not subclass the core types (list, dict, ModelPatcher, VAE, CLIP). That's not an accident - it's what stops ComfyUI's executor from treating it as a list and mapping over it, which is exactly the kind of type chaos that turns a CLIP into a VAE and produces those wonderful "what is wrong with this graph" errors.

What you actually set

No required inputs, no widgets to configure. You wire things in, it routes them out. The inputs are dynamic and any-type, so there's genuinely nothing to configure - which is the whole point. It's a routing valve, not a settings panel.

When to reach for it

The honest answer: when your canvas looks like a plate of noodles and you want one clean trunk line. It shines in workflows where several branches converge on one consumer - for example, when you're building a reusable subgraph and want to hide the plumbing. The trade-off is legibility in a different direction: a node that carries "everything" makes it harder to see what flows where, so it's a decluttering tool for the canvas, not for your understanding. Keep it for graphs you already understand.

Installing it

It's part of h4_Live:

cd ComfyUI/custom_nodes
git clone https://github.com/m3rr/h4_Live
# restart ComfyUI

or ComfyUI Manager → search "h4_Live." No extra dependencies.

Where it can bite you

Any-type routing is powerful and slightly cursed. If you connect something exotic that the proxy's type detection doesn't recognize, it falls back to a passthrough - usually fine, sometimes not. And because the single output is typed *, ComfyUI's type-checking is doing a lot of trusting; when a downstream node chokes, the error message can be bafflingly generic. Debugging a mis-wired Oxidine is harder than debugging the equivalent direct wires, so don't reach for it until the graph works un-bundled. When you do, it's genuinely the least-spaghetti way to carry a model triple across a big canvas.