H3RelayInternalSegmentPaths

H3RelayInternalSegmentPaths is a boring node with a boring job: you hand it the chain state and a saved segment record, and it tells you the file paths. Where the current clip lives. Where its resume checkpoint is. Where the previous checkpoint is. Which run and shot you're looking at. That's it - no inference, no generation, no magic.

Boring is the point. MiniMax H3 continuation is built on checkpoints: each accepted shot saves a safetensors resume checkpoint so the next shot can continue from an exact visual/audio history instead of hallucinating a fresh take. Something has to know where those files live, and this node is the lookup service.

Where it came from

This is one of the nodes H3 Relay vendors from the Comfy-Org MiniMax H3 Contex Loop runtime and re-registers under its own namespaced class id (the category conditioning/minimax/contex_loop/steerable is the giveaway). Upstream's public registration is disabled; H3 Relay registers the runtime under H3RelayInternal* names so its own graph-builder nodes can construct subgraphs that use them. When you use H3 Relay · Generate Shot, this thing is quietly doing the path bookkeeping in the expanded subgraph.

Inputs and outputs

Two required inputs, both typed wires rather than widgets:

• state (H3_CHAIN_STATE) - current chain state, e.g. from H3 Chain Current Shot.
• segment (H3_CHAIN_SEGMENT) - the saved scene record produced by Segment Save.

Five outputs, all strings except the last:

• current_segment - path to the current clip.
• current_checkpoint - resume checkpoint for this shot.
• previous_checkpoint - the checkpoint before it (empty for shot 1), which is what the next continuation actually extends.
• run_name - the run's name.
• shot_index - which shot this is.

There's a safety check buried in there: if the segment you hand it doesn't match the current state index, it raises "received the wrong saved segment" rather than returning paths for the wrong shot. Continuation from a mismatched checkpoint is exactly the kind of silent-corruption bug this pack refuses to have.

When you'd use it

Almost never by hand. It's an internal utility - if you're building a custom steerable H3 graph and need to feed a checkpoint path into a loader or a script, this is the clean way to get it. For everyone else, it's worth recognizing so you don't panic when it appears in your graph alongside the public nodes.

Install is the shared pack path: ComfyUI Manager → H3 Relay, or git clone https://github.com/akatz-ai/h3-relay into custom_nodes, then restart. Needs ComfyUI 0.32.0+, FFmpeg, and the MiniMax H3 models from MODELS.md - separately licensed, and the H3 Community License is territorial, so check whether you're covered in your region before you run anything.