Debug Node

Most of this pack's data moves around as LIST - image paths out of Image Loader, batches out of Batch Processor, captions out of Caption Generator. All of that is invisible until something goes wrong downstream, and by then you're debugging blind: was the folder scan empty, did batching produce something weird, did captioning actually run? Debug Node exists to let you check at any point in that chain without pulling the graph apart to do it.

How it works

Unlike a typical debug sink that dead-ends a wire, this one passes through. Plug any LIST in as input_list, and you get two things back: the exact same list, unchanged, as debug_list - so you can keep it wired into whatever was going to consume it next - and debug_text, a human-readable dump of what's actually in there. You're not choosing between debugging and continuing the pipeline; you insert this node inline and get both.

The inputs and outputs that matter

• input_list (LIST, required) - the only input. Drop it onto any list wire in the graph.

Two outputs: debug_list (LIST, pass-through - wire this onward exactly where input_list was headed) and debug_text (STRING, the readable version - read this in the console/log or a text-display node).

Where to actually put it

Between Image Loader and Batch Processor, to confirm your folder scan found what you expected before anything downstream burns time or GPU on a list that's empty or wrong. Between Caption Generator and Caption Export, to eyeball the actual caption text before it gets written to files on disk - especially useful before you flip overwrite_existing on over in Caption Export, since that's the point of no easy return for whatever's already there.

Installing it

Through ComfyUI Manager: search ComfyUI-Transformers-Pipeline, install, restart. By hand:

cd ComfyUI/custom_nodes
git clone https://github.com/mediocreatmybest/ComfyUI-Transformers-Pipeline

then restart. No downloads - it's pure introspection, no model involved.

Common issues & troubleshooting

debug_text looks empty or nearly empty. That's real information, not a bug in this node - it means the list feeding into it is actually empty or thin. Trace one step further upstream: if you dropped this after Image Loader, that usually points at a wrong directory_path; after Caption Generator, it usually points at a model or task mismatch on Model Loader.

Not sure the pass-through actually preserved the data. It does - debug_list is the same list object handed straight back, so wiring it onward instead of the original input changes nothing about what downstream nodes receive.

Wired it in but the graph still fails the same way. This node only shows you what's there; it doesn't fix anything. Once you can see the actual list contents, the fix is whatever the contents tell you - a wrong path, an empty batch, a caption that came back blank - not something this node does for you.