NAIA Request Random Prompt (with Override)

The main NAIA Request Random Prompt node has one annoying property: it's all-in. You wire it up, it re-rolls a prompt on every run, and if you ever want a fixed prompt or a fixed resolution you either re-wire the graph or type over the output. This variant, NAIA Request Random Prompt (with Override), is the same engine with a set of switches so you can decide, field by field, whether NAIA's answer wins or your typed input does.

Think of it as the main node plus a bypass lane. You get all the same prompt-engineering override widgets (use_naia_settings, pre_prompt, post_prompt, auto_hide, the 15 preprocessing dropdowns, host/port), but the outputs are now per-field decision points instead of a package deal.

The switches that matter

• use_naia_bridge - the master switch. true (default): normal operation, NAIA is called and the prompt re-rolls each run. false: the node never touches the NAIA server and just passes through the four values you fed it (prompt, negative_prompt, width, height). Better still, in bypass mode it uses a real hash-based IS_CHANGED instead of the always-dirty NaN trick, so if your inputs don't change, ComfyUI's cache holds and the node doesn't re-run at all. That's a genuinely nice touch - it makes this node a drop-in "manual/auto" switch for a whole branch of your graph.
• override_prompt / override_negative / override_width / override_height - the per-field versions of the same idea. With the bridge on, each toggle decides whether NAIA's freshly-fetched value replaces what you typed. true = NAIA wins, false = your widget value (or an upstream connection) wins. So you can roll random prompts but lock the resolution to 1024×1024, or roll a random size but keep your own negative. Mix and match without rewiring anything.

The prompt, negative_prompt, width, height inputs are just typed values (or linked inputs) that act as the fallback whenever the corresponding override is off. Width/height are clamped 64–8192 in steps of 8.

Outputs

Same four as the main node: prompt, negative_prompt (strings) and width, height (ints). They feed the same places - prompt into a positive CLIP Text Encode via Convert Widget to Input, width/height into EmptyLatentImage. The same advice applies: NAIA's negative is a static value from its UI, so usually leave override_negative alone and type your own.

Install and prerequisites

Same pack as the rest of the bridge:

cd ComfyUI/custom_nodes
git clone https://github.com/DNT-LAB/comfyui-naia-bridge.git
cd comfyui-naia-bridge
pip install -r requirements.txt

Deps are just websocket-client and requests; no models. You need NAIA 2.0 with the ComfyUI sync-API patch and Web Session enabled, and a search run first so there's a result set to draw from.

When to pick this over the plain node

Honestly? Only when you need the bypass. If you just want random prompts every run, the plain NAIA Request Random Prompt is simpler and has the same engine. But if you're building one workflow that sometimes rolls prompts and sometimes runs a fixed batch - say, a generator graph you also use for reproducibility - this node replaces what would otherwise be two graphs or a lot of manual bypassing. That cache-preserving bypass is the reason it exists, and it's the reason I'd pick it over manually toggling nodes.