Allma Gate (renamed → Allma Muter)

If you're reading this because you loaded a workflow and found a node called Allma Gate (renamed → Allma Muter), here's the whole story: the node was renamed once its behavior settled, and Gate is now just a compatibility shim that keeps old workflows loading. The actual node you want is Allma Muter. There is nothing to learn about Gate that isn't learned about Muter.

Why the shim exists

A node's class name is what a saved workflow records. Drop the old name and every existing instance becomes a red "missing node" box - including instances sitting inside other people's workflows, since the pack is published. So the author kept AllmaGate as a subclass of the Muter with the same implementation and flagged it deprecated (is_deprecated = True).

When you load a workflow containing a Gate, the frontend rewrites the node type on the fly, so a workflow you re-save stops depending on the shim and records AllmaMuter instead. The Gate alias survives for API-format prompts and for anything that was never re-saved.

What it does (which is what Muter does)

It mutes the branches you point it at - up to ten - with a master enabled switch, the same way Ctrl+M mutes a node. Nothing passes through it; the real wire still runs straight from the source to whatever consumes it, and this node just points at the branch it governs. That's why it has no outputs and never executes. Toggles can be driven by a wire, but only from a literal boolean read before the graph runs - a computed boolean can't be known in time. And nodes you muted by hand are never woken up again by the muter; only the ones it put to sleep come back.

For the full story - why muting is done in the browser rather than as a value, and the Muter-vs-Bypasser decision - read the Muter and Bypasser articles. Short version: mute removes a branch from the graph, bypass keeps the chain whole.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/OliveiraNickolas/AllmaNodes

Restart, and the pack registers both names. No pip install, no backend, no model files. You don't need to do anything about the rename - just be aware that if you re-save a workflow with a Gate in it, it'll come back as a Muter, which is the intended upgrade path. Given the pack is brand new with no community footprint yet, there's no history of rename-related breakage beyond this one, but the shim pattern is the standard way ComfyUI packs handle renames, so treat the deprecation notice as harmless.