MiniMax H3 Inline Prompt Override (Plan v2)

Sometimes you don't want the full ceremony. You've got a working prompt, you want to try a variant, and you want to flip back and forth without deleting nodes or re-pairing prompts and plans. Inline Prompt Override (Plan v2) is the small experiment node for exactly that: a drop-in between a prompt source and Apply Reference Plan where you paste a full H3 prompt override, or disable it and pass the original through.

It's deliberately tiny - four inputs, three outputs, no model calls, no pausing. Its value is that the override path stays honest with the rest of the pack's philosophy: descriptive prose may change, but compiler-owned structure, references, dialogue, timing, and media routes stay locked. You can't use this node to smuggle in a hand-edited <Subject 4> that the compiler never assigned.

Inputs that matter

• h3_prompt - the compiled or enhanced prompt to use when the override is disabled or empty.
• plan_context - the matching plan from the same prompt source. The node keeps all reference media attached to it.
• override_prompt - the full H3 prompt to try. Blank text bypasses the override. Structural/reference/dialogue changes in it are rejected.
• use_override - the toggle. Disable it to keep your experiment text in the workflow while forwarding the original prompt. This is the A/B switch: same graph, two behaviors, one boolean.

Outputs

• h3_prompt - the inline override, or the original when bypassed.
• plan_context - the media-bearing plan with a plan-bound approval for exactly this prompt.
• override_report - whether the override was used and which compiler-managed structures were verified.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/ethanfel/ComfyUI-MiniMax-H3-Guide

Restart, browse MiniMax H3 → Plan v2. No extra dependencies.

Gotchas

• The override must be a full prompt. This isn't a "find-and-replace" widget; you paste a complete H3 prompt or nothing. Partial snippets get rejected because the validator needs to check the whole structure.
• Override and plan must agree. Same rule as everywhere in this pack - if h3_prompt and plan_context come from different sources, the downstream Apply Reference Plan will refuse the pair.
• Use it for experiments, not final structure. If you find yourself overriding the same structure every run, you're fighting the compiler - move the change into the plan itself (edit the Shot or reference node) and drop the override.

The right mental model: this is the "try a prompt variant, compare, keep the winner" node. Pair it with Prompt Review Gate if you want a human pause before generation, or use it solo for quick side-by-side runs. For everything else, let the plan be the source of truth.