I2Cnet2i Toggle

I2Cnet2i Toggle is the sibling of the pack's I2i Toggle, and like that one it's a single checkbox that passes a boolean through untouched. The name is the author's own shorthand for the workflow branch it controls: an image-to-image pass that goes through a ControlNet - i2cnet2i, roughly "img2img → ControlNet → img2img." You flip it, and the whole ControlNet-guided img2img branch of the graph turns on or off.

It's a gating node, not a router. It doesn't know what a ControlNet is and it never touches one. It emits an enable_i2cnet2i boolean, and the nodes that actually act on it - a CSwitchBooleanLatent to pick the VAE-encoded source image, a CSwitchBooleanConditioning to swap in ControlNet-conditioned prompt, a denoise value that drops below 1.0 - are wired to read that one signal. Flip it once and every consumer agrees.

Inputs and output

• enable_i2cnet2i - BOOLEAN, default off. The single widget.
• Output: the same enable_i2cnet2i boolean, to fan out to as many consumers as you like.

Default off is deliberate: you want the plain txt2img path as the safe baseline and the ControlNet branch as something you explicitly switch on, rather than the other way around.

Why reach for it

If you've ever kept two nearly-identical versions of a workflow - one with the ControlNet branch, one without - because tearing a branch out by hand takes five minutes each time, this is the node that makes that a checkbox. It also keeps the "ControlNet on" state visible in the graph instead of buried in a widget. And because it's a plain typed boolean source, it composes with the pack's lazy switch nodes: the branch you don't select doesn't even execute, so leaving ControlNet off genuinely skips that upstream work instead of computing it and discarding it.

Install

Part of duckcomfy personal nodes. ComfyUI Manager → search "duckcomfy personal nodes" → install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/duckcomfy/duckcomfy_personal_nodes

Restart ComfyUI. No Python dependencies beyond ComfyUI itself, no model downloads - the pack is a personal grab-bag largely copied from other suites to minimize dependency surface and supply-chain risk. That's the whole reason a one-boolean node ships at all: the author needed it in their own graphs and bundled it.

Gotchas

Same as its sibling: the boolean is the instruction, not the mechanism. Wiring this node alone does nothing visible - you need the switch downstream that consumes the boolean. If you flip it and the graph doesn't change, check that the latent switch, conditioning switch, and denoise all read from this output, and that you actually have a ControlNet loader and preprocessor on the gated branch.