H3 Context Preview:
The H3 Context Preview node helps you inspect the context assembled for a generation task before relying on it elsewhere in your workflow. It creates a size-limited, redacted audit view, allowing you to review information such as the declared request, reference mapping, evidence, plan, prompt, validation details, and provider information. This makes it easier to check whether your creative intent and supporting context have been represented as expected. The node preserves the original report rather than modifying it, tracks fields omitted or redacted from the preview, and indicates when the preview has been truncated. It also checks the preview’s structure and safety requirements and stops with an error if it cannot construct an acceptable result. As a terminal audit node in the h3_context/audit category, it supports inspection through ComfyUI’s interface rather than generating images or video itself.
H3 Context Preview Input Parameters:
report
A required H3_CONTEXT_REPORT connection containing an inspectable, typed context report from Plan or Compiler. This report supplies the information the node uses to construct its audit preview and retrieve the original prompt text. Connect a compatible report socket rather than a plain text prompt, image, or manually assembled dictionary: the node checks that the underlying report is a valid ContextReport before building the preview. The report’s contents determine which request details, references, evidence, planning information, validation results, and provider metadata can appear in the audit view. The node does not modify the report. There is no default value, numeric minimum or maximum, or selectable option list for this input; it must be supplied through a compatible connection.
H3 Context Preview Output Parameters:
prompt
An H3_PROMPT_STRING containing the exact text stored in the source report’s prompt document. This lets you retrieve the report’s prompt alongside its audit preview without rebuilding or rewriting it. Importantly, this value is taken directly from the source report, not from the redacted or potentially shortened preview, so the preview’s omission and truncation behavior should not be interpreted as protection for this separate output. You can pass it to another node that accepts H3_PROMPT_STRING when you need the original prompt text.
preview
An H3_CONTEXT_PREVIEW containing a structured, bounded, redacted audit representation of the source report. It includes sections for the request, reference mapping, evidence, plan, prompt, and validation, together with provider identity, an optional provider receipt, report and preview identifiers, schema information, limitations, and diagnostics. Report and prompt fingerprints provide identifying values for the corresponding content. The status is COMPLETE or TRUNCATED, indicating whether the preview-building process had to truncate content; COMPLETE does not mean that redaction is absent or that the creative task is guaranteed to succeed. The omitted_fields and redacted_fields entries identify affected field paths so you can understand what the preview leaves out or conceals. This output is an inspection object, not a generated image or video, and it must satisfy the implementation’s safety and serialized-size checks.
H3 Context Preview Usage Tips:
- Connect the report output from a compatible Plan or Compiler node. For example, build your request, prepare the plan, compile it, and connect the compiled report to this node to inspect the assembled context.
- Check the request, reference mapping, and plan together when reviewing a reference-based task. This helps you spot discrepancies between your intended instructions and the context recorded upstream.
- Read the preview’s status, limitations, diagnostics,
omitted_fields, andredacted_fieldsbefore treating it as a complete account of the source report. Missing content may reflect preview limits or redaction rather than missing information upstream. - Treat the
promptoutput separately from the redacted preview. It contains the source prompt text, so review it before sharing it or forwarding it to another service. - Make changes in the upstream request, reference setup, plan, or compilation steps, then run the preview again. This node is read-only and has no exposed settings for editing the report, changing redaction behavior, or increasing preview limits.
- Run the node through ComfyUI’s normal execution flow. Terminal preview emission requires host prompt and execution-node identifiers, which the node attempts to obtain from the execution environment automatically.
H3 Context Preview Common Errors and Solutions:
invalid_report: report must be a ContextReport
- Explanation: The supplied value is not the typed context report expected by the node. Plain text, images, unrelated custom objects, and manually created dictionaries do not satisfy this requirement.
- Solution: Connect a compatible
H3_CONTEXT_REPORToutput from Plan or Compiler and rerun the upstream steps. If the connection already appears correct, check that the connected nodes come from compatible versions of the extension.
preview_failed: context preview construction failed closed
- Explanation: The node received a report but could not build a preview that passed its checks. Possible underlying causes include invalid report content, unsupported schema information, unsafe projected data, or an exceeded preview size limit. “Failed closed” means it stops rather than returning a preview that failed validation.
- Solution: Rebuild the report using the upstream nodes and inspect the ComfyUI error details for the underlying cause. If the report is unusually large, try a simpler request or less extensive upstream content. Avoid manually modifying internal report data.
missing_correlation: terminal preview requires host prompt and execution-node IDs
- Explanation: The node could not obtain the execution identifiers needed to associate the interface preview with the current ComfyUI run. This can occur when the node is invoked outside the normal host execution flow.
- Solution: Execute it as part of a normal queued ComfyUI workflow. If the issue persists there, check the extension’s execution integration and installed version. These identifiers are not exposed input parameters, so adding a report connection alone cannot supply them.
preview_failed: terminal preview emission failed closed
- Explanation: The terminal preview process encountered a problem while checking execution information, interpreting the event state, or building the interface projection. The node stops instead of emitting an invalid interface result.
- Solution: Rerun the workflow through ComfyUI and inspect the detailed error log. Regenerate the report upstream, and check extension compatibility if the failure continues with a newly built report.
terminal preview emission failed closed with a lifecycle-specific error code
- Explanation: A report lifecycle check failed during terminal preview emission. The node preserves the lifecycle error’s own code, so the displayed code may differ from
preview_failed; the supplied code does not enumerate all possible lifecycle codes. - Solution: Use the accompanying code and underlying log message to identify the failed lifecycle check. Regenerate the report in the current workflow and rerun it through the normal execution flow. If it persists, include the exact code when reporting the issue.
preview schema version is unsupported
- Explanation: The preview’s schema version does not match the version supported by the installed implementation. This can appear as the underlying cause of a broader preview-construction error.
- Solution: Ensure the report-producing nodes and preview node use a compatible extension installation, restart ComfyUI after updating, and generate a fresh report.
preview exceeds the bounded byte limit
- Explanation: The serialized preview exceeds the implementation’s maximum permitted size. The check uses its UTF-8 byte size, not simply the number of visible characters. The provided interface does not expose the limit as an adjustable setting.
- Solution: Reduce unusually extensive upstream text or report content where practical, then rebuild the report. If ordinary reports repeatedly trigger this error, retain the detailed log and report the issue rather than trying to increase a nonexistent node setting.
fingerprints must contain report and prompt
- Explanation: The constructed preview does not contain exactly the required report and prompt fingerprint entries. This indicates an internal data-structure problem rather than a missing artist-facing setting.
- Solution: Regenerate the report and avoid manually constructing or editing preview objects. If the problem persists with reports generated by the extension, check version compatibility and provide the detailed error log to the extension maintainer.
provider_identity must be non-empty
- Explanation: The preview’s provider identity is missing, empty, or not text. This violates the preview’s required structure and can cause preview construction to fail.
- Solution: Rebuild the report through the normal upstream workflow and inspect any available provider-related diagnostics. If a freshly generated report still fails, check the upstream integration rather than attempting to set provider identity on this node.
