H3 Studio · Context Inspector

The Director is a black box with a lot of moving parts - auto routing, prompt compilation, reference handling, resolution planning. When something comes out wrong, the first question is always "what did it actually decide?" H3StudioContextInspector is the debug node that answers that, without running any generation. It's a pure utility: feed it a studio_context from the Director and it dumps what that context contains.

The outputs tell the whole story at a glance:

• compiled_prompt - the actual prompt H3 will receive, after @ImageN compilation and any enhancement. This is the single most useful debug output in the pack: it shows you whether your references got compiled the way you intended, and whether the enhancement mode mangled or preserved your wording.
• context_info - a string summary of the route and dimensions the Director settled on: which H3 path (FL2VA or REF2VA), the resolution, and the rest of the decisions that live in the context.
• width and height - the final aligned canvas size, so you can verify the resolution planner gave you what you asked for.
• seed - the exact seed the Director picked, which matters more than it sounds. H3 Studio caps seeds at 2^50-1 to stop ComfyUI's LiteGraph from clamping two different randomized seeds onto the same boundary value - and this output is how you confirm the actual value being used before you spend ten minutes sampling a run you meant to change.

How to use it

Wire the Director's studio_context output into this node, attach the outputs to a text display (or just let them sit - the node executes as part of the graph), and check them before you queue an expensive run. It's especially valuable the first few times you use the Director, because the gap between your prompt and the compiled prompt is where most of the surprising behavior lives. When a reference edit comes out ignoring a reference, the compiled_prompt will show you whether the reference even made it into the conditioning - usually the problem is an ordinal mismatch (@Image3 mentioned with only two images connected) or a reference that didn't get a clear role.

When you don't need it

Once your workflow is stable and boring, this node is dead weight - it doesn't participate in generation, it just reports. The pack's own docs classify it under Utilities for a reason. Reach for it when debugging, leave it out of your final graph, and maybe keep it on a bypassed branch so you can toggle it on without rewiring.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/thaakeno/ComfyUI-MiniMax-H3-Studio.git
cd ComfyUI-MiniMax-H3-Studio
python -m pip install -r requirements.txt

Restart and hard-refresh the frontend. No extra dependencies - it's a pure reporting node with nothing to install beyond the pack.