Boolean Basic

About as simple as a node gets: it outputs a boolean, true or false, that you set with a toggle. That's the whole thing. You reach for it when some other node has a boolean input - an "enable" flag, a "use model 1" switch, a bypass toggle - and you want that decision to live in its own labeled node rather than buried inside the consuming node's widget.

It sounds trivial because it is, but a dedicated boolean source earns its place once your graph gets big. One clearly-named toggle you can find at a glance beats hunting through a busy node's parameters for the flag you meant to flip.

How it works

One input, boolean, a toggle that defaults to false. One output, BOOLEAN, carrying whatever you set. Wire that output into any node that takes a boolean and you've externalized the decision.

The common pairing in this pack is the Choose Upscale Model node, whose use_model_1 input is a boolean - drive it from a Boolean Basic (or route it through Boolean Reverse first) and you've got a clean, visible upscaler toggle. It also works anywhere ComfyUI expects a BOOLEAN, not just ControlAltAI nodes.

The inputs and outputs that matter

• boolean - the toggle. Set true or false.
• BOOLEAN - the output. Plug it wherever a boolean is wanted.

There's genuinely nothing else to it.

How to install it

ComfyUI Manager → search ControlAltAI Nodes → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/gseth/ControlAltAI-Nodes

then restart. No dependencies.

Common issues

Hard to break a constant. The only real question is whether you even need it - if a node's boolean is set-and-forget, just set it on the node. Boolean Basic pays off when you want the flag externalized: shared by several nodes, prominently placed, or flipped often. If you need to feed a value and its opposite to two different places from one decision, pair it with Boolean Reverse so a single toggle drives both. And remember it defaults to false, so a freshly-dropped node outputs false until you flip it.