Show Any Text In CMD console-SG

The weird thing about ComfyUI is how much text flows around invisibly. A prompt scheduler spits out a string, a text-encoder passes a conditioning, an API node returns some JSON - and you never actually see any of it. It just hops from wire to wire until it does something. That's the gap Show Any Text In CMD console-SG exists to close: it's a debug node that prints whatever string you feed it to the terminal where ComfyUI is running, in color, and hands the same text back out so you can tap a wire without breaking your flow.

The name is a lie in one nice way: it doesn't call any API and needs no key, no GPU, and no model download. It's one ~100-line Python file with zero dependencies - the kind of custom node you could read top to bottom in a couple of minutes if you're the paranoid type, which is more than you can say for a lot of what the ecosystem ships (the ComfyUI custom-node scene has had its share of malware scares, and this is the reassuring opposite end of it).

What you actually set

There are four inputs, and honestly only one matters.

• text - the only real input. It's forceInput, so you can't type a literal; you must wire a STRING output into it. Connect anything: a prompt, a filename, a LoRA name, whatever a node is passing down a wire you don't trust.
• show_any_text_in_console - a simple on/off toggle (default on). Flip it off and the node stops printing but still passes the text through, so you can leave it in your graph and silence it later.
• color_preset - dropdown with eight standard console colors: white, red, green, yellow, blue, magenta, cyan, black. It starts on white.
• hex_color - leave this empty unless you want a custom color. Enter a hex like #FF0055 and it overrides the dropdown. It has to be exactly six hex digits; anything else is silently ignored and it falls back to your preset - no error, which is worth knowing when your color "isn't working."

The one output is a STRING passthrough, so you can chain it anywhere in a text pipe and read the value without changing what flows onward.

How it works

Under the hood it's embarrassingly simple: the node prints a little =====> banner to stdout, then your text wrapped in ANSI escape codes - \033[91m for red, and a TrueColor \033[38;2;R;G;Bm sequence when you give it a hex code - then a reset code. Because it's marked as an output node, the text also shows up in the widget area on the node itself, so you get a readable preview in the graph and a timestamped copy in the console.

Installing it

Via ComfyUI Manager, search Show_Any_Text_in_CMD_Console-SG (or just search the author, ShammiG) and hit install. It's published to the Comfy Registry, so Manager finds it without fuss. No Manager? The manual route:

cd ComfyUI/custom_nodes
git clone https://github.com/ShammiG/ComfyUI-Show_Any_Text_in_CMD_Console-SG.git

Then restart ComfyUI. There's no requirements.txt and nothing to pip install - that's the whole point of the node.

Where people get burned

First: "CMD" is a Windows-ism, but the node works anywhere - it just prints to stdout, and if you run ComfyUI inside Docker or behind a service manager, that output might land somewhere you're not looking. Find where your ComfyUI logs go first. Second, if you see raw escape gibberish like [91m instead of color, your terminal isn't rendering ANSI codes - that's a terminal setting, not the node's fault. Third, the "black" preset is invisible on a dark terminal by definition. And remember the silent hex fallback: #FFF won't work, only full six-digit codes.

It's a tiny tool, and it won't change your life. But the first time you're debugging why a workflow is producing garbage and you actually see the prompt that was really going into the sampler, you'll be glad it exists.