WebUI Bridge ControlNet Config

WebUI Bridge ControlNet Config is the read-only tap for the ControlNet section of the pack's settings blob. The main WebUI Prompt Bridge node folds preprocessor, model, weight, start/end, resize mode, control mode and pixel-perfect into a single module_config JSON output; this node pulls just the controlnet section out so you can inspect it or hand it to your own nodes.

For most people this is a debugging node. You've configured ControlNet in the Bridge's panel, something isn't steering the image the way you expect, and you want to confirm what's actually in the config - weight 1.0 vs 0.3 is a big difference, and the JSON output makes it visible at a glance. It's also useful if you're building custom workflows and want to read the Bridge's settings programmatically instead of hardcoding.

How it works

One input, two outputs, no models, no computation. Feed it the module_config string:

• config_json - the ControlNet section, pretty-printed. You'll see preprocessor, model, weight, start, end, resize_mode, control_mode, pixel_perfect.
• enabled - a boolean telling you whether the ControlNet module is switched on in the Bridge.

The enabled output is the one that bites people. Every Apply node in the pack checks it before doing work, so if you think ControlNet is running but it isn't, this node is the fastest way to confirm the module is simply off in the Bridge's settings - the README makes the point explicitly that a visible panel is not the same as an enabled module.

Inputs and outputs

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

How to install

Ships with the ComfyUI-WebUI-Prompt-Bridge pack: ComfyUI-Manager → ComfyUI WebUI Prompt Bridge, or git clone https://github.com/dianfangsihuo/ComfyUI-WebUI-Prompt-Bridge.git into custom_nodes, then restart. No extra dependencies - this node parses a string, so it needs nothing beyond the pack itself.

Common issues

Don't confuse this node with WebUI Bridge Apply ControlNet. This one reads and reports; the Apply node is what actually steers the conditioning. If you wire this node's output into nothing but a preview, you're looking at the config, which is a legitimate use - just don't expect it to change your render. If enabled is false and you expected it true, flip the ControlNet module on in the main node's settings, then re-run. And remember the config stores the preprocessor name as a preference, not a guarantee that preprocessing ran - the Apply node doesn't preprocess, so a raw photo in with canny selected will still be raw when it hits the controlnet.