🚀 Show Any

Every ComfyUI user has had the debugging moment: a node refuses to connect, or a workflow silently produces garbage, and the only useful question is what is actually in this wire? This node answers it for literally any input. Its single input accepts any data type - image tensors, latent dicts, strings, ints, floats, whatever - and prints a formatted readout of what it received, right in the node's UI. No more guessing whether that value is a list, a tensor, or a dictionary with the wrong key.

It's a "show" node in the same family as ComfyUI's own display nodes, but without the type strictness. The placeholder text in the UI tells the story: "Connect INT, FLOAT, STRING or any data type."

How it works

The trick is the wildcard input type - a special AnyType class that equals anything, the standard ComfyUI pattern for accepting arbitrary data without failing type validation. Validation is skipped on the backend, so it never refuses a connection. When it executes, it inspects what it got and formats a description:

• Torch tensors (IMAGE, MASK, etc.) - type, shape, dtype, plus a sample value.
• LATENT dicts - type and the shape of the samples tensor.
• Primitives (int, float, str, bool) - type and value.
• Anything else - dumped as JSON, or a fallback type + string representation.

It has no outputs and is flagged as an output node, so it always executes when wired in.

Install

ComfyUI Manager (search "YarvixPA") or

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

restart. Under ComfyUI-YarvixPA/Utils/Show.

When to reach for it

Debugging, full stop. "Why is this conditioning wrong?" - drop it on the conditioning and check it's the shape you expect. "Is this really a mask?" - it'll tell you the dtype and range. "What's this custom pack outputting?" - this is the fastest way to see. Two honest notes: it's an output node, so it forces the whole upstream graph to run even if you're just exploring - fine in an idle editor, mildly annoying if it sits in a production graph doing nothing. And a single-element list gets unwrapped for display, which is usually what you want and occasionally surprising if you expected a list. Keep it as your debugging friend, not a permanent fixture.