ImageGetter

ImageGetter is the typed-down cousin of the komojini pack's Getter. Same idea - a key that pairs with a Setter, same execution-order guarantee - but it's hard-wired for IMAGE instead of the wildcard * type. If your graph is mostly images, that's a feature: the output port advertises itself as IMAGE, so you can't accidentally wire an image where a latent belongs, and ComfyUI's type checker catches mistakes at connect time instead of runtime.

Mechanically it's a pass-through, just like the plain Getter. You give it a key, you connect the image you care about, and it forwards that image downstream. The value it forwards is whatever lands on its input - the key is the pairing label, and it forces the ordering guarantee when the matching Setter sits upstream in the execution path. Want true wireless pickup instead? That's CachedGetter, which reads from the pack's in-memory key/value store. ImageGetter is the "keep a real connection, but organize it by name" option.

Inputs and output. key (STRING, required) and an optional value input typed IMAGE. One output, also typed IMAGE (labeled * in the schema, but it's image-typed on the wire). That's the whole node.

When you'd actually reach for it. This is a workflow-legibility node, so it earns its keep on big graphs. Typical use: an image you generate or load early in the pipeline needs to appear in several downstream branches - a comparison node, a video loader, a second-pass sampler. Rather than dragging one wire to three far-flung places, you name it once with a Setter and read it where you need it. If you're on a small workflow, don't bother; a wire is simpler and easier to follow.

The usual gotchas. Because it's a pass-through, a CachedGetter-style pickup isn't automatic: if nothing is connected to value, it falls back to returning the first argument it sees, which will be the key string - and you'll have a string pretending to be an image. And since this is a Feb-2024 pack, the JS that auto-links getter/setter pairs was written against older ComfyUI internals; on a current build the auto-title/auto-color magic can be janky. The execution-order guarantee still holds as long as the Setter actually runs first.

Install. One pack covers all of it:

ComfyUI Manager → search "komojini-comfyui-nodes" → Install → restart

or cd ComfyUI/custom_nodes && git clone https://github.com/komojini/komojini-comfyui-nodes. No model downloads, nothing heavy to install beyond the pack's pytube/opencv requirements. If you're already using the pack's FlowBuilder for step-by-step generation, this is the tidy way to move images between steps.