MiniMax H3 Review Gate Relay

A context loop run stops at a Review Gate after each scene and waits for you to approve, retry, reroll or stop. The problem is physical: that gate lives inside the workflow that's executing, on the canvas that queued it. Close the laptop, drop the browser session, or reconnect from the machine downstairs, and you're staring at a job that is patiently waiting for a decision you can no longer reach.

Review Gate Relay is the fix, and it's pleasantly dumb about it. There are no inputs and no outputs - INPUT_TYPES is empty and the Python side is a noop. All the work is the node's custom web UI, which talks to the running job's in-memory state.

How you use it

Open ComfyUI on the same server the job is running on, add the Relay to any canvas (an empty workflow is fine), and use the selector at the top of the node to pick the project, branch, scene and gate. No wires, no Plan, no model loaders, and no Queue click. Then:

• browse takes with the selector or the arrows, and play or scrub the selected one - its saved prompt and full seed are shown below the player;
• Approve selected resumes the waiting job;
• Select & stop selects that take and finishes through the original Gate's normal behavior;
• Keep this take is ticked by default on every take. Untick the ones you want the Gate to remove - the selected take is always retained, and the Relay confirms before sending a decision that could delete unchecked takes;
• when Review each candidate is enabled, Next candidate tells the waiting job to generate the next one.

It polls lightweight in-memory state every two seconds. It does not scan chain folders, read checkpoints while polling, decode video on the server, or re-load a video that hasn't changed. Only the preview you selected is actually loaded, which is why this stays usable on a run that's holding 40 GB of VRAM.

The limits, which are the useful part

There has to be a live execution. After ComfyUI restarts, or for a batch that was saved with Pending Review so it stops cleanly instead of holding an execution open, the Relay has nothing to wake. Those jobs are not listed as live gates - go back to the original workflow's saved-review or checkpoint recovery controls. That distinction catches people, because a deferred batch looks exactly like a finished one from a distance.

Ownership doesn't move. The original job keeps project ownership; the Relay never takes it, and you don't need Force ownership. It also never queues its own workflow, which is the behavior you want with top_level_requeue workflows - those still need their original continuation canvas for later prompts.

It doesn't extend anything. The Gate's auto-approval timeout keeps running, and the Relay shows you the deadline without pausing it. If you're relying on a long timeout as a safety net while you walk away, that net still fires.

Decisions are per-job and unambiguous. Multiple waiting jobs are listed separately, and a decision can't silently land on a different project or branch. Prompts and seeds are read-only here: the Relay selects among saved takes, it doesn't copy another workflow's Plan or settings into the current canvas. An explicit ownership takeover by something else still invalidates the job, which is the one thing a Relay can't work around.

Install

ComfyUI Manager, search MiniMax H3 Contex Loop, or:

cd ComfyUI/custom_nodes
git clone https://github.com/seitanism/ComfyUI-H3-Motion-Context-MultiRef.git
git clone --branch main https://github.com/ethanfel/ComfyUI-MiniMaxH3-Context-Loop.git

Restart ComfyUI after cloning or updating, and hard-refresh the browser tab - the Relay is a frontend extension, so a cached page is a node with no UI. No pip dependencies ship with the pack. You still need the H3 model files and the usual companion packs for the run; the Relay itself needs nothing but a live gate on the same server. The Registry entry still uses the older Contex Loop spelling, so search for the display title if the folder name doesn't match.

If it doesn't see your gate

Check, in order: are you on the same server and port as the job; is the job actually executing right now (rather than finished or deferred); and is a different browser tab holding the gate. The host ComfyUI's normal access controls apply here too - if the instance is behind a login or a reverse proxy, the Relay inherits that, and the fix is to get your browser to the real instance rather than to restart anything.