Input Boolean (ShellAgent Plugin)

Input Boolean (ShellAgent Plugin) is the simplest node in the pack: a named BOOLEAN slot that a ShellAgent app can flip at runtime - face fix on or off, upscale or not, watermark yes/no. While you're testing locally, the widget is just a checkbox, and what you check is what comes out.

It's hard to say much about this node because there isn't much to say, which is the point. It exists so your workflow has a typed yes/no entry point that an external caller can control, with the app's form rendering it as a checkbox.

How it works

Same pattern as every input node in this pack: validate() tells ShellAgent "this input is a boolean named whatever you set in input_name", the app renders a checkbox, and the chosen value arrives at the node's boolean output as a Python True/False. No default_value? There is one - it's false by default in the optional section, so unset means "off" unless the app says otherwise.

Inputs and outputs

• input_name - the variable name the app sees. Default input_boolean.
• default_value - the checkbox state used when the app doesn't supply one. Defaults to false.
• description - optional help text for the app's UI.

Output: a single BOOLEAN on the boolean socket. Wire it anywhere a boolean is accepted - toggles on loaders, KSampler switches, any node with a boolean input. Note the output type is BOOLEAN, not the older * boolean-y widgets, so it plugs into nodes that declare a real boolean input.

Installing it

Same one-pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/myshell-ai/ComfyUI-ShellAgent-Plugin

restart, or search ComfyUI-ShellAgent-Plugin in ComfyUI Manager. No models, no heavy surprises beyond the pack's usual pip requirements.

Common issues

• The app shows a checkbox but the workflow ignores it. Make sure you actually wired the boolean output into the downstream node's toggle - a checkbox sitting unconnected is just a checkbox sitting unconnected.
• It's always false. Check default_value if the app isn't overriding it; the default is off.
• Won't connect to a node. Some nodes still expose toggles as a widget rather than a real BOOLEAN input, so the wire may refuse. Convert with a boolean→anything utility if you hit that.

This is the node you'll forget exists until a workflow needs a switch the caller controls. Then it's exactly right.