Active Model

Most nodes move data. ActiveModel doesn't move a single pixel - it's the pack's remote control. Add it to a graph full of ModelParamsPipe nodes and it becomes a dashboard: one toggle button per pipe, and flipping a toggle ON sets that pipe's node to run while every other pipe in the graph gets bypassed. Exactly one model is live at a time, and you switch between them by clicking a button instead of right-clicking around the graph.

The name is a small lie: it doesn't "activate a model" by loading anything. It flips node modes. When you turn one pipe on, every other ModelParamsPipe in the graph is set to bypass mode (and it'll even enforce that rule for you if it catches two active at once). If a pipe isn't in the graph yet, the node just waits - it dynamically builds its toggles from whatever pipes exist, and re-syncs when you add, remove, or rename one.

How it works - and why it's fragile

There are no Python inputs or outputs. The info_schema shows an empty required list and it's registered as an output node, which is the giveaway: all the logic lives in JavaScript (js/active_model.js). The Python stub exists purely so ComfyUI has something to register. The JS scans the graph, registers every ModelParamsPipe, adds a toggle widget per pipe with exclusive-on logic, and exposes a right-click menu with "Activate First Hub", "Switch To Next Hub", and "Log Hub Names."

That pure-frontend design is the double-edged sword. It's why the node can be a lightweight control panel instead of a heavy data node - but it's also why it's the most fragile thing in the pack. JS-heavy custom nodes are exactly what snaps when ComfyUI changes its frontend, and the community has a recent, well-documented scar: rgthree's Nodes 2.0 breakage in late 2025 was almost entirely about frontend-coupled nodes. If you run bleeding-edge ComfyUI and ActiveModel suddenly stops showing toggles, that's the class of problem you're in.

When it's worth it

If you A/B test checkpoints the old way - right-click each loader, Bypass, run, un-bypass, repeat - this is a strict upgrade. One node, one click per model, no hunting for the right node in a crowded graph. It pairs with MySwitchIndex if you prefer dataflow routing (that's the "wire it through a switch" school), but ActiveModel is the "toggle the graph state" school, and honestly it's the more intuitive one for a beginner comparing models side by side.

The caveats are real though: it only recognizes this pack's own ModelParamsPipe nodes, it does nothing outside a multi-pipe graph, and when it can't find any pipes it just logs to the browser console ("No target nodes found") and sits there. If that console message is all you're getting, the node isn't broken - you just don't have any pipes for it to control.

Installing

ComfyUI Manager → search MultiModel → install, or:

cd ComfyUI/custom_nodes
git clone https://github.com/FaberVS/MultiModel

Restart, and make sure the js folder shipped with it - the node is dead without its frontend code. No model downloads, no Python dependencies beyond ComfyUI's own.