Print (Badman)

The oldest debugging trick in software, ported into a node: wire any string output into this, and it prints the value to the console when the graph runs. No image preview widget, no fancy display - just the raw value, logged, exactly like dropping a print() statement into a script you're trying to understand.

Why you'd reach for it

A lot of ComfyUI's string-producing nodes don't give you an easy way to actually see what they resolved to mid-graph - a wildcard processor's output, a concatenated caption, a preset path a color-match node just saved to. You can often infer it from the final image, but when something's wrong and you're not sure whether the bug is in the string logic or somewhere downstream in the sampling, the fastest way to find out is to look at the actual string value at that exact point in the graph. Splice this node onto any STRING output you're suspicious of, run once, and check the console. It's a terminal node - is_output_node is true, and it has no outputs of its own - so it doesn't interrupt or reroute anything; you can leave it dangling off a wire without touching the rest of your graph's logic.

Inputs and outputs

One required field: value (multiline string, default empty). No outputs - this node's entire job is the side effect of printing, not passing anything forward.

Installing it

ComfyUI Manager: search ComfyUI-BadmanNodes, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/MariusKM/ComfyUI-BadmanNodes

Nothing else to install - it's a print() call wrapped in a node.

Where people get tripped up

The thing that actually catches people out is where "console" means, and it depends on how you're running ComfyUI. On a local install, that's the terminal window you launched ComfyUI from - easy to miss if you've minimized it or if you're watching the browser tab instead. On a hosted or cloud setup (running a workflow through the API on a service like ComfyICU, for instance), there is no terminal window in front of you at all - "console output" means the run's server-side logs, which you have to go look up separately rather than something that pops up in the UI as you watch the graph execute. If you've wired this node in and nothing seems to be happening, you're very likely looking in the wrong place rather than the node failing to run - check wherever your setup actually routes stdout before assuming the print didn't fire. And because it has no output socket, don't try to chain something after it expecting the string to pass through - it's a dead end by design, meant to be a spur off the side of your graph, not a link in the main chain.