Shima Inspector

Shima Inspector is the debugging node you wish you'd placed earlier. It accepts up to ten inputs of any type, shows you what each one actually is - type, shape, a preview of the value - and passes all ten straight through so you can leave it inline while you poke at a workflow. Think of it as a multimeter taped into your graph: you can see the voltage without breaking the circuit.

The mechanism is simple and clever. All ten sockets are wildcard (*), so an IMAGE, a LATENT, a MODEL, a dict, whatever, all plug in. On execution it walks each input and builds a readable summary - tensors get their shape and dtype ("TENSOR, Shape: [1, 512, 512, 3], float32"), lists and dicts get their lengths and a key preview, strings get truncated to 200 chars - and renders that as a little HTML table in the node's UI area. Because it's an output node (is_output_node: true), it always runs, which is exactly what you want from a debug tool: it won't be skipped by ComfyUI's caching.

How to use it

• Plug the wire you're suspicious about into any of any_01 through any_10. Nothing is required - empty sockets just show "No inputs connected."
• Queue the workflow. The node fires, the table updates, and you read off the shape/dtype/keys.
• The ten any_* outputs mirror the inputs, so you can chain it into the middle of a graph and keep the signal flowing while you watch.

The killer use case: a node downstream keeps failing or silently doing nothing, and you're not sure if the upstream actually produced a tensor with the shape you think it did. Inspector settles it in one run instead of three rounds of guess-and-check. It's also great for confirming that a "broadcast" from the island system actually arrived - plug the suspected output in and see whether it's there or None.

Install

Standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/KDB-USJP/shima_wf

then restart, or ComfyUI Manager → search "Shima". No models, no extra pip packages - this one is pure Python and torch.

Honest caveats

It's a display node, so a few things follow. The HTML panel is rendered by the pack's JS on the canvas, so under the Nodes 2.0 frontend it can render as a bare box (classic legacy-canvas breakage - flip back to the classic renderer if that bugs you). It doesn't persist a log between runs beyond the last execution, and there's no "inspect only this wire" mode - it shows everything connected, so unplug what you don't care about. And if you only need one socket, you're hauling a ten-port node for it; that's fine. The nearest core-adjacent equivalent is the built-in "Debug" notes and the primitive viewer, but Inspector gives you type and shape in one glance, which is the part that actually saves you time. For anyone doing serious troubleshooting, this is one of the more immediately useful nodes in the pack.