D2 Save Image Eagle

D2 Save Image Eagle is what happens when you bolt the Eagle asset manager onto D2 Save Image. It saves your file locally exactly like the parent node - with the same filename templates, formats, and metadata - and then registers it into an Eagle folder with a memo attached. If you already keep your generations in Eagle, this removes the single most tedious step in your workflow: the drag-and-drop plus manual annotation that follows every good run. It can even write the full A1111-style generation parameters into the memo automatically.

How it works

Two things happen on every execution. First, the image is saved with all the D2 Save Image machinery - PNG/JPEG/WebP/animated_webp, filename_prefix templating with %date:...%, quality/lossless/fps controls. Second, the file is sent to Eagle's local API, which places it into eagle_folder (by name or ID - a folder by that name is created if it doesn't exist) with memo_text as the item's annotation.

The headline feature is the automatic memo. If you connect the d2_pipe output of D2 KSampler into this node's d2_pipe input, the full parameter set - prompt, negative, steps, sampler, scheduler, CFG, seed, model - is formatted A1111-style and written into the Eagle memo for you. You get a searchable generation record in your library without typing a word. For videos or custom cases, you can override with your own memo_text (the docs show building one with D2 Filename Template2); when both exist, the auto parameters come first, then your custom text.

The inputs that matter

Everything from D2 Save Image, plus the Eagle bits:

• images - what to save.
• d2_pipe - from D2 KSampler; enables the automatic A1111-format memo.
• filename_prefix - filename template (defaults to %date:yyyyMMdd-hhmmss%).
• format / lossless / quality / fps - encoding controls, including animated_webp.
• eagle_folder - Eagle destination by name or ID; created if absent.
• memo_text - custom memo, appended after the auto parameters.
• preview_only / popup_image - preview/gallery behavior, same as D2 Save Image.

Output: filenames, a LIST of saved file paths.

Installing and the one hard prerequisite

Part of D2 Nodes ComfyUI:

cd ComfyUI/custom_nodes
git clone https://github.com/da2el-ai/D2-nodes-ComfyUI

or search "D2 Nodes ComfyUI" in ComfyUI Manager. The Eagle API is the pack talking HTTP to http://localhost:41595, so Eagle must be running with its local API enabled - without that, every save errors out at the registration step. That's the failure mode to know first: check Eagle's running, check the API toggle in Eagle's settings, then suspect everything else.

Troubleshooting

• "Eagle request failed" - Eagle not running, or the API is off. Fix those before anything else.
• No memo on the item - the d2_pipe isn't connected. Without it there are no auto parameters; your memo_text still lands, but the automatic record won't.
• Wrong folder - eagle_folder takes a name or ID; a typo just creates a new folder, which is arguably worse than an error because it silently scatters your library. Check spelling.
• Images saving but not appearing in Eagle - same root cause as the first bullet; the local save succeeds and the API call is what fails.

The pack also has D2 Send File Eagle for non-image files (videos from a Video Combine node), which is the right tool when there's no image save step involved. For the bread-and-butter "generate and file it," this is the node - save, register, annotate, done, all in one click of Queue.