CLIP Input Switch

Straightforward per WAS's own description: it switches between two CLIP inputs based on a boolean switch. Wire in two CLIP sources, wire in a true/false, and whichever one the boolean picks is the one that passes through to the rest of your graph.

Why you'd want this

The obvious case is A/B comparison - you've got two CLIP encoders (say, from two different checkpoints, or a base CLIP versus one you've patched with a LoRA) and you want to toggle between them without rewiring the graph every time. Flip the boolean, re-run, compare. It also works as a lightweight feature flag inside a shared workflow: build the graph once with both CLIP sources always connected, and let a single switch (which you could drive from a Text Contains or Logic node upstream) decide which one is actually used for that run.

This node is one of an entire family WAS ships under the same idea - Model Input Switch, VAE Input Switch, Image Input Switch, Latent Input Switch, Lora Input Switch, ControlNet Model Input Switch, Upscale Model Input Switch, and more. All of them share the exact same mechanism, just gating a different data type. Once you understand this one, you understand all of them.

How it works

It's a strict either/or, not a blend - nothing interpolates between the two CLIP inputs, the boolean simply selects which one is passed through unmodified. The output is a single CLIP, ready to plug into a CLIPTextEncode node exactly as if you'd wired the source directly.

That's also its limitation: it only ever picks between two. If you need to choose among three or more CLIP sources, you'll need to chain a second Input Switch off the output of the first, feeding the "loser" of one comparison into the next - workable, but worth planning for if you know up front you'll have more than a binary choice.

Installing it

Part of the full WAS Node Suite pack, not a standalone install:

• ComfyUI Manager - search WAS Node Suite, install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/WASasquatch/was-node-suite-comfyui/, then pip install -r requirements.txt from inside that folder, then restart ComfyUI.

Common issues

There's not much that goes wrong with a node this simple - the main thing to keep straight is that it's a selector, not a merge. If you were hoping for some kind of interpolation or averaging between two CLIP encoders, that's a different (and much less common) operation than what this node does.

The pack-wide caveat still applies: WAS Node Suite has been unmaintained since December 2023, and "Import Failed" errors after updating ComfyUI or another custom node are a genuine, recurring complaint - the pack's own author has acknowledged that ComfyUI updates can bump shared dependencies out from under WAS's older pinned versions. If the whole suite fails to import after an update, reinstalling requirements.txt inside your ComfyUI venv is the usual fix.