SAX Debug Text

Some nodes have a job and a half. SAX Debug Text has one job: take any value, turn it into text, and show it to you on the node. That's it. There's an input value that accepts anything - a string, a number, a dict, a tensor - and the node auto-converts it to a string and displays it in the node UI. No outputs, terminal node, done.

Don't underestimate it because it's boring. This is the node you reach for when you need to see an intermediate value that ComfyUI otherwise swallows: what did the wildcard expand to? What string came out of the prompt concat? What's inside that metadata blob before it gets written to the output? ComfyUI doesn't show you most intermediate values unless a node chooses to, so a cheap "print anything" display fills a real gap.

How it works

Connect value, run the workflow, read the node. Because it's an output node, ComfyUI always executes it and it re-runs when the input changes, so it behaves like a live probe rather than a snapshot. The string conversion is automatic - you don't pick a format, you don't type a converter. That's the whole design: zero friction, so you actually use it.

It's the text-and-values sibling of SAX Debug Inspector (which is pipe-shaped) and SAX Assert (which checks rather than displays). Where the Inspector is for pipe internals, Debug Text is for anything at all.

Where it's genuinely handy

• After a SAX Prompt node, to verify POPULATED_TEXT actually expanded your wildcards and LoRA tags the way you expected. Prompt bugs are silent, and this makes them visible.
• Before a text-based metadata embed, to confirm what's actually in the string that's about to get baked into your PNG.
• Anywhere a node outputs a string you've never seen and want to sanity-check without reading the source.

The honest caveats

It's a debug node, so it has no business in a shared or production workflow - bypass or delete it before you pass the graph around. And "any value" means it'll happily dump a giant tensor or dict as a wall of text in the node body, which is fine for inspection and annoying if you leave it wired to something big. Treat it as a temporary probe, not a permanent fixture, and it'll answer more "where did that string go" questions than any node twice its size.