Text to Console

WAS's README doesn't give this one its own line, but it's the text-flavored member of a small, obvious family the pack does document explicitly - "Dictionary to Console" is right there described as "Print a dictionary input to the console," and Text to Console does the identical job for plain strings. You feed it text, it prints that text to the console when the workflow runs. That's the entire feature. No visible output in the ComfyUI browser UI, no fancy formatting - just a value showing up in your server log at the exact point in the graph where you dropped the node.

That sounds almost too simple to be useful until you've spent twenty minutes wondering why a prompt isn't behaving the way you expect. WAS Node Suite has a genuinely deep text-processing layer - wildcard parsing, NSP (Noodle Soup Prompts), token substitution, string concatenation chains, dictionary-backed replacements - and any of those can silently produce something different from what you intended. Text to Console is how you actually look. Drop it inline right before a CLIPTextEncode, run the workflow once, and read exactly what string made it that far. It doesn't need to sit at the end of a chain either - since it's meant to slot into the middle of a graph, you can plant several of these at different points to bisect where a string went wrong.

One detail that matters more on a hosted platform than on a local install: this prints to the server console, not anywhere the browser shows you. Running locally, that's the terminal window you launched ComfyUI from. Running on something like ComfyICU, that means your run logs - not the workflow canvas, not a node preview thumbnail. If you add this node and then go looking for its output on-screen and find nothing, you're not doing it wrong, you're just looking in the wrong place.

The input is a text string; there's no meaningful output socket to speak of beyond, at most, a pass-through of the same string - the entire point is the side effect of printing, not anything downstream needs to consume.

Installing it: ComfyUI Manager, search "WAS Node Suite," install, restart - simplest route. Manual install: cd ComfyUI/custom_nodes && git clone https://github.com/WASasquatch/was-node-suite-comfyui, then pip install -r requirements.txt (portable: python_embeded\python.exe -s -m pip install -r requirements.txt; manual/venv: activate the venv first), then restart ComfyUI. Nothing model-related or dependency-heavy about this specific node - it's a print statement wearing a node's clothing.

Where it bites: almost nowhere on its own - there's no model, no external library, nothing to break beyond text formatting. The actual risk lives one level up: WAS Node Suite hasn't been actively maintained since December 2023 (its README title literally says "Retired"), and the community's recurring pain point is the entire suite failing to import after a ComfyUI or Python environment update. If Text to Console disappears from your node search, check your startup log for an import error on the whole pack before assuming this specific node broke - that's almost always what's actually going on.