🪠️ WWAA Display Any

WWAA Display Any is the debug node you didn't know you needed: a single input of any type, and it prints what's actually flowing through your workflow to the ComfyUI UI. Tensors are opaque in ComfyUI - you can't just hover and see their shape or contents - and this node is the cheap way to peek. It's part of WWAA-CustomNodes from WeirdWonderfulAI.Art, and it fills the exact gap that every graph-based tool has: visibility into intermediate values.

The input type is * (any), and the only setting is mode:

• raw value - prints the value as its Python string representation.
• tensor shape - for anything with a .shape attribute, walks the structure (including dicts and lists) and prints the shape(s) instead of the raw data. This is the mode you want when an image or latent is flowing through and you just need to confirm its dimensions and batch size.

It's an output node, so the result appears in the UI and is also returned as a STRING you could wire onward if you really wanted.

How it works

Under the hood it's a str(input), with a small recursive walker for the tensor-shape mode that flattens nested dicts/lists and collects every .shape it finds. No processing, no side effects beyond the UI print. It accepts anything ComfyUI can route, which is the point - you can drop it on a wire anywhere, run, and read the output. For tensors, raw value gives you the tensor's string repr (type, device, shape, dtype) while tensor shape gives you just the dimensions, which is cleaner for quick checks.

Inputs

• input - any type (the * wildcard).
• mode - raw value or tensor shape.

Output: a STRING (shown in the UI as the node's text output).

Installing it

It's in the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/hgabha/WWAA-CustomNodes

Restart ComfyUI. Or ComfyUI Manager → search "WWAA Custom Nodes" → install → restart. It's under 🪠️ WWAA/utilities. No models, no declared dependencies.

Gotchas

Two honest caveats. First, it's a debug aid, not a display widget - there's no fancy formatting or image preview; don't expect it to render a thumbnail. Second, being a "wildcard" node it can occasionally be the source of ambiguous-wire type mismatches in older ComfyUI versions when ComfyUI tries to validate what connects to it; if a workflow complains about the connection, it's usually the validation logic, not this node, and the VALIDATE_INPUTS override in the code tries to keep that from biting. If you're hunting a shape mismatch, wire it after the node you suspect and read the numbers - then delete it before saving the final workflow.