WebUI Bridge ADetailer Config

This is the smallest kind of node in the WebUI Prompt Bridge pack: a config reader. The main Bridge node bundles a lot of settings into one module_config JSON output - ADetailer, ControlNet, SAM, upscale and mask sections all travel in that single string. WebUI Bridge ADetailer Config just pulls the ADetailer section out so you can see it, use it, or override it.

If you're a beginner, the honest answer is that you may never need this node directly. It exists because the pack's Apply and Conditioning nodes need the ADetailer settings extracted from the shared config blob, and exposing that extraction as a node means you can inspect what's actually configured - or pipe the settings into your own custom nodes if you're building a workflow the one-click builder doesn't cover.

How it works

One input, two outputs. You feed it the module_config string from the main node (or from anywhere, really - it's just a string). It parses the JSON and returns:

• config_json - the ADetailer section as pretty-printed JSON, so you can read the exact model, confidence, denoise, mask_blur and cycles values that will be used.
• enabled - a boolean. If the ADetailer module is turned off in the Bridge's settings, this is false and config_json holds an empty section.

The enabled flag is the part worth paying attention to. Everything else in this pack checks it before doing work, so if your Apply node mysteriously passes images through unchanged, this node is the quickest way to confirm the module is simply disabled.

Inputs and outputs

• module_config (required) - the settings JSON, usually from the WebUI Prompt Bridge main node's module_config output.
• Outputs: config_json (STRING) and enabled (BOOLEAN).

How to install

It's part of the ComfyUI-WebUI-Prompt-Bridge pack. Install the pack via ComfyUI-Manager (search ComfyUI WebUI Prompt Bridge) or clone it into custom_nodes, then restart:

cd ComfyUI/custom_nodes
git clone https://github.com/dianfangsihuo/ComfyUI-WebUI-Prompt-Bridge.git

No models, no extra dependencies beyond what the pack installs. Unlike the Apply node, this one doesn't require Impact Pack because it only parses a string.

Common issues

The one real trap is hooking it to nothing: module_config from the main node, plus this node's output feeding nothing but a preview - that's fine for debugging, but it's not applying anything. Remember this node is a read-only tap; the ADetailer work happens in WebUI Bridge Apply ADetailer, and the settings only matter if that node's module is enabled. If enabled comes back false, go into the Bridge's settings and switch the ADetailer module on before you chase any downstream behavior.