🪛 Show any value to console/display

The universal debug probe. Wire literally anything into it - a string, a number, a whole JSON blob, the output of some custom node you don't fully trust - and it prints the value on the node itself and, if you want, to your terminal console too.

Why you'd reach for it

Every serious ComfyUI debugging session eventually hits a point where you need to know what's actually flowing through a wire, especially once you're dealing with */ANY-typed connections you can't just eyeball from the graph. A switch's output, a pipe's contents, a value from a node whose docs are thin - this is the node you tap in to find out. It's a small utility, but it's the kind you end up reaching for constantly once it's installed.

How it works

At runtime the node stringifies whatever's connected and renders it on its own face. Turn on console and the same value gets written to stdout too, which matters for anything too big for the little on-node display - a full tensor repr, a long JSON dump. The prefix field tags console output so multiple Show Any nodes scattered across a busy graph don't blur together in the terminal.

Inputs and outputs

All optional. any_value - the wildcard input, connect whatever you want inspected. console (boolean, default off) - write to terminal. display (boolean, default on) - show on the node itself. prefix (string, default empty) - a label prepended to console output. There are no outputs at all; this is a dead end by design, meant purely for inspection, not for passing values onward.

Installing it

Through ComfyUI Manager, search crystools. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/crystian/ComfyUI-Crystools.git
cd ComfyUI-Crystools
pip install -r requirements.txt

Restart ComfyUI. Nothing else needed - no models, no heavy dependencies for this node.

Common issues

If nothing shows up, the first thing to check isn't the node's settings - it's whether any_value is actually connected. An unconnected optional input just shows nothing, silently, with no error to point you at the problem.

For big objects - a full workflow JSON, a large tensor's string representation - the on-node display gets unreadable fast. Flip console on and use prefix to grep it out of the terminal log instead of squinting at a cramped node widget.

And worth knowing going in: this node only shows you a raw stringified value, it doesn't pretty-print structure. If what you're inspecting is JSON-shaped and you want it readable, Show any to JSON is the one that formats it - and it also gives you an output socket, which this node deliberately doesn't.