Cloud LTXAV Text Encoder Loader

LTX-2 (Lightricks' 19B audio-video model) doesn't use a small CLIP tucked inside the checkpoint. It wants a serious, separate text encoder loaded as its own node - locally that's the LTXVGemmaCLIPModelLoader you see in any LTX-2 template. This Cloud node is that same step, done on Comfy Cloud's side of the wire. You add it to a cloud chain, and it contributes an LTXAVTextEncoderLoader entry to the workflow JSON that gets shipped to Comfy Cloud, returning a CLOUD_CLIP handle you feed into a Cloud CLIP Text Encode.

Here's the quirk that makes this node different from every dropdown-driven loader in the pack: all three of its inputs are plain STRING fields. No dropdown. The cloud's text-encoder options list is huge and drifts as Lightricks adds encoders, so the author chose to accept any string and let the cloud validate it. The source comment puts it plainly - copy the value from your local LTX workflow's widget to be sure.

Inputs

• text_encoder - the encoder filename. Default is umt5_xxl_fp8_e4m3fn_scaled.safetensors.
• ckpt_name - the LTX-2 checkpoint, default ltx-2-19b-dev-fp8.safetensors. The encoder and checkpoint are declared together because that's how the LTX-2 loader rolls.
• device - default "default". Leave it alone unless you know the cloud worker needs a specific device hint.

Output is a single CLIP of type CLOUD_CLIP, the text-encoding half of your conditioning chain. It flows into a Cloud CLIP Text Encode node to make positive/negative conditioning.

Installation

The pack is ComfyUI-CloudAPI-worker:

cd ComfyUI/custom_nodes
git clone https://github.com/Dobidop/ComfyUI-CloudAPI-worker

Then cp config.json.example config.json, paste an API key from https://platform.comfy.org/profile/api-keys, and restart. It's in ComfyUI Manager by pack name; deps are requests, Pillow, safetensors only.

Gotchas

• The strings have to match cloud filenames exactly. Because there's no dropdown, a typo or an old name fails on the cloud side with an API error, not a friendly local one. The escape hatch is a Cloud List Models node with folder=text_encoders to see what the cloud actually reports.
• This is an LTX-2 node through and through. If you're building a non-LTX chain, the regular Cloud CLIP Loader is the one you want; this exists because LTX-2's loader is a different shape.
• Proof-of-concept caveat applies to the whole pack: it's a small community project, the author posted it on r/comfyui as a "very basic proof of concept," and the LTX-2 path in particular is verified mainly against the included example workflow. Expect to debug the occasional mismatch.