Image Selector

You generated 24 frames and only 6 are keepers. The alternatives are grim: remember the indices and type them into a slice node, or delete frames in an image editor and re-load. Image Selector makes it visual - it shows you every image in the batch and lets you click the ones you want, then hands back the selection as a batch.

It's an interactive node, which means it changes how your workflow runs: on first run it displays all the images and pauses the workflow for you to choose. Click to toggle, Shift+click for a range, Ctrl+A to select all, Esc to clear. Hit Confirm and the workflow auto-requeues with your choice baked in. That pause-and-resume flow is the trade for getting a real human decision into the graph - it's ComfyUI's answer to "preview culling," and the README's ecosystem section mentions exactly that Eclipse feature set (Get First/Last, preview culling, seed interop).

What comes out

• images - your selected frames stacked into a batch [N,H,W,C]. The gotcha in the tooltip: they're resized to the first selected image's dimensions, so if your batch had mixed sizes, everything comes out uniform. Usually that's a feature; occasionally it's a surprise.
• indices - the confirmed selected indices, as a LIST. This is the part that feeds back into automation: wire it to a slice or a re-ordering node and the selection becomes data you can reuse instead of a one-shot visual choice.

The execution_trigger input is the node's internal re-execution counter - the tooltip is explicit that the UI updates it on Confirm and you shouldn't touch it manually. Leave it alone.

How it actually runs

Under the hood the node fingerprints its input (so it knows when the batch changed), stores the previews and your selection keyed by the node, and uses the trigger to re-fire after Confirm. If you're the kind of person who hates nodes that block, note the honest alternative: it's an output node, so it runs every time - that's required for the interaction to work. For batch work it's the difference between "select frames by eye in 20 seconds" and "edit a JSON list."

Installing

ComfyUI_Eclipse, r-vage's all-in-one pack. Manager → search ComfyUI_Eclipse, or:

cd ComfyUI/custom_nodes
git clone https://github.com/r-vage/ComfyUI_Eclipse

Restart; under Eclipse → Image → Batch Operations. Standard deps; the pack targets current ComfyUI (frontend 1.51.2+) and v4.0 removed legacy RvTools_v2 nodes (Migration Tool for old saves). Interactive nodes are the most sensitive to frontend version, so if the picker misbehaves, update ComfyUI first.

The thing to plan for: the resize-to-first-selected behavior means your pipeline should tolerate uniform-size output, and the pause means you don't want this node in an unattended batch run - it's an interactive tool by design. Use it when you're curating, and wire around it when you're not.