PN Switch

PN Switch is the member of the TGu Utilities trio you'll actually reach for daily. MPN Switch swaps a model and its prompts together; this one drops the model and keeps just the Prompt-and-Negative pair. Your checkpoint stays put - you're toggling between two prompt setups, and that covers a surprising amount of real workflow.

Think about how often the model stays fixed while the words change. You want the same base render with and without a negative-prompt crutch (the "bad anatomy, extra fingers" list) to see if it's actually helping. Or two positive variants of the same idea - one plain, one with style tags appended. Or an "add detail" prompt you switch in for the final pass. That's exactly this node: two CONDITIONING pairs in, the active one out.

How it works

Identical mechanism to its big sibling, minus the model lane. active OFF → outputs positive1 and negative1; active ON → outputs positive2 and negative2. No merging, no math - the selected conditioning pair passes through as-is. The widget is a simple boolean, and you can wire it from a control node if you want to flip it programmatically.

The inputs that matter

• active (BOOLEAN, default off) - the whole interface. Off is pair 1, on is pair 2.
• positive1 / positive2 (CONDITIONING) - your two positive prompt encodes.
• negative1 / negative2 (CONDITIONING) - the matching negatives.

Outputs: positive, negative, which feed straight into your KSampler's conditioning slots. Note there's no MODEL in or out here - if you want to swap the model too, step up to MPN Switch from the same pack, or just leave the model wire alone.

Installing it

ComfyUI Manager → Install Custom Nodes → search TGu Utilities → install → restart. No pip dependencies, no model downloads; it's pure graph plumbing, safe and offline. The manual route:

cd ComfyUI/custom_nodes
git clone https://github.com/TGu-97/ComfyUI-TGu-utils

Restart and it lands in the TGu_util category.

Troubleshooting

• Flipping it changed nothing. Check both conditioning pairs are actually connected - an unwired input on the inactive side stays silent until you switch to it, and then your KSampler errors on the missing slot.
• The trigger-word scenario from the README. The pack's LoRA Switch doc says to build the LoRA branch with Conditioning (Combine) or Conditioning (Concat) to append trigger prompts. The same applies here if your "variant 2" positive includes trigger words.
• Expect zero fanfare. This pack's README documents a single node, the GitHub repo is currently unreachable, and the author is long gone. For a boolean passthrough that's tolerable - but if you'd rather not rely on frozen code, rgthree's switch nodes do the same job with an active maintainer.