Create and preview a ComfyUI support report with private fields omitted by default

Use fictional values to check what is omitted

The private-fields example includes a fictional identity, an absolute model path, a CLIPTextEncode prompt, a saved title and an arbitrary custom secret. The default report excludes those values, original IDs, unknown node-type names and model basenames. It retains known base-node names, structural diagnostic codes and aliased dependency relationships.

The output has schema checkaifree.comfyui-support-report.v1 and runnableWorkflow: false. It is a new support document, not the original with secret-looking strings rewritten. The input JSON remains unchanged, and the report is not an importable sanitized graph.

• Download the fictional private-fields JSON — Self-authored three-node API prompt with a fictional person, model path, prompt, title and custom field. It is inspected locally and never executed.

Inspect and save the complete default preview

1. Step 1

   Generate the default report

   Open Prepare a report for a support question and click Try synthetic private-fields example. All Optional content checkboxes are off. Expect api-prompt · warnings, three node entries, one connection, zero errors, one warning and zero unsupported checks.

   Open the support-report tool

2. Step 2

   Check the aliased inventory

   The report contains node-001 through node-003, one dependency reference and one unresolved entry. The third type becomes unknown-type-001. dependency-001 points to node-001 and identifies checkpoint/ckpt_name, but has no value field in the default report.

3. Step 3

   Review every exported field

   Read the Complete report preview in JSON mode. Search or select the preview to confirm that Synthetic-Ada, ada-project, paper café, [email protected], SyntheticSecretDoNotShare and private.json are absent. optionalContent is {}. Fixed diagnostic locations remain, so the report still discloses limited structural information.

4. Step 4

   Download the document you reviewed

   Click Download JSON report or select Markdown in Complete report preview and click Download Markdown report. Files are comfyui-support-report.json and comfyui-support-report.md. To paste a support question, select and copy the complete read-only preview. Include the remaining implementation/version questions rather than describing the report as proof that the graph runs.

Make each optional disclosure visible before downloading

Changing an option removes the old preview. Click Generate report preview to see a fresh complete export before downloading. Even with all three options enabled, the custom secret and unknown custom path remain omitted because those fields are not on the small allowlist. This is omission by documented scope, not automatic proof that remaining content contains no secrets.

Opening a new file or sample, or editing the input, restores hidden optional content. Clear local input removes this tool's current input and preview. Keep your original privately if the support provider needs an exact reproducer later; send it only after a separate review.

Share an incomplete result honestly

Try malformed JSON records errors in a diagnostic report; Try empty workflow produces an empty supported graph with no node inventory. Unknown formats and exceeded processing bounds remain unsupported or incomplete. A downloadable report can describe those failures, so its existence is not workflow success.

JSON limits are 5 MiB, 1000 nodes, 10000 links, depth 64 and 150000 values; added notes are limited to 20000 characters. Default reports reduce copied data but cannot guarantee anonymity or complete privacy. No node, extension, URL, filesystem lookup or model download is performed.

• Official workflow 0.4 schema at fixed docs revision 7ca6a40804ef — Primary reference for saved node fields and six-element link tuples. The local validator implements a stated subset rather than full JSON Schema conformance.
• Official workflow 1.0 schema at the same fixed docs revision — A separate versioned format with state, saved nodes and object-form links. The local subset reports named-slot and subgraph coverage limits instead of certifying runtime compatibility.
• Official base-node definitions at fixed revision ce1e922d8623 — The site's reference catalog contains the 65 names in this revision's base NODE_CLASS_MAPPINGS. Core extras, frontend-only nodes, custom installations and later revisions are outside its scope.

Sources and reproducible inputs

• Download the fictional private-fields JSON — Self-authored three-node API prompt with a fictional person, model path, prompt, title and custom field. It is inspected locally and never executed.
• Official workflow 0.4 schema at fixed docs revision 7ca6a40804ef — Primary reference for saved node fields and six-element link tuples. The local validator implements a stated subset rather than full JSON Schema conformance.
• Official workflow 1.0 schema at the same fixed docs revision — A separate versioned format with state, saved nodes and object-form links. The local subset reports named-slot and subgraph coverage limits instead of certifying runtime compatibility.
• Official base-node definitions at fixed revision ce1e922d8623 — The site's reference catalog contains the 65 names in this revision's base NODE_CLASS_MAPPINGS. Core extras, frontend-only nodes, custom installations and later revisions are outside its scope.