Meta

Meta is the pack's introspection node: you connect it to any output and it tells you what's actually on that wire - sizes, keys, and types - as real outputs you can feed into other logic. If Beautify is the "show me" debug node, Meta is the "measure it" debug node. Wire a Highway or Junction pipe into it and it hands you back the batch size, the list of lane keys, the types, and the declared Comfy type of whatever fed it.

That last part is the sneaky useful one. ComfyUI's custom pipe types (HIGHWAY_PIPE, JUNCTION_PIPE, SCRIPT_DATA...) are opaque - a normal node can't tell you what a pipe contains. Meta can, because it reads both the data itself and the upstream node's declared output type straight out of the workflow graph. If you're debugging why a pipe-fed node is complaining, Meta is the first place to look.

The outputs

Six outputs, all straightforward:

• batch_size - the number of items (for a pipe: number of lanes/entries).
• data_size - the size of the payload - for a Highway, per-lane lengths; for a Junction, per-type counts; for a string, its length (and grapheme count).
• key_list - the keys/lane names inside the data.
• type_list - the types attached to those keys.
• comfy_type - the Comfy output type declared by the node upstream of you.
• py_type - the Python type of the data (e.g. RevisionDict, str, int, CloudData).

It handles a surprising range of inputs: the pack's pipe RevisionDicts, ScriptData, CloudData, strings (split into grapheme clusters and code points), ints, and floats (with their binary representations). Wire in whatever you're unsure about and read what comes out.

The input

• data (optional) - the wildcard input. Connect the wire you want to inspect.

How to install it

The usual:

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

restart, or ComfyUI Manager → search "ComfyUI-0246". No models.

Common issues & troubleshooting

Outputs come back empty for an unknown type. Meta's source match statement covers the pack's own structures plus str/int/float - anything else falls through with minimal output. That's not a bug so much as a boundary; Beautify in full mode will show you more for exotic data.

comfy_type is None. Meta reads the upstream output type from the workflow's link data; if the upstream is a wildcard (*) or the link is odd, there's no type string to report. Check what's actually upstream of your connection.

The values don't update. Meta is a pure reader - if the data genuinely changed and the outputs didn't, ComfyUI cached the node. Touch the connected upstream so IS_CHANGED fires.

Like everything in this pack: single-author, dormant since early 2025. But as a pure-logic inspection node, Meta is about as stable as this pack gets - nothing about reading data structure depends on ComfyUI's latest internals.