Anything Everywhere

Three KSamplers, one VAE, one CLIP, and a canvas that looks like a bowl of noodles. Anything Everywhere is the node that lets you drop that one VAE near the top of the graph and never draw the wire again.

What it is

One node, any number of sources. Whatever you wire into it gets offered to every unconnected input of the same type in the workflow when the prompt is built - root graph and subgraph nodes alike. Wire a VAE output in, and every free VAE input in the graph quietly gets it. Leave the node bypassed and it does nothing at all, which is the switch you'll use more than any setting.

The line it sits on is not new. chrisgoringe's cg-use-everywhere invented the shape (Anything Everywhere?, Prompt Everywhere), and the community argument about it is well documented: a post titled "Please Stop using the Anything Anywhere extension" pulled +96 and 87 comments on the grounds that routing any output to any input regardless of type makes a workflow impossible to debug. That complaint is fair, and it's about what you point it at, not about the node.

How it works

The Python class is a no-op that never executes - this is a frontend node. The JavaScript patches the API prompt returned by graphToPrompt, injecting the extra links, which has a genuinely useful side effect: queueing and Export (API) both contain the links. Export the API prompt and it runs correctly on another machine, or on a serverless backend with no canvas at all. (That is exactly the feature Use Everywhere users were asking for years ago - "a button which replaces the UE nodes with actual links, that way the workflow is compatible outside of the UI".)

On the canvas it tells you what it's reaching: inputs it feeds glow in the link's colour, other free inputs get a small dot, and the node wears a green badge in its title bar (yellow when a regex restricts it, dim when it feeds nothing). The translucent phantom links only draw when the node or a target is selected or under your pointer - Settings → BCNodes › Anything Everywhere controls how eager it is.

Two node properties (right click → Properties Panel) narrow the blast radius: title_regex filters target nodes by title, input_regex by input name. A node that sets a regex takes precedence over one that doesn't.

The node exposes a single optional wildcard slot named anything. The canvas grows additional slots as you wire them - one empty anything slot always waits at the bottom for the next source - and it has no outputs, which is correct: it is a broadcaster, not a pass-through.

Where it earns its keep

Shared, boring, single-instance values: the VAE, the CLIP, a control image every branch needs, a seed. Things there is exactly one of and that you never want to trace.

Where it bites you is the opposite: model and conditioning wires. If the thing that distinguishes branch A from branch B is a broadcast, your graph now has no visible reason for its own output. The debugging tax is real, and it's the KB's standing warning about type-erasing convenience nodes. My rule of thumb - broadcast the boring constants, draw wires for anything you're still iterating on.

Installing it

ComfyUI Manager, search ComfyUI-BCNodes. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/0xBeycan/ComfyUI-BCNodes
pip install -r ComfyUI-BCNodes/requirements.txt

Restart ComfyUI and reload the browser tab - the whole node is frontend code, so a stale tab means a node that appears to do nothing. requirements.txt only installs postfx and caption-audit for other nodes in this pack; this one needs nothing.

Common issues

A prompt built without the frontend has no links. This is the big one. Run a hand-written API prompt or a bare-bones serverless workflow and validation fails with Required input is missing, because there was never a frontend to write those links in. Export from the UI and you're fine; assemble a prompt in Python and you must add the links yourself.

The source has to be in the root graph. A source that is a subgraph node's output is not resolved, and the console says so.

Two packs, same node name. If you also run Use Everywhere, you'll have two nodes called Anything Everywhere - the BC one is BC_AnythingEverywhere under BCNodes/workflow. Check the category when you're not sure which you dragged out.

Muted or bypassed is silent. That's the design, but it's also the failure mode: someone bypassed it while testing, and now a random input three screens away is unconnected with no visible cause.