BMAB Remote Access And Save

This is BMAB's own take on Save Image, and most of it is exactly what you'd expect from any save node: a filename prefix, a choice of format, and a date-stamping toggle. The part that isn't standard is remote_name, which the README doesn't document and no example workflow in the repo spells out clearly. Based on the field name and its pairing with BMAB Image Storage elsewhere in the pack (which routes images by a ComfyUI client_id rather than writing them locally), the honest read is that this saves locally and can tag or route the save for some remote destination or viewer - but we can't confirm the exact mechanism from the schema or docs alone. If the remote-delivery half matters for what you're building, budget time to check the pack's Python source rather than assume from the field name.

What's solid: the local save

Setting the uncertain part aside, the base behavior is dependable and simple. It writes your image(s) to disk with a configurable prefix, in PNG or JPG, optionally with a date stamp folded into the filename so repeated runs don't collide or overwrite each other - the same convenience core Save Image gives you, just with the format choice exposed as a widget instead of fixed to PNG.

The inputs and outputs that matter

• filename_prefix (default "bmab", required) - the base name your saved files start with.
• format (enum: png / jpg, required) - pick jpg if you're saving large batches and don't need lossless output; png otherwise.
• use_date (enum: disable / enable, required) - fold a date stamp into the filename to avoid collisions across runs.
• remote_name (STRING, required) - see above; treat this as the piece to verify against source if it's load-bearing for your setup.
• bind (optional, BMAB bind) and images (optional, IMAGE) - you can feed images directly, or pull them off a bind that's already carrying an image through BMAB's pipeline.
• No outputs - is_output_node: true, this is a terminal save step.

How to install it

ComfyUI Manager: search comfyui_bmab. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/portu-sim/comfyui_bmab.git
cd comfyui_bmab
pip install -r requirements.txt

No model dependency - this is a save utility, not a generation node.

Common issues & troubleshooting

Files aren't landing where you expect. Check your ComfyUI output directory configuration first - same as any save node, if you're running with a custom --output-directory or on a hosted setup with per-run output scoping, "where you expect" and "where it actually is" can diverge.

Filenames collide and overwrite between runs. Turn use_date to enable. If you're running the same prefix across many quick iterations in the same session, a date stamp alone might not have enough resolution to keep every run separate - pair it with distinct filename_prefix values per experiment if you need to be certain nothing overwrites.

You left remote_name blank and nothing seems different. That's consistent with the local-save path working independently of whatever the remote piece does - if you only need files on disk, you can likely ignore remote_name entirely and treat this as a Save Image with more filename options.