Pipe Meta Edit

Pipe Meta Edit is the in-line version of Meta Edit: it sets a key → value pair on the meta dict inside a FULL_PIPE and hands you the pipe back, so you can annotate a workflow without ever unpacking the pipe. One wire in, one wire out, and a metadata note rides along to the Save node.

This is a "clean up your workflow" node in the truest sense. The alternative - with the pack's own FullPipeOut - is to unpack the pipe, extract meta, edit it, pack it back in. That's three nodes and a tangle of wires just to write one note. Pipe Meta Edit collapses it into one, which is exactly the author's stated goal for the whole pack: the Easy-Use pipe system is fine in concept but too slow to rewire, so everything here is built to be one-node-and-done.

Why would you annotate a pipe at all? The meta dict rides all the way to Save (Full Pipe), which reads it to build A1111-style metadata. The loader fills in ckpt_name, the prompt nodes fill in positive_text/negative_text. Pipe Meta Edit is the escape hatch for everything else: which style preset ran, what source image this frame came from, which variation batch - anything you want to see in the saved file's metadata but that no other node thinks to record.

Inputs and outputs

• full_pipe - required, in and out.
• key and value - plain strings. model_family / illustrious, purpose / experiment-3, whatever you need.

Output: the same full_pipe, with meta updated (existing keys preserved - it copies the current dict and only sets the one key, so chaining several Pipe Meta Edit nodes is safe).

Installing

Part of the mudknight utils pack. ComfyUI Manager → search comfyui-mudknight-utils, or:

cd ComfyUI/custom_nodes
git clone https://github.com/mudknight/comfyui-mudknight-utils

Restart ComfyUI. No model downloads, no dependencies beyond core ComfyUI.

Gotchas

• Metadata you never see - if your workflow ends in a plain SaveImage instead of the pack's Save (Full Pipe), the meta dict is ignored. The A1111 metadata path is pack-specific.
• Keys collide silently - setting ckpt_name yourself would overwrite the loader's value. Pick names that don't clash with ckpt_name, positive_text, negative_text unless you mean to.
• "meta" vs the pipeline - this edits the pipe's metadata, not the ComfyUI workflow JSON. If you're trying to inject into the embedded workflow, that's a different mechanism (and handled by the save node).

It's a tiny, zero-impression node in a niche pack - the sort of thing you install for the loader and prompt nodes and then discover makes your output files actually tell you what happened.