Disarm H3 RefMod Bridge
A node kept alive for old workflows, and that's about it
- status
Disarm H3 RefMod Bridge is the pack's most honest node: it's marked DEPRECATED in the source, kept purely so saved workflows that reference it keep loading, and it does almost nothing. If you're building a new workflow, skip it entirely. If you've inherited one that has it, read this so you understand why it's there and what to do with it.
What it used to be, and why it's now hollow
In older versions of the pack, the Continuum integration worked through process-global bridge state: a bridge would arm somewhere, and the Disarm node was how you tore that state down when a workflow changed branches. That design was fragile - global state leaking between runs, cleanup that didn't happen on errors - and v0.2.0 replaced it. The Continuum RefMod Bridge now scopes everything to a cloned MODEL branch via ComfyUI's public outer-sampling hook, with cleanup on completion, error, or cancellation. There is no global bundle anymore, and therefore nothing left to disarm. The source says as much: "Legacy workflow compatibility: global bridge state no longer exists."
So the node is a no-op with a console message. It takes one input - a trigger integer whose only purpose is to make ComfyUI re-run the node when it changes (set its control-after-generate to randomize if you ever need it to fire per generation) - and returns a status string. Change the trigger, it "disarms," prints a status, moves on. The bridge it would have disarmed isn't listening.
The honest answer
If a saved workflow from the earlier revisions has a Disarm node in it, you have two options: leave it - it's harmless and keeps the graph loadable - or delete it and use the modern equivalent. The modern switch is on Continuum RefMod Bridge itself: enable=False removes the bridge from its cloned model, and bypassing its MODEL output achieves the same. Disarm adds nothing to that flow.
Install
It installs with the rest of the pack - ComfyUI Manager (search "ComfyUI-MiniMaxH3Mod") or:
cd ComfyUI/custom_nodes
git clone https://github.com/Luisacaotica/ComfyUI-MiniMaxH3Mod
Restart. Deps are light; nothing extra. And since this node only makes sense in an H3-Continuum context, you'd also need that pack, real H3 weights, and its VAE in a current ComfyUI - remembering H3's community licence excludes the US, EU, UK and Korea from the local-weights path.
Common issues
The only real "issue" is expectation mismatch: people drop it into new workflows because the name sounds like a safety switch, then wonder what it protected. Nothing. It protects nothing, because there's no armed global state anymore. If a reference persists into a run you didn't want it in, the cause isn't a missing Disarm - check which model branch your Continuum bridge is armed on and flip its enable off instead. This node is a museum piece for backwards compatibility, and the cleanest relationship with it is to delete it from new graphs.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| trigger | INT | 00–4294967295 | Any change re-runs the disarm; 'randomize' after each generate makes that automatic. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| status | STRING | — |