FL Image Picker

Here's a genuinely clever little node. Normally a ComfyUI graph runs start to finish with no human in the loop - which is great until you've generated a batch of 12 and want to send only the 3 good ones into an expensive upscale or video pass. FL_ImagePicker puts you in the middle. It pauses execution, pops a modal showing your batch, and waits for you to click the keepers. Then the workflow resumes with only what you chose. It's the kind of quality-of-life idea that gets posted to r/comfyui as a standalone "hey, this exists" resource - and it did.

How it works

When execution reaches this node, it doesn't just pass the batch through. It halts the run and shows a picker UI in the browser with your incoming images. You select the ones you want, confirm, and the node outputs only those. If you walk away, a timeout_seconds guard eventually releases it so the run doesn't hang forever. Simple concept, and it turns a fully-automated graph into a semi-interactive one exactly where a human judgment call adds the most value - before the costly step.

The classic pattern: cheap generation → FL_ImagePicker → upscale / video / detailer. You spend compute only on the images you actually picked, which on a serverless setup is real money saved.

The inputs and outputs

• images - the batch to choose from. Required.
• timeout_seconds - how long it waits for you before giving up, from 30 seconds to an hour (default 300). Set this to how long you realistically need to eyeball the batch.

Outputs:

• selected_images - the IMAGE batch of just your picks. This is the one you wire onward.
• selection_info and selected_indexes - STRING outputs describing what you chose (and which positions), handy if you want to log or branch on the selection.

Installing it

Part of the Fill-Nodes pack. ComfyUI Manager: search ComfyUI_Fill-Nodes, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/filliptm/ComfyUI_Fill-Nodes

then restart. The pack throws a big "Machine Delusions" banner into your console on startup - cosmetic, ignore it.

Where people get tripped up

• It blocks execution - so it's a bad fit for headless or API runs. This is the big one, especially on cloud/serverless ComfyUI. If nobody's sitting at the browser to click, the node just waits out its timeout_seconds and then releases (usually passing nothing or everything, depending on the timeout behavior). On a scheduled or API-triggered workflow there's no human to pick, so either drop this node from automated graphs or set a short timeout you understand. It's built for interactive sessions.
• The picker is a browser modal. You need the ComfyUI web UI open and focused on the same machine that's running the job. It's not going to reach out to your phone.
• Set a sane timeout. Too short and it releases before you've decided; too long and a forgotten run ties up your GPU. Match it to your actual attention span for the task.
• It's a curation tool, not a filter. If you want automatic rejection (say, dropping black frames), that's a different node - this one is specifically for a human making the call.