🔱 Artha Logic Passthru

Artha Logic Passthru is the 🔱 Artha pack's controlled valve: any value goes in, a Boolean decides whether it comes out or gets swapped for nothing, and you get the Boolean back on a second output so you can chain decisions. It's the node you reach for when you want a branch to conditionally carry a value - not just a true/false flag, but the actual image, prompt, or number that should flow only when the condition holds.

This is what makes the Logic family more than bookkeeping. Gate and Compare give you Booleans; Passthru turns a Boolean into an actual data gate. "Only feed this image into the sampler when the quality check passed" is exactly its job.

How it works

The state combo (true/false, default true) is the valve. When it's true, the node passes the any-type any input straight through to the any output and forwards the Boolean on the state output. When it's false, the any output becomes None while state still reports false.

The key detail: the Boolean always comes through on the second output, regardless of the valve position. So downstream logic can keep reading the state even when the data path is closed - which is exactly what you want when building an "else" branch.

Inputs that matter

• any - the value to gate. Any type (*): image, string, number, whatever.
• state - the valve position, true/false combo.

Outputs: any (the input, or None when closed) and state (the Boolean).

Installing it

One-pack install, same as the whole Artha family:

cd ComfyUI/custom_nodes
git clone https://github.com/Cyrostar/ComfyUI-Artha-Nodes
pip install -r ComfyUI/custom_nodes/ComfyUI-Artha-Nodes/requirements.txt

restart ComfyUI, or install "ComfyUI-Artha-Nodes" through ComfyUI Manager. No API key, no models, no extra deps - pure routing logic.

Common issues

• Downstream node gets None and errors: the valve is closed (state false). That's the intended behavior - the "else" branch needs to handle the closed state, or you need the state output to drive a switch elsewhere.
• Expecting a fallback value instead of None: Passthru doesn't have a fallback input - closed means None, full stop. If you need "value B when closed," pair it with an Input Selector instead.
• state isn't runtime-controlled: it's a combo you set, not an input you wire. To drive the valve from a live condition, feed a Compare/Gate result into a different structure (or the pack's BOTH TRUE selector modes).

The honest verdict: it's a small node with one job, and it does it cleanly. The None-when-closed behavior is the thing to internalize - design your downstream for it and Passthru becomes the cleanest way to build conditional data flow in an Artha-native graph.