🐸 Image Picker

Frog Image Picker is the node that stops you from saving nine out of ten images you'll delete anyway. It sits between the sampler and the save node. The sampler runs a batch, thumbnails appear on the node itself, you click the ones worth keeping, hit Proceed, and only the selected frames continue downstream to the save node. Everything else dies in the picker. It's the ComfyUI version of "reroll until good, then save the winners" - without a file manager in the loop.

The mechanics are worth understanding, because they're not a hack. The picker is a blocking node: it pauses execution, shows your results as a thumbnail grid directly on the canvas, and waits. When you click Proceed it hands the selected frames onward; click Cancel and it discards the batch and starts fresh. The important promise, spelled out in the README, is that the sampler does not re-run on Proceed - the picker and everything downstream execute again, but generation is paid for once. That's the difference between this and the naive "regenerate and cross your fingers" approach. The node's own docstring says the queue pauses naturally because execution hasn't finished; no second prompt is ever submitted.

The inputs

There's exactly one real input, and it's optional:

• images - the batched IMAGE tensor from your sampler. Connect it and the thumbnails populate.
• hold_queue - a boolean, default true, which the tooltip calls a "legacy setting - the blocking approach always pauses the queue naturally. Kept for workflow compatibility." In other words: ignore it; it's there so old workflows don't break.

What comes out

selected - the chosen frames as a batched IMAGE tensor, ready for a save node. is_output_node is true, which is ComfyUI's way of saying this node is an endpoint in its own right - it's meant to be the last interactive thing before saving.

Installing it

Pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/RabbitThatIsPink/FrogNodePack

or via ComfyUI Manager → "Frog Node Pack". Restart, hard-refresh, no extra dependencies. The interactive UI lives in the pack's web/ directory.

Where people trip

The one thing that confuses everyone the first time: the queue looks like it's stuck. It isn't - the picker is holding execution open waiting for you to interact, and the whole ComfyUI queue pauses at that node until you click. That's the feature, not a hang. Second: if you wire nothing into images the node still blocks and waits, so don't leave it in a workflow that's supposed to run unattended - it's a human-in-the-loop node by design. And because it's a blocking interactive node, automated or batch-cli runs will stall at it; keep it out of any pipeline that runs without you watching.