IAMCCS H3 · LatentGoAhead · Universal Branch

IAMCCS_MiniMaxH3LatentGoAheadBranch is the same node as IAMCCS_MiniMaxH3LatentGoAhead with one difference in the class body:

class IAMCCS_MiniMaxH3LatentGoAheadBranch(IAMCCS_MiniMaxH3LatentGoAhead):
    """Universal graphs execute this branch only through the lazy selector."""
    OUTPUT_NODE = False

Same inputs, same outputs, same render function. The single change is that it is not an output node - it publishes nothing, creates no preview entry, and doesn't mark itself as terminal.

What the flag changes

That one flag is what makes it usable inside the pack's universal graphs. The lazy router (IAMCCS_MiniMaxH3ContinuousBackendLazyRouterR42) wires all four continuity engines into prefixed sockets and evaluates exactly one of them. If every candidate were an output node, you'd get the side effects of four terminals in one graph, including published results from engines that never ran. The branch variant is the version you connect to the router; the full node is the version you use in a dedicated LatentGoAhead workflow where nothing else competes for the terminal slot.

Because it's an intentional non-terminal, the "problem" people report with it is a feature: queue a graph where this is the only LatentGoAhead-class node and you may see no output registered, because nothing in the graph is asking to publish. Wire it through the router (or add a preview node) and it behaves normally.

Everything else lives on the main node

Everything substantive - the past-positioned latent history, the 18/35/52 context window, the freeze-tail detection, the delivery-only joins, the per-run checkpoint folder with latent and frame fingerprints, and the report string that feeds the Ahead Control Room - is described on the main node's page:

• IAMCCS H3 · LatentGoAhead · Native AV History

Install

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

Or Manager → IAMCCS → restart. No extras for this node beyond the FL2VA H3 stack it samples with. One practical note: if a workflow shows both the main node and the branch wired into the same graph, you have two copies of the pipeline with one of them invisible in your output list. Pick one - router for universal graphs, main node for dedicated ones.