Display Int (rgthree)

Display Int is a tiny debugging node that shows you an integer after the graph runs. That's the whole thing. When you've got a number bouncing through your workflow - a computed width, a seed, a step count, a batch index - and you want to see what value actually landed, you tap this onto the wire and read it. Think of it as a typed, no-frills readout for exactly one kind of value.

Why you'd reach for it

ComfyUI keeps intermediate numbers invisible. A resolution gets computed by a math node and vanishes straight into a resize; a step count comes out of a config node and disappears into a sampler. If the result looks wrong and you suspect the number, you've got no easy way to check it without inspecting the console. Display Int surfaces it right on the canvas.

It's the integer-specific cousin of Display Any, which shows any type. So why use the narrow one? Two reasons. It advertises intent - when you drop a Display Int, you and anyone reading your graph know it's an integer readout. And it'll only accept an INT, so if you try to wire a float or a string into it, the type mismatch tells you the value isn't the integer you assumed. That's a small but genuine sanity check.

How it works

Two mechanics matter. First, it displays after execution - ComfyUI runs the whole graph, then reports - so you queue the prompt and the number appears (or updates) once the run finishes. Nothing shows on a workflow you haven't run yet.

Second, Display Int is an output node. In ComfyUI, output nodes are the endpoints the engine works backward from, like Save Image and Preview Image. The practical consequence: attaching a Display Int to a branch is enough to make that branch execute, because the engine now has a reason to compute it. Handy when you want to force a number to resolve so you can inspect it - but worth remembering when you're muting things to save compute, since a stray Display Int can keep a branch alive.

The input and output

There's exactly one input:

• input - an INT. Drag from any integer output into it.

And there are no outputs - it's a terminal readout, not a pass-through. You look at the number; you don't route it onward. If you need the value and want to see it, branch a Display Int off the wire (ComfyUI lets one output feed several inputs) rather than trying to pass through it.

Installing it

Display Int ships with rgthree-comfy. Install the pack via ComfyUI Manager - search rgthree's ComfyUI Nodes - or clone it by hand:

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

Restart ComfyUI afterward. No models to download, no heavy dependencies - the pack is entirely graph and UI code.

Common issues

The usual non-bug: the node is blank until you queue the prompt. It's a post-execution display, so run the workflow before expecting a number.

The second: type mismatch. Display Int only takes an INT. If the value you're trying to inspect is actually a float (a cfg value, a strength), this node won't accept it - reach for Display Any instead, which takes anything. Honestly, if you're not sure what type you're dealing with, just start with Display Any and switch to Display Int once you've confirmed it's an integer.

And the pack-wide one: if the node renders oddly, check whether ComfyUI's Nodes 2.0 frontend is enabled. The Vue rewrite broke rendering for several rgthree nodes, and the community's standing fix is to keep Nodes 2.0 off. A plain number readout usually survives it, but it's the first thing to rule out.