ShellAgentPluginOutputBoolean

Output Boolean (ShellAgent Plugin) is the pack's simplest output node: it takes a BOOLEAN in, tags it with an output_name, and hands it back to the app as a named true/false field in the workflow's result. The typical use case is a pipeline that ends in a decision - "did this pass the check?", "is this face fix applied?" - where the caller needs an actual yes/no answer, not an image.

Like every output node in this pack, it's a terminal: no output sockets, nothing rendered on screen, the result exists only in what the parent application reads back over ComfyUI's UI result channel.

How it works

The exact same pattern as Output Text and the other output nodes, with a boolean payload. Wire a True/False into the boolean input, set output_name (default output_boolean), and on completion the node emits {"ui": {"output": [value]}}. validate() advertises {title: output_name, type: boolean} to ShellAgent so the app renders a checkbox or yes/no indicator and knows which key to expect. There's genuinely nothing else going on under the hood.

The inputs

• boolean - the value to return. Wire from any BOOLEAN output, or from a comparison node that computes a condition.
• output_name - the key the app reads. Default output_boolean; keep it unique across your workflow's output nodes.

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 model files; the pack's shared pip requirements install alongside it.

Common issues

• Nothing appears locally. Expected for this pack's output nodes - the value goes to the app, not the canvas.
• Can't find a boolean to wire in. Comparison/validation nodes that output BOOLEAN are the usual source; if you only have a widget toggle, convert it to a real boolean first.
• The app always gets the same answer. If the input is a hardcoded toggle, you'll get a hardcoded answer - wire in an actual computed condition.

It's the lightest node in the family and it knows it. One boolean, one name, one result field. That's the whole job, and it does it without fuss.