AIHub Action Set Project Config Boolean

AIHub Action Set Project Config Boolean is one of four near-identical nodes in this pack that write a value into the client project's config file - this one writes a boolean (true/false). It's a bookkeeping node: it doesn't produce output for you, it records state for the project. Think of it as the workflow saying "this run used a fallback," "the background is enabled," or "mark this job as done" - a value that a later workflow or the client app can read back via the matching expose-project-config node.

The "project" concept is core to how otavanopisto's ComfyUI-aihub-workflow-exposer organizes multi-step work: a project is basically a folder with a config.json and files, which the client manages - the most useful form of state for step-by-step generation. This node sends a SET_CONFIG_VALUE message over the pack's own websocket (port 8111) with the field path and the value; the client decides how to store it.

How it works

When it runs, it sends a JSON message to the client: {"type": "SET_CONFIG_VALUE", "field": "<field>", "value": <value>}. That's the entire job. The client's project store writes it wherever it keeps config - a config.json in the project folder in the basic case. Dots in the field value address sublevels, so effects.blur.enabled becomes a nested path.

The inputs that matter

• field (required) - where to write the value. Use dots for sublevels: settings.face_restore.
• value (required) - the boolean to store. A widget toggle on the node, or wired in if your workflow computes it.

No outputs, and unlike most action nodes this one doesn't even ship a file - it's pure state mutation.

Installing it

ComfyUI Manager (search "ComfyUI-aihub-workflow-exposer"), or:

cd ComfyUI/custom_nodes
git clone https://github.com/otavanopisto/ComfyUI-aihub-workflow-exposer
# restart ComfyUI

No dependencies - the pack has no requirements.txt.

Where people get burned

The field path is your contract. The client reads back exactly the path you wrote - settings.foo and foo are different keys, and the client's read node needs to use the same dotted path or the value is invisible. Also remember this only matters inside a project: if the workflow isn't running in a project context (set on the workflow controller), there's no project config to write to. And the pack-wide rule applies: no aihub client connected means the message goes nowhere and nothing appears to happen.