KfDebug_Model

Let's be straight about KfDebug_Model: there's not much to inspect on a model. A MODEL in ComfyUI is a big opaque wrapper around a bunch of weights - no tensor shape, no dtype report, no values worth dumping. So what this node actually gives you is proof of life. It logs the type of whatever came down the wire, plus the label you gave it, and passes the model through unchanged. If you were wondering whether a model actually made it through a chain of switches, loaders, or LoRA appliers, this answers it.

It does not tell you which checkpoint the model is, what LoRAs are baked into it, or anything about its weights. Don't ask it to. The inspector checks for dtype, shape, size, keys, list-ness - and a ComfyUI model object has none of those, so you get the type and nothing more. That's the honest ceiling of this node, and it's still useful in exactly one scenario: "did this wire actually carry a model?"

Why you'd reach for it

Conditional model routing. If you're using a switch or bypass to choose between two models mid-workflow, a KfDebug_Model right after the switch tells you which one actually arrived when the graph ran. Same deal after a LoRA applier - the applier can fail silently and leave you with a model that's subtly wrong, and the debug node at least confirms a valid model object is flowing.

It's the thinnest node in the KfDebug_* family, and it's fine that it is. Debug nodes are allowed to be boring.

The inputs that matter

• item - the MODEL to inspect, force-input off a wire.
• label - multiline string, default "debugging passthrough". This is doing most of the work here: label it "after lora" or "refiner model" and the console line tells you which wire you're looking at.

Output: a single MODEL, the identical object, passed through. You can keep it inline without changing behavior.

How it works

Same shared inspector as every KfDebug_* node - this one is KfDebug_Passthrough with RETURN_TYPES = ("MODEL",). It logs the type, finds nothing inspectable on a model object, and logs the item. You'll get something like type: <class 'comfy.sd.ModelPatcher'> and then the object repr. That's the whole report: "yes, a model object is on this wire."

Installing it

Part of ComfyUI-Keyframed (dmarx's pack wrapping his keyframed library). ComfyUI Manager: search "Keyframed". Or manually:

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

Restart ComfyUI. The pack auto-installs keyframed and toolz on first load; no model files to download - the pack itself is just code.

Troubleshooting

If you expected this node to tell you more about a model, that's the main "issue": it can't, by design. The type line in your console is the deliverable. If you need deeper info on a model, you're looking for a dedicated inspection node from a heavier pack, not a keyframing utility's debug passthrough. And the usual family rule applies - output goes to the terminal, not the canvas.