CLIPTextEncodeFlux_motorway_edition

Flux doesn't encode your prompt once - it encodes it twice, through two different text encoders, and bakes a guidance value into the conditioning. CLIPTextEncodeFlux is the node that ties all that together, and this is its Motorway-ed clone: the CLIP comes out of the Motorway by key, you fill in two prompt boxes, and the finished conditioning goes back in under a key you name.

If you've only ever run Flux from a template workflow, you've used this node's plain version without thinking about it. It's the reason Flux workflows have two text boxes where SD1.5 had one, and it's why the "guidance" number in Flux workflows is not CFG - get that last bit wrong and you'll spend an afternoon confused.

How it works

The wrapper pulls one thing out of the Motorway and writes one back:

• INPUT_clip_key - key for the Flux CLIP (default clip). This has to be the dual-encoder CLIP - Flux loads a CLIP-L plus a T5-XXL through the loader - so feed it the CLIP from a CLIPLoader_motorway_edition or a Flux checkpoint, not a plain SDXL CLIP.
• clip_l - the prompt for the CLIP-L encoder (multiline). Natural-language friendly.
• t5xxl - the prompt for the T5-XXL encoder (multiline). Same idea, but this is the encoder that carries most of the semantic load for Flux - the two fields can and often should be worded differently.
• guidance - default 3.5, range 0–100. This is Flux's own guidance value, baked into the conditioning, not CFG. Cranking it doesn't give you "stronger CFG" - it shifts how the model interprets the prompt, and it runs at single-pass cost.
• OUTPUT_CONDITIONING_key - where the conditioning goes, default CONDITIONING.

The node instantiates the real core CLIPTextEncodeFlux, runs both encoders, and stores the result under the output key. The only visible output is the MOTORWAY 🚌💨, and the sampler downstream reads the CONDITIONING key.

On that 3.5 default: the community has a genuine take here. 3.5 is what the official workflows ship with, but it's widely blamed for Flux's "same-face" look; the recurring advice for people in Flux workflows is to drop guidance to around 1.8–2.0, with higher values (4.0–4.5) reserved for realism-LoRA setups. It's a taste knob with real consequences, and it's the one field on this node people actually fight about.

Motorway specifics

MOTORWAY 🚌💨 is required. The defaults assume your CLIP lives under clip; if your loader used a different key, update the field or you'll hit the signature 'MotorwayClass' object has no attribute 'hash_' error. Keys overwrite as they flow down the chain.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/agilly1989/ComfyUI_agilly1989_motorway

Restart, or search "ComfyUI_agilly1989_motorway" in ComfyUI Manager. No pip dependencies; the model files are, as always, on you.

Fine print

The pack is an explicitly-beta side project - README opens "BIG BROKEN WITH ASYNC WILL FIX WHEN I GET THE TIME/MOTIVATION" - and the current hotfix release has the _motorway_edition clone generation commented out of __init__.py, so on the newest main these nodes may not load at all. Workflows referencing them with missing nodes are hitting exactly that. GitHub issues are the channel; the author has stated his Discord DMs get ignored.