Bridge Input (CLIP)

CLIP is the text encoder that turns your prompt into conditioning - the thing that sits between the prompt text and the KSampler. Bridge Input (CLIP) is ComfyBridgeIO's named tap on that stream, and like the MODEL and VAE variants it's more landmark than injection point.

The node has an optional value input socket (CLIP) and a single value output socket (CLIP). You wire the CLIP from your checkpoint loader (or a standalone CLIP loader) into the input, then feed the output to your CLIP Text Encode node. The Python client can't serialize a CLIP model into a JSON patch - it's a big in-memory object, not a value - so this bridge's real job is structural: the name widget tags the spot, and bridge.get_schema() reports to the agent that "the text encoder enters here," which is exactly the info an agent needs to reason about whether a workflow's prompt path is intact.

There's a subtle reason this matters for agent-driven setups. The prompt text that the agent injects flows through a STRING bridge into the Text Encode node, and the Text Encode node needs a CLIP. If the CLIP stream is buried in an unlabeled loader connection, an agent inspecting the workflow can't tell where the encoding happens. A named CLIP bridge makes the chain legible: prompt STRING bridge → Text Encode → sampler. Same contract, one named node per conceptual stage.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/cbpark84/ComfyBridgeIO

Restart ComfyUI, or ComfyUI Manager → search ComfyBridgeIO → Install. No model files shipped by this pack (your CLIP comes from your checkpoint or a dedicated loader), no heavy deps. Python client optional (pip install -e in the repo; aiohttp, websockets, Pillow). The README's clone URL says nicekate/ComfyBridgeIO - stale, use cbpark84 as above.

Common issues

The unwired-input trap applies again: no CLIP connected means the Text Encode gets nothing and the graph errors at that node. And a heads-up for the FLUX crowd - FLUX's text encoder is a separate T5 model; if your workflow uses one, wire the CLIP bridge off the right loader or you'll get the "CLIP is not compatible" class of errors downstream. The bridge itself won't save you there; it only passes through what you give it.