KfDebug_Clip

CLIP objects are the most "just trust it" things in a ComfyUI graph. They're opaque model handles you wire from a checkpoint loader into a text encoder, and you never actually look inside one - until a workflow gives you an error and you realize you have no idea what your CLIP even is. KfDebug_Clip is the passthrough debug node for that case: it inspects the CLIP, dumps what it learns to the console, and passes the exact same object out the other side.

It's part of the pack's debug family, and like the others the killer feature is that it's a passthrough. You splice it onto a wire, run once, read the console, and leave it or delete it - the downstream graph sees the identical CLIP either way. For a type as opaque as CLIP, that low-friction access is worth more than you'd think.

How it works

The inspection routine is shared across the debug family. For a CLIP it logs the object's type, then looks for shape and dtype information - CLIP wrappers are Python objects rather than tensors, so you'll mostly see the type and whatever attributes the specific wrapper exposes (which is genuinely useful: the type line will tell you which model family your CLIP belongs to, and that alone explains a lot of "why won't this encode" errors). If the object has a keys() or item structure it walks that too. The whole thing lands in the ComfyUI console with your label attached so you can tell multiple debug nodes apart.

The inputs

• item (required) - the CLIP to inspect.
• label (default "debugging passthrough") - a tag printed with the log; rename it so you know which node produced which block.

The output

CLIP - the identical object, passed through untouched. Works as a terminus (it's an output node) but shines mid-wire.

How to install it

Installs with the pack: ComfyUI Manager → search ComfyUI-Keyframed, or

cd ComfyUI/custom_nodes
git clone https://github.com/dmarx/ComfyUI-Keyframed

then restart ComfyUI. No models to fetch; the only dependency is the keyframed library (plus toolz), auto-installed on first import.

Troubleshooting

The usual debug-family footguns apply. The output goes to the console, not the UI - if the node's output panel is blank, that's expected. And there's a hierarchy to what you'll see: type always, shapes/dtypes when the wrapper exposes them, and little else. A CLIP is a wrapper around a text encoder, not a data structure, so don't expect a rich dump - the honest value here is usually just confirming which model family you're actually holding. If your real problem is a downstream encode error, this node's job is to confirm the CLIP itself isn't the broken link, not to fix the error.