basicIn_Boolean

It's a checkbox. That's genuinely most of what there is to it - but the reason it earns a spot in this pack's IO_Port family instead of just being "use ComfyUI's own switch node" is the second output. You flip one toggle and get both the value and its inverse, which quietly kills the extra NOT node you'd otherwise need any time one part of your graph needs "if true" and another part needs "if false" off the exact same switch.

What it does

You set boolean_value - true or false, defaulting to false - and the node outputs it twice: once as-is (BOOL) and once flipped (INVERTED_BOOL). That's the entire mechanism. It's the kind of node that's boring right up until you're three levels deep in a preset-switching workflow (which is what this whole pack is built around - the "Loader → Controller → Sampler" framework the README leads with) and you realize you need both a gate and its exact opposite fed from a single toggle, without the two ever getting out of sync because you forgot to flip a second switch to match the first.

The inputs and outputs that matter

One input, boolean_value, and that's the whole surface. Two outputs: BOOL for wherever you want "this is true," INVERTED_BOOL for wherever you want "this is false" - driven by the same click. Wire them into anything that branches on a boolean: this pack's own conditional routing, a switch node, or a gate on whether a controller stack does anything at all.

Where it actually shows up in a workflow

Think of any place a preset-switching graph needs to branch: "if this controller stack is active, run it - otherwise, pass the input straight through untouched." That's naturally a boolean gate feeding two opposite conditions, and it's exactly the shape this pack's Controller Stack modules are built around (the README leads with this: general control stacks for image, wan, AnimateDiff, Kontext, and QwenEdit, each one toggleable). One basicIn_Boolean node, wired to both the "active" branch and the "bypass" branch of a stack, keeps the two conditions from ever describing two different states of the same toggle.

Installing it

Search "ComfyUI-Apt_Preset" in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/cardenluo/ComfyUI-Apt_Preset.git

Run install.bat on Windows (or pip install -r requirements.txt on Linux/Mac) and restart ComfyUI. No models, no extra dependencies - it's a pure logic primitive.

Where this can trip you up

Honestly, there's not much to go wrong with a single checkbox and its inverse - the failure mode here isn't the node, it's forgetting it exists. If you find yourself adding a separate NOT/invert node downstream of a boolean toggle anywhere in an Apt_Preset workflow, that's the sign you should've reached for this instead: one source of truth, two outputs, no chance of the "true" branch and the "false" branch quietly disagreeing because you edited one toggle and not its mirror. Beyond that, the only real gotcha is generic to the whole pack: if the node doesn't show up in the menu after install, check the ComfyUI console on startup for an IMPORT FAILED line - a skipped dependency from the install step, not a bug in this specific node - and rerun install.bat before troubleshooting further.