Send Eagle with text

If you generate images in bulk and then spend an hour dragging them into a viewer and re-typing prompts, this node exists for you. Send Eagle with text is the main node in the ComfyUI-send-Eagle(slim) pack, and it does exactly one thing: drops your finished image into the local Eagle library - annotations, negative prompt, memo and all - while the queue is still running. No manual exporting, no copy-pasting prompts into a tag field afterward.

Eagle, if you're not already in the cult, is a desktop image manager that power users swear by for organizing model outputs and datasets. The community signal matches: when someone on r/StableDiffusion asked how people organize generations, the answer from an Eagle user was basically "Eagle for everything, and this node to connect it directly to Comfy." It's a niche, but a loyal one.

How it works

This is an output node - no outputs, it's the end of the line. When the queue reaches it, it takes the images tensor off the wire, encodes it to webp or png depending on your format setting, and POSTs it to Eagle's built-in local HTTP API (the one running on your machine, localhost:41595 by default). That's the whole trick: no cloud service, no API key, no account. The only thing it depends on is Eagle actually being open.

The author's framing makes the design intent clear. It's the "slim" rewrite of the original ComfyUI-send-Eagle - less kitchen sink, focused on the send-and-annotate flow, with settings like the default folder living in config/default_config.json (copy config.json.template to customize) instead of cluttering the node.

The inputs that actually matter

• images - your finished image, straight out of VAE Decode. This is the only one you can't skip.
• format - webp or png. This choice matters more than people expect (see below).
• lossless_webp - for webp only: on gives you lossless, off gives you lossy.
• compression - webp quality, 1–100, default 80. Only relevant if you're writing lossy webp.
• prompt_text, negative_text, memo_text - all optional multiline strings that become Eagle's annotations and tags on the saved file.

Here's the trade-off to think about before you set format to webp out of habit: png preserves the full ComfyUI workflow - the README is explicit that prompt and extra_pnginfo are embedded as metadata, so you can drag the image out of Eagle, drop it back into ComfyUI, and the whole graph rebuilds. That's a genuinely great archival feature and the whole "workflow included" ethos in one click. Webp is much smaller, but you give up that drag-back round-trip.

Installing it

ComfyUI Manager is the easy route - search for "Eagle" and it's the pack titled ComfyUI-send-Eagle(slim). Or the manual way:

cd path/to/ComfyUI/custom_nodes
git clone https://github.com/shingo1228/ComfyUI-send-eagle-slim.git

Then restart ComfyUI. Notably, this pack has no model files to fetch and no heavy dependency pile - the README lists no requirements.txt drama at all. That's refreshing in an ecosystem where half your setup time is dependency conflict roulette.

Where people get burned

The one failure mode worth knowing: if Eagle isn't running, nothing appears anywhere. The node talks to the local Eagle app over HTTP, so a closed Eagle means your image silently goes nowhere. Keep Eagle open before you hit queue. And if you set a target folder in the config that doesn't exist yet, the README says images fall back to Eagle's root folder - so don't panic when something lands outside your carefully nested structure the first run.