🖥️ Log to Console

"🖥️ Log to Console" does one job: print whatever string you feed it to the terminal where ComfyUI is running, with some friendly cyan and yellow ANSI coloring, then hand the string right back. It's the terminal-flavored cousin of Log to Workspace - same pass-through idea, but the output goes to your terminal scrollback instead of an on-canvas box. If you run ComfyUI in a terminal you actually watch, this is the fastest way to see which prompt a batch actually used.

How it works

Give it a string, it prints a header line with your prefix_label, then the text in quotes. The detail that makes it useful for batches: if the input arrives as a list of strings rather than a single string, it prints a batch count first, then each item numbered. That's the whole batch-debugging loop in one node - you see all ten prompts your randomizer produced, labeled and in order, before the sampler touches any of them.

Now the catch, and it's a real one: this node is not marked as an output node. ComfyUI figures out what to execute by walking backward from its output nodes, so a debug node with nothing wired out of it can get skipped entirely - it just won't run, no log, no error. The fix is to wire its text output onward. Drop it inline in the prompt chain - randomizer → this node → CLIP encoder - and it fires on every run while remaining invisible to the result. If you leave it dangling with nothing connected, don't be surprised when your terminal stays silent.

The inputs that matter

• text - the string (or batch of strings) to log. forceInput means it's meant to be wired, not typed.
• prefix_label - the label printed in the header, default LOG TEXT. Make it descriptive - SUBJECT PICK, LIGHTING - so multi-node logs are readable.

Output: text (STRING), unchanged. Wire it onward so the node actually runs.

Installing it

Same as the whole pack - no requirements.txt, no models, pure Python stdlib. The README is a "TODO." stub, but there's nothing to configure beyond the install itself.

ComfyUI Manager → Custom Nodes Manager → search "TextRandomizer" → Install → Restart

or cd ComfyUI/custom_nodes && git clone https://github.com/fls-eugene/ComfyUI_TextRandomizer, then restart.

When to reach for it

When you want the log in your terminal - because you're grepping it, because you're watching ComfyUI output while it runs anyway, or because the on-canvas textarea of Log to Workspace isn't enough room. It's also the lower-overhead sibling: no JS extension involved, just a print. Pick based on where you look when a batch finishes: terminal, this node; canvas, Log to Workspace. Either way, wire the output through.