ℹ️ Prompt Loop Info

Here's the short version, because you should hear it before you build anything on this node: PromptLoopInfo looks like it reports which prompt in the batch you're on, and it doesn't. The code returns current_index = 0 and total_count = 1 - hardcoded, every time, no matter how many prompts you're looping through. It's a placeholder implementation ("kann später erweitert werden" - "can be extended later" - says the source comment). The README doesn't even document this node. It's the pack's stub.

That's not a reason to skip the rest of the pack - the file and text loop nodes are real and useful. It's just a reason to know what this one actually is before you wire its outputs into something that matters.

What it does

The node takes one required input, prompt (a STRING, marked forced-input, so you must wire it rather than type into it). It passes that prompt straight through and also exposes three outputs:

• prompt - the same string you fed in, unchanged
• current_index - always 0
• total_count - always 1

So in practice it's a named pass-through: if you need the prompt string available at a second point in the graph and want the wire labeled, it works fine for that. The source is five lines and does exactly one thing, which is pass the value along.

The trap

The natural reading of those outputs - "current index within the batch" and "how many prompts total" - is precisely what you'd want if you were building per-prompt filenames or a progress display. And it's exactly what this node won't give you. Wire current_index into a filename expecting image_003 and every single file comes out image_0. You'll think the save is broken. It isn't - the info node just isn't implemented yet.

If you actually need batch-aware numbering, the honest answer is that this pack doesn't provide it, and there's no hidden switch to turn it on. Either wait for the author to finish the feature, or get index info from a different approach (some savers can template per-batch values into filenames on their own - check what your save node supports before inventing a workaround).

Should you use it at all?

Only as a labeled pass-through or a debugging placeholder - and even then it's marginal, because a plain Reroute or a wire does the same job without the misleading extra sockets. If the author ever wires this up for real, it'll be a genuinely nice little node for the pack's overnight-batch use case: showing "prompt 7 of 40" in the console or baking an index into filenames. Until that lands, treat it as documentation of the pack's intended design, not as working functionality.

Installation

Nothing special here - it ships with the pack and installs with it:

cd ComfyUI/custom_nodes
git clone https://github.com/max-dingsda/ComfyUI-PromptLoop

Then restart ComfyUI. No dependencies, no models. Under the promptloop category, next to its two working siblings and the save node.

One sentence of context if you're new to this pack's style: it's a small, honest utility pack, written plainly and shipped with a Created by max with Claude credit in the README. The file loop node is the star; this Info node is the rough edge. Know what you're grabbing and it won't waste an evening of your life.