Workflow Status

Three weeks after you post an image, someone asks what LoRA and settings produced it. You know the answer is in the PNG metadata, but that means opening ComfyUI, dragging the file back in, and reading node widgets one at a time. Unless you wrote it down at generation time, in which case it took five seconds.

Workflow Status writes it down. It collects the values that vary between runs and prints them as plain lines.

What it produces

Every input is optional, and only the ones with a real value show up:

LoRA: klein_softskin_v2
Trigger: ch9ractername
Seed: 8842190
Prompt: editorial close-up
Face Score: 59.9%
Verdict: Identity drift detected

Nothing connected at all gets you (no status fields provided) - which is a clearer thing to see than an empty box, and a decent hint that you forgot to wire it.

The face score line has a small nicety: a numeric score gets % appended if it doesn't already have one, formatted without trailing zeros. So 0.599 prints as 59.9% only if you already multiplied it - otherwise it prints 0.599%, which is honest but a reminder that you're looking at the raw value.

Inputs and output

All six are optional and all are wildcard (*) typed, so INT, FLOAT and STRING all connect directly:

• lora_name, trigger_word, seed, prompt_preset, face_score, verdict
• summary (STRING) - the multi-line text.

The intent is obvious once you look at the input names: they line up one-to-one with the outputs of the rest of this pack. LORA_BASENAME from LoRA Loader + Name, trigger from Trigger Word, seed from the sampler, percentage and verdict from the face-similarity or Face QC nodes.

Where the output goes

It's a STRING, so anywhere text goes. Two sensible destinations:

A text preview node. Watch the summary build up as the graph runs, which is genuinely useful for confirming a QC gate fired when you expected it to.

A save node's metadata or sidecar. This is the one that pays off later. If your save path writes a caption, a JSON sidecar or an A1111-style parameter string alongside the PNG, the summary slots straight in - and now the info is next to the image instead of only inside it.

The case for it

Worth being clear about the value, because "print some values" sounds like a toy. The reproducibility story in this ecosystem rests on metadata embedded in the PNG, and that metadata genuinely is complete - drag the image back in and the whole graph reconstructs. But it's locked in the file. Strip it by re-encoding, screenshotting, or posting through a host that recompresses, and it's gone with no way to recover it from the pixels.

A plain-text summary sitting next to the file is the cheap hedge against that. It's also the version a human can read without opening ComfyUI at all.

Install

Manager → search Orel's Nodes → Install → restart → hard-refresh the browser.

cd ComfyUI/custom_nodes
git clone https://github.com/DarkOrel/Orels-Nodes.git orels-nodes
python -m pip install -r orels-nodes/requirements.txt

Restart and hard-refresh. This node needs nothing from that requirements file - the text and debug nodes are stdlib Python and load on a bare install.

Gotchas

Empty means invisible. A value that arrives as an empty string is dropped from the output entirely, label and all. Handy most of the time, occasionally confusing when you expected a line to be there and it isn't.

It formats, it doesn't compute. No averaging, no thresholds, no decisions. If the verdict says the run failed, that judgement came from the gate node upstream, not from this one.

Seed is whatever you wired. If you take the seed off a sampler widget whose control_after_generate is set to randomize, be aware of the well-known ordering trap: the control fires after the run by default, so the number in the box may be the one that will be used next, not the one that just ran. Switching the global "widget control mode" to Before fixes it once and for all, and it's worth doing before you trust a single seed you've logged here.

Verbose by nature. Six fields wired gives you six lines. Fine for a caption, awkward if you're piping it into a filename - use Filename Builder for that.