MiniMax H3 Generic Loop Capability / 通用循环能力探针 (Advanced EXP/T8)

ComfyUI has a draft "Generic Loops" scheduler contract being built upstream - a mechanism that's meant to let a model's own architecture define how long-video continuation works, rather than every node pack reinventing its own loop. It's a draft, it isn't released, and that's exactly the problem this node solves: how do you know whether the core you're running even has it?

This node is a probe. It has no inputs, does no sampling, and changes nothing. On execution it inspects the running ComfyUI core for the draft Generic Loops contract and reports what it found. That's the whole job, and the source is explicit that it never enables a draft backend or alters the released T8 long-video runtime. It's in the pack's read-only diagnostics family, next to nodes like the official-risk diagnostic and the tiled-VAE audit - the "tell me what my environment actually supports" crowd.

How to use it

Drop it anywhere on an empty part of the canvas and run. It outputs:

• available (BOOLEAN) - whether the draft contract is present
• status (STRING) - a human-readable state summary
• report_json (STRING) - the machine-readable detail

Wire the booleans and strings to text display or switch nodes if you want to gate other behavior on the result. That's the legitimate use: conditional logic in a workflow that needs to know whether a core has this capability before deciding a route.

Installing it

Part of the T8mars/comfyui-minimax-h3-audio-T8 pack. Search "MiniMax H3 Audio T8" in ComfyUI Manager, install, restart; or:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8.git minimax-h3-audio-T8

Update ComfyUI itself first - this pack family needs a recent core (comfy_api.latest, comfy.weight_adapter, comfy.patcher_extension, comfy.ldm.minimax) and fails wholesale import on old ones, which is the "every T8 node is red" situation you'll read about everywhere.

The honest take

This is a niche utility. If you're not writing conditional workflows around draft ComfyUI features, you will never touch it, and that's fine - it's a diagnostics node, not a feature. The one thing to internalize: available: true does not mean T8 will use Generic Loops. The released T8 long-video runtime is unchanged regardless of what this probe finds, by design. Treat this as an environment inspection tool for people who like to know what their build can do, and skip it if that's not you. The pack's own README is at pains to say these EXP/diagnostic nodes "only generate plans or reports" by default - this one is the purest example of that philosophy.