BMAB SD-WebUI API BMAB Extension

This node is a signal, more than anything else, of where BMAB actually came from. Before it was a ComfyUI pack, BMAB was an Automatic1111 extension - one real user on r/StableDiffusion mentioned using "Bmab a lot" on A1111 back when reinstalling their setup, well before the ComfyUI port existed. This node is part of that lineage: it's a configuration piece meant to drive BMAB's post-processing features on a remote A1111/Forge instance through its API, from inside a ComfyUI graph - for people who kept both UIs around and want to script the older one from the newer one.

What we can say for certain, and what we can't

The info_schema for this node is unusually sparse: no required inputs at all, one optional socket (extension, an EXTENSION type), and one output of the same type. That shape says this is a settings/config node meant to be wired into a larger SD-WebUI-API graph - one that presumably includes other "SD WebUI API" nodes for the actual txt2img/img2img calls, none of which are covered in this batch of articles, and none of which the pack's README documents at all. What exact BMAB post-processing options this node configures, and what widgets beyond the schema's visible sockets it exposes, isn't something we can responsibly guess at from the schema alone.

If you're trying to use this node for real, the honest starting point is: you need a running A1111 or Forge install with the original BMAB extension installed and its API enabled, and you're looking to drive that instance's post-processing from a ComfyUI graph rather than replicate the behavior natively in ComfyUI. If that's not your setup, this node has nothing to offer you - it's not a general-purpose BMAB feature, it's specifically the API bridge to the old extension.

The inputs and outputs that matter

• extension (optional, EXTENSION) - presumably chains from or into another SD-WebUI-API extension configuration node elsewhere in a larger graph.
• Output: extension (EXTENSION) - passed onward, same type.

That's the entirety of what the schema tells us.

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

Same two companions as the rest of the pack, Fannovel16/comfyui_controlnet_aux and cubiq/ComfyUI_IPAdapter_plus, per the README - already in ComfyICU's shared image.

Common issues & troubleshooting

You added this node expecting it to run BMAB's post-processing locally, in ComfyUI. It doesn't - that's what the rest of the pack (Resize By Person, Reframe, Inpaint, and friends) is for. This node is specifically for talking to a separate, running A1111/Forge instance over its API.

You don't have an A1111/Forge install with BMAB running anywhere, and this node isn't doing anything useful. That's expected. Without a remote SD WebUI target to actually talk to, this node has no work to do - it's not a self-contained feature.

We can't tell you the exact configuration options this node exposes beyond the schema shown here. If this bridge matters for your setup, the pack's Python source is the only place to get certainty - the README and the schema don't go deep enough on the SD-WebUI-API side of BMAB to say more responsibly.