h4 - Docu Scribe

H4_DocuScribe is the node that documents your workflow for you. Drop it on the canvas, connect the nodes you care about, and it crawls the graph backwards from its own position - via ComfyUI's prompt graph object - and writes a Markdown report describing what it found, saved to disk with your chosen filename and path. It's the answer to the question "what the hell does this workflow actually do?" that you've asked about every workflow you downloaded a month ago and forgot.

The mechanism is worth understanding because it's clever and slightly unusual. When a normal node runs, it only receives the values on its inputs - and a tensor carries no metadata about where it came from. So DocuScribe cheats: it grabs the whole graph (prompt) plus its own node ID, finds itself in the graph, and walks the upstream connections node by node, collecting names, types, and settings as it goes. That's why it's a workflow documenter rather than just another display node - it's reading the graph, not the data.

The settings

• filename - the report name, default h4_Report_.
• path - the subfolder, default h4_reports. Reports land relative to ComfyUI's output area.

The input

• source_1 - a * wildcard. Connect nodes here to document them. The spider crawls upstream from whatever you wire in, so the more you connect, the more of the graph it captures.

The output

No tensor outputs - it's an output node whose product is the file on disk. Check your h4_reports folder after the run.

Installing

Same as the pack: ComfyUI Manager → search "h4_Live", or:

cd ComfyUI/custom_nodes
git clone https://github.com/m3rr/h4_Live

restart. Pure Python, no extra dependencies.

Where people get burned

The main gotcha is scope: DocuScribe documents what it can see - the subgraph reachable from its inputs. A disconnected node, or one that feeds your workflow but not this node, won't appear in the report. Connect it to a central node (a sampler or loader) to capture the broadest upstream view. Second, it writes a file; if you've got the pack's QoL file-writing behaviors disabled or are running under ComfyUI Desktop Edition's sandbox, output path quirks can bite - the README is upfront that CDE degrades h4's file/UI extras. If the report folder shows up empty, check the path and whether the graph crawler had anything upstream to find.

It's a genuinely useful habit-builder: wire one into your complex workflows, and every few weeks you get a free map of what you built. Not a hero node, but quietly the most underrated one in the pack.