📋 PRO List Cache

Somewhere in your workflow you've got a PRO_SetNode stashing a value, and a PRO_GetNode pulling it back out across the graph. This node answers the question you'll eventually ask: what's actually in that shared cache right now? It lists every stored variable and the type ComfyUI detected for it, as a plain string. That's it - it's a debug/inspection utility, and it's the node you add to the graph when a Get node is returning nothing and you can't tell why.

The pack ships a whole context-memory subsystem (this is the "PRO" in the name): thread-safe shared storage that auto-detects ComfyUI types - MODEL, CLIP, VAE, IMAGE, LATENT, CONDITIONING, STRING, and so on - and is explicitly compatible with existing workflows that use rgthree-comfy's SetNode/GetNode pattern. PRO_ListCacheNode sits on top of that storage and prints the ledger: variable name plus detected type, or [PRO_Cache] Empty when there's nothing stored. Its companion PRO_ClearCacheNode wipes it.

The inputs and output

Just one optional input, trigger - an any-type wire you can connect to force ordering in the graph (so the list reflects the cache after a Set node has run, not before). Output is a single info STRING with the full listing, formatted for reading in a text display node.

When it saves you

The classic failure: a PRO_GetNode comes back null or stale and you can't tell if the variable was never set, was set under a different name, or was cleared. Drop this node in after the Set, run once, and you immediately see the name mismatch or the empty cache. It's also the fastest way to sanity-check whether your type detection did what you expected - a variable that should be an IMAGE showing up as something else tells you the auto-detect guessed wrong.

Installing it

ComfyUI Manager → search "COMFYUI_PROMPTMODELS" → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/cdanielp/COMFYUI_PROMPTMODELS

No API key, no model files, no dependencies beyond the pack's own requests/Pillow. Requires ComfyUI >= 0.26.0.

The honest caveats

This is a utility node, so keep expectations sized right: it lists, it doesn't explain. It tells you a value exists and its detected type - not what the value is or which node wrote it. And because the cache is process-global and persists across executions, the contents you see may include stale entries from earlier runs; if a list looks wrong, clear the cache with PRO_ClearCacheNode and rerun before debugging anything else.