Meta Edit

Meta Edit is the simplest node in this pack and maybe the most underrated: it sets a single key → value pair on a metadata dict and hands it back. Two string inputs, one META output, nothing else. It exists because the full-pipe system carries a meta dictionary alongside the model and conditioning, and the Save (Full Pipe) node reads that dict to write A1111-compatible metadata - so this is how you get your own notes into the output file.

The full-pipe philosophy is worth a sentence: instead of a pile of wires, one connection carries a bundle, and the meta dict is the part that rides along so your pipeline can remember things across nodes - the checkpoint name, the prompt text, whatever you care about. Most of the time you never touch meta directly because the loader and prompt nodes fill it for you. This node is for the cases they don't cover: "which character preset did this run use?", "what was the source image?", "batch 12 of 40, keep me honest."

Inputs and outputs

• key and value - both plain strings, default empty. Type artist / mudknight and that pair lands in the meta dict.
• meta (optional) - the incoming META dict. If you leave it disconnected, the node starts from an empty dict; if you chain Meta Edit nodes together, each one builds on the previous.

Output: the updated meta dict. The standalone version outputs raw META (which you can then feed into a FullPipePack or a FullPipeIn's meta slot); its pipe sibling, Pipe Meta Edit, does the same thing but reads and writes inside a FULL_PIPE directly.

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. No model downloads, no dependencies beyond core ComfyUI.

Notes and gotchas

• Duplicate keys overwrite - setting the same key twice replaces the value. There's no append; it's a dict, not a log.
• Metadata only matters if something reads it - outside this pack, only Save (Full Pipe) consumes the meta dict for A1111 text, and the ComfyUI workflow JSON is written separately. If you're not using the pack's save node, your key-value pairs won't magically appear in the PNG.
• Not to be confused with the pipe version - if you're mid-pipeline and just want to tag the pipe, use Pipe Meta Edit. This one is for building or editing a META value you'll pack in later.

A two-input utility in a zero-impression pack. If you've ever wished your output files carried a bit more context than the prompt, this is the honest, boring way to make that happen.