DP Prompt Mode Controller

This one doesn't generate anything or transform any text - it's a label. A single dropdown that says which of three prompt sources you want active, and an output that carries that choice downstream to whatever node is actually built to read it. Think of it as the master switch at the top of a workflow that has multiple ways to get a prompt and needs one place to decide which is live.

How it works

You pick one of three modes: Prompt_Manager_Prompt, Random_Prompt, or Other_Prompt - names that map to the three different ways this pack lets you get a prompt into a workflow (a manually managed one, a randomly generated one, or something else entirely you're feeding in yourself). The node's only job is to hold that choice and hand it downstream as its output.

The important detail is the output isn't a plain string - it's typed as the same three-value set as the input dropdown. That's deliberate: it means this node's output can only plug into an input on another node that's built to accept exactly those three values, which in this pack is a matching switch node elsewhere that actually branches your graph based on the mode. This node picks the setting; something else reads it and does the routing.

Inputs and outputs

One required input:

• prompt_mode - a three-way choice: Prompt_Manager_Prompt, Random_Prompt, Other_Prompt. No optional inputs.

One output, prompt_mode, typed to those same three values.

Installing it

Through ComfyUI Manager: search ComfyUI-Desert-Pixel-Nodes, install, restart. By hand:

cd ComfyUI/custom_nodes
git clone https://github.com/DesertPixelAi/ComfyUI-Desert-Pixel-Nodes

Restart ComfyUI. Nothing to download - it's a config node, about as lightweight as a node gets.

Where people get tripped up

The main confusion is expecting this node to do something on its own. It doesn't touch your prompt text, generate anything, or route anything by itself - it's purely a labeled setting. If nothing in your workflow visibly changes when you flip the dropdown, that's expected unless you've actually wired its output into a downstream node built to react to it (a switch elsewhere in this same pack that reads the three-way mode type). Trace the wire from the output before assuming the node is broken.

Because the output type is a specific three-value enum rather than a generic STRING, you also can't wire it into an arbitrary text input expecting to get "Random_Prompt" as literal text - ComfyUI's type system will reject a connection to anything that isn't built to accept that exact typed set. If you actually want the mode name as plain text somewhere, you'll need to convert it rather than connect it directly; this node's output is a selector value, not a string.

This is one of a handful of controller/switch pairs in this pack (see also DP Random Mode Controller and DP Random Mode Switch, which follow the identical pattern for a different set of choices) - if you're only looking at this one node in isolation without the switch it's meant to feed, you're looking at half the mechanism.