WebUI Bridge ADetailer Conditioning

A detailer that re-renders a face crop using the same prompt as the whole image is half a tool. You don't want "1girl, blue dress, standing by the sea" steering a face crop - you want "detailed eyes, detailed face, high detail skin" and a matching negative that fights the usual small-region artifacts. WebUI Bridge ADetailer Conditioning is the node that makes that second prompt set real.

It takes the conditioning you already built, plus your clip, and re-encodes the ADetailer module's dedicated positive and negative prompts into fresh conditioning that you feed to the Apply node. The base prompt and the detail prompt end up as two separate sets of conditioning, which is exactly how the detect-and-refine loop is supposed to work.

How it works

The node reads the adetailer section out of module_config - the same JSON blob the main WebUI Prompt Bridge node produces. If the module is disabled, it passes your positive and negative straight through untouched. If it's enabled, it tokenizes and encodes the configured detail prompt (default something like "detailed face, detailed eyes, detailed hands") and negative prompt with the clip you provide, and returns those as the new conditioning.

Note what it does not do: it doesn't run any sampling, and it doesn't detect anything. It's a prompt-preparation node. Its outputs positive and negative are meant to be wired into a detailer that accepts custom conditioning - in this pack, that's WebUI Bridge Apply ADetailer, or any FaceDetailer-style node that takes a positive/negative conditioning input.

Inputs and outputs

• clip - required, and it should match the model family you're running. An SDXL clip won't encode the way a Qwen-Image clip does.
• positive, negative - your existing conditioning; pass-through when disabled.
• module_config - the Bridge's settings blob.
• Outputs: positive, negative (the detail-pass conditioning) and status - a string reporting which model/confidence/denoise settings went into it, useful for debugging.

How to install

Part of the ComfyUI-WebUI-Prompt-Bridge pack - ComfyUI-Manager → ComfyUI WebUI Prompt Bridge, or clone into custom_nodes and restart. No extra models. Its only real prerequisite is that you're using the pack's module_config output so the settings exist to be read.

Common issues

The most common mistake is expecting it to work without a detailer downstream - it's conditioning, not a fix. Wire its outputs into an Apply/detailer node or you'll see no change. And if you've configured the detail prompt in the main Bridge node but this node keeps passing things through, the adetailer module is almost certainly disabled in settings - the README is explicit that a panel being visible doesn't mean the module is enabled. One tip: since the negative detail prompt is what stops re-rendered eyes from melting, don't leave it blank, even if you think the base negative covers you.