Nodes/IAMCCS-nodes/INT Value Monitor
ComfyUI Node

INT Value Monitor

See the number that's driving your batch loop

By IAMCCS·Created 11 months ago·Updated 8 days ago· 113
INT Value Monitor
    • value
    • report
    value0
    labelQwen batch count

    ComfyUI's UI is genuinely bad at one thing: showing you the value of an INT as it flows through a workflow. Widgets show you what you typed, not what's actually being passed after a node recalculates it. IAMCCS IntValueMonitor is the fix - a passthrough that prints a labeled value to the UI text area every run so you can see what the graph is really handing around.

    The default label tells you exactly where the author needed this: "Qwen batch count." In the Qwen Multi-Gen / dataset-creation workflows this pack ships, a prompt count gets computed somewhere upstream and drives a loop, and when the loop generates a surprising number of images you need to see that count at a glance. This node puts it on screen.

    How it works

    Inputs: value (INT) and label (STRING, the tag printed in the report). It's an output node, so every execution prints {label}: {value} to the UI text panel.

    Outputs: value passes straight through unchanged, and report carries the same "label: value" string if you want to wire it somewhere (a text display, a log, a condition). Nothing is modified - it's purely observational.

    The workflow habit worth building

    Wire one of these after anything that computes a count: batch sizes, loop indices, frame counts, slice results. When something downstream behaves unexpectedly, the first question - "what value is this branch actually receiving?" - is answered by a glance at the last run's text output instead of a debugging session. It's the INT equivalent of sticking a Show Text node on a STRING, and it costs one node to leave in place permanently.

    Install

    Ships in IAMCCS-nodes:

    cd ComfyUI/custom_nodes
    git clone https://github.com/IAMCCS/IAMCCS-nodes.git
    

    or ComfyUI Manager → search IAMCCS, restart. Zero extra dependencies.

    The caveat

    It prints on every run, so in a tight loop it'll fill your UI text area fast - set a descriptive label or remove it after the mystery is solved. And don't expect it to do anything clever; that's the point. It's a single-purpose lens, and for a node that small, that's exactly right.

    CategoryIAMCCS/Utils

    Inputs (2)

    NameTypeDefaultDescription
    valueINT0-2147483648–2147483647
    labelSTRINGQwen batch count

    Outputs (2)

    NameTypeDescription
    valueINT
    reportSTRING