H3 Native MiniMax H3 Adapter:
The NativeH3Adapter bridges a rendered H3 context report and native MiniMax H3 conditioning workflows. It preserves the final prompt exactly and prepares a declarative wiring manifest—a structured connection plan—describing direct connections from original media to pinned MiniMax H3 conditioning nodes. This helps you carry prepared context into native H3 workflows without having this adapter rewrite the prompt. Its role is to describe the intended native connections, not to generate artwork or execute those connections itself. The node validates the report and stops if wiring construction fails, rather than returning a potentially invalid connection plan. It does not claim equivalence with the official H3 implementation.
H3 Native MiniMax H3 Adapter Input Parameters:
report
Required input of type H3_CONTEXT_REPORT. This must be a rendered H3 context report containing the final prompt document and the context information needed to construct native H3 wiring. Connect the upstream component that produces this report rather than supplying ordinary prompt text, an image, or a manually assembled text summary. The node uses the report to prepare the native connection plan and retrieves the prompt directly from its prompt document, so changes to the report can affect both the preserved text and the resulting wiring. At execution time, the value must be a ContextReport object; an incompatible value is rejected. There are no numeric minimum or maximum values, selectable options, or default value defined for this input.
H3 Native MiniMax H3 Adapter Output Parameters:
prompt
Output of type H3_PROMPT_STRING containing the exact text stored in the report’s prompt document. The node returns this text without adding, rewriting, or summarizing it. This is useful when you want the native workflow to retain the wording already prepared upstream. Treat it as the finalized prompt text, not a new interpretation of the report or a description of the wiring. Because it uses a dedicated H3 prompt socket type, connect it to downstream inputs that accept H3_PROMPT_STRING.
native_h3_wiring
Output of type H3_NATIVE_H3_WIRING containing a NativeH3Wiring object constructed from the report. This is a declarative manifest describing direct original-media connections to pinned MiniMax H3 conditioning nodes. In practical terms, it is a structured plan for compatible downstream workflow components to interpret, not an image, a finished generation, or proof that those connections have already been executed. The node also registers the constructed wiring with the report through its reconstruction-registration helper before returning the results. If wiring construction or that registration fails with one of the handled exceptions, execution stops instead of returning this output.
H3 Native MiniMax H3 Adapter Usage Tips:
- Connect
reportto an upstream rendered H3 context report. A plain text prompt is not a substitute, even if it contains the same wording as the report’s final prompt. - Make prompt changes upstream before producing the report. This adapter preserves the report’s final text exactly and provides no prompt-editing controls.
- Use the outputs with components that support their exact socket types:
H3_PROMPT_STRINGandH3_NATIVE_H3_WIRING. Do not assume that a general text input or a standard image-conditioning input can accept these custom types. - Treat
native_h3_wiringas a connection plan, not an automatically executed native graph. Confirm that your downstream workflow includes compatible components to interpret or use the manifest. - Keep the original media referenced by your report available to the native workflow, since the manifest is intended to describe direct original-media connections.
- This node has no tuning settings beyond its required report connection. For different prompts or conditioning arrangements, adjust the upstream report-producing workflow rather than looking for hidden settings here.
- When troubleshooting a validation failure, check whether the upstream report has actually been produced. Validation temporarily accepts
Noneto defer linked-input checking, but execution still requires a validContextReport.
H3 Native MiniMax H3 Adapter Common Errors and Solutions:
report must be a ContextReport
- Explanation: The node received a value that is not a
ContextReport. This diagnostic uses the codeinvalid_report. Common examples include connecting plain prompt text or providing no usable report at execution time. - Solution: Connect a compatible upstream output of type
H3_CONTEXT_REPORTand verify that its producing node completes successfully. Do not replace the report with text, an image, or another object.
native H3 wiring construction failed closed
- Explanation: The node could not safely construct or register the native H3 wiring and deliberately stopped. For handled errors other than
NativeH3AdapterError, the diagnostic code isnative_h3_wiring_failed. The underlying cause may be a contract-validation failure, a context-report error, or a type or value error. This message alone does not identify the exact report field or operation responsible. - Solution: Check the upstream report-producing node for errors and regenerate the report after correcting them. Review the ComfyUI error details or console traceback for the underlying exception, which is preserved as the cause. If you recently changed the report’s media or context configuration, check those changes first.
native H3 wiring construction failed closed with an adapter-specific diagnostic code
- Explanation: When the underlying failure is a
NativeH3AdapterError, the node keeps that error’s diagnostic code while using the same general failure message. The supplied source does not list the possible adapter-specific codes, so their precise meanings cannot be determined from this node alone. - Solution: Record the diagnostic code and inspect the accompanying traceback to identify the rejected condition. Use that detail to correct the report or native-workflow compatibility issue before retrying; the general message does not necessarily mean the prompt text itself is invalid.
