Display Any (rgthree)

This is the print() statement of ComfyUI. When you can't tell what value is actually flowing down a wire - is that string what you think it is, is that number what the math node computed, what did the API node really return - you tap Display Any onto it and read the answer. It's the single most useful debugging node in the pack and it's completely unglamorous, which is probably why it gets a lot of impressions and few clicks: people don't realize how much time it saves until they're stuck.

Why you'd reach for it

ComfyUI hides most intermediate values. A prompt travels invisibly through encode nodes, a computed dimension disappears into a resize, an integer bounces between three math nodes and you have no idea what it landed on. Normally you'd have to guess or dig through the console. Display Any just shows you: connect its input to any output in your graph, run the workflow, and the value renders as text right on the node.

The key detail is in the name - Any. It'll take a string, an int, a float, a boolean, a list, a dict, whatever. If the backend can turn it into readable text, this node will show it. That makes it the catch-all counterpart to the more specific Display Int, which only accepts integers.

How it works

Two things about the mechanism are worth internalizing, because they explain the node's quirks.

First, it displays the value after execution, not live. ComfyUI is a batch graph - it runs, then reports. So you queue the prompt, the graph runs, and then the text appears (or updates). You won't see anything change mid-run.

Second, and this is the part that trips people up: Display Any is an output node. In ComfyUI, output nodes are the endpoints the graph works backward from - Save Image, Preview Image, and yes, this. That has a real consequence: because it's a terminal output, attaching Display Any to a branch is enough to make that branch execute, even if nothing else downstream needs it. Handy when you want to force a value to compute so you can inspect it; something to remember when you're muting things to save compute, since a stray Display Any can keep a branch alive.

The input and output

There's exactly one input:

• source - typed as *, meaning it accepts anything. Drag from any output slot into it and ComfyUI won't complain about type mismatches.

And there are no outputs - this is a dead end by design. You don't pass the displayed value onward; you look at it. If you need the value and want to see it, put the Display Any on a branch off the wire (ComfyUI lets one output feed multiple inputs) rather than trying to route through it.

Installing it

Display Any comes with rgthree-comfy. Install the pack via ComfyUI Manager - search rgthree's ComfyUI Nodes - or clone it manually:

cd ComfyUI/custom_nodes
git clone https://github.com/rgthree/rgthree-comfy.git

Then restart ComfyUI. No models, no dependencies to install; the whole pack is graph and UI code.

Common issues

The most common "bug" isn't one: nothing shows up until you actually queue the prompt. It's post-execution display, so a fresh workflow you haven't run yet will show an empty node. Run it.

The second is expecting to chain through it - there's no output, so you can't. Branch off the source wire instead.

And the third, as with everything in this pack: if the node renders wrong or the text area misbehaves, check whether ComfyUI's Nodes 2.0 frontend is enabled. The Vue rewrite broke rendering for several rgthree nodes and the community fix has been to keep Nodes 2.0 turned off. A plain text display usually survives it, but it's the first thing to rule out when an rgthree node looks broken.