Eagle Image Node for PNGInfo

Let's set expectations before anything else, because the name is doing a lot of promising it can't cash: this node will not push your renders into Eagle. If you came here because you use Eagle (the image-organizing app a lot of artists use to tag and browse thousands of reference images and renders) and you want your ComfyUI outputs to land there automatically with prompt/seed metadata attached, searchable - that's a real, useful thing to want. It's also not what this specific node, as defined, does.

What it's supposed to be

The README credits bbc-mc/sdweb-eagle-pnginfo as the inspiration - an Automatic1111/WebUI extension that exports your generated images straight into an Eagle library, PNG metadata and all, so you can browse your generation history by its actual parameters instead of digging through a folder of 00023.png. Porting that idea to ComfyUI would genuinely be handy. This node is hylarucoder/comfyui-copilot's attempt at that port, and the pack itself is candidly labeled "self-used nodes" in its own README - a solo dev's personal toolbox, not a maintained, feature-complete product.

What it actually does

Here's the part worth being blunt about: this node has zero outputs. Not "an output you have to dig for" - none at all, and it isn't flagged as an output node either. In ComfyUI's execution model, a node only runs if it's marked as an output node (like Save Image) or if something downstream depends on one of its outputs. This node is neither. Drop it into a graph, wire up an image, hit queue - and it just sits there. ComfyUI's executor has no reason to ever touch it, because nothing points to it and it points to nothing.

The inputs also give the game away. image (an IMAGE input) is the only one that looks purposeful. The rest - int_field (an integer, 0 to 4096, step 64, defaulting to 0), float_field (0 to 10, step 0.01, defaulting to 1), print_to_screen (an enable/disable toggle), and string_field (a plain string defaulting to "Hello World!") - are, field for field, the exact placeholder inputs from ComfyUI's own official example custom-node template, the one bundled with every ComfyUI install to teach developers the node API. If those names ring a bell, that's why. It reads like the boilerplate got wired up with an Eagle-flavored name and credit line, and the actual Eagle-export logic - the part that would open a connection to Eagle's API or write metadata into the file - never got attached before it shipped.

None of that makes the fields meaningless if you're poking at it out of curiosity: print_to_screen set to enable is the classic pattern for dumping whatever values the node received to your console, which is a debugging aid, not a feature. But treat the whole node as a stub rather than a working pipeline step.

Installing it

Same story as the rest of the pack - this isn't a heavily-registered community node, so don't count on ComfyUI Manager's missing-node auto-installer catching it reliably when you open someone else's workflow. Install it directly:

cd ComfyUI/custom_nodes
git clone https://github.com/hylarucoder/comfyui-copilot

Restart ComfyUI afterward. No model files, no heavyweight dependencies - the README doesn't list any, and given what the node actually does, that tracks.

Common issues

The one that will actually cost you time: if you wire this into a workflow expecting it to do something - save to Eagle, print metadata, anything - and nothing happens, that's not a misconfiguration on your end. It's the node. There's nothing broken to fix in your setup; there's simply no execution path that reaches it.

If you genuinely want ComfyUI output flowing into an Eagle library, your better move is to look for a pack built and maintained specifically for that purpose on ComfyUI's own node graph, rather than this ported stub - the original sdweb-eagle-pnginfo project it's credited to is an Automatic1111 extension to begin with, so even a finished port would be translating behavior across two different tools' plugin models, not a drop-in.

One more naming note worth flagging: "comfyui-copilot" is also the name of a much larger, unrelated project - an AI chat assistant for building ComfyUI workflows, from a completely different author. If your search results surface something with a chatbot interface, that's not this pack.