Selector Out (CLIP)...

SelOutCLIP ("Selector Out (CLIP)") is the fan-out half of the pack's Selector family, and it's the mirror image of the SelIn nodes. Where a SelIn node takes eight inputs and emits one, SelOutCLIP takes one CLIP input and emits eight outputs - and only the output matching model_type carries the signal. The other seven are None, which in ComfyUI means whatever's downstream of them simply doesn't execute.

So the mental model flips. The In nodes select which upstream branch feeds one consumer; the Out nodes select which of several downstream consumers gets the one upstream signal. If you have a single text encoder and want to control which of eight branches - eight different prompt-encoding setups, eight different KSampler chains - actually runs, SelOutCLIP is the valve. One model_type number, fed by a RecourseCkpt broadcast, and the graph activates exactly one lane.

How it works

model_type (1–8, required) picks the output. The single clip input comes in, and the node places it on OUT_<model_type> while every other output is None. Because ComfyUI skips nodes whose inputs are None, the seven inactive lanes cost you nothing - that's the "selector" behaving like a circuit breaker, not a passive wire. OUT_1 lines up with SD1, OUT_2 with SDXL, OUT_3 with Flux, and so on down the pack's standard table, so the numbering stays consistent with everything else.

Inputs & outputs that matter

• model_type (INT, required) - which output lane activates.
• clip (CLIP, optional) - your one text encoder to fan out.
• OUT_1 … OUT_8 (CLIP) - eight potential lanes; only the selected one carries the CLIP.

Installing it

The pack standard. ComfyUI Manager → search comfyui-selector → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/exdysa/comfyui-selector

Restart and it's under Selector_Recourse/Out. No requirements.txt, no model files, no network access.

Gotchas

• This is usually the more awkward direction. Most multi-model graphs want "many sources, one consumer" (SelIn), because your model loaders sit upstream. The Out direction shines when you've got one source feeding a choice of downstream pipelines. If you're not sure which you need, you probably want SelIn.
• None on inactive outputs means nodes connected there won't run or show errors - which is the feature, but it makes debugging confusing if you forget a node is attached to an inactive lane.
• It's a valve, not a router-with-memory: change model_type and a different lane fires next run. Single-author pack (GPL-3.0, quiet since early 2025) - small, but the circuit-breaker behavior is exactly right for "only run the branch that matches the loaded model."