Full Pipe In

The mudknight pack's full-pipe convention has a gap: once everything is bundled into a FULL_PIPE, how do you change one thing - a seed, an image, a negative - without unpacking all nine slots, editing, and repacking? Full Pipe In is the answer. It takes an existing pipe and swaps in new values for whatever you connect, returning an updated pipe.

Mechanically it's simple: it copies the pipe dict, then overwrites the keys you provided, skipping anything left empty or unconnected. That's the whole trick, and it's why this node exists - the pack's own loaders stuff model, clip, vae, and seed into a pipe, but once that bundle is on the canvas you'd otherwise have nowhere to inject a per-branch seed or a new image.

The inputs

Required is just full_pipe. Every slot from the pack's pipe schema is optional and behaves like an override: model, clip, vae, positive, negative, seed, image, latent, meta. Leave a slot unconnected and it's passed through untouched. Note that the copy-on-write means the original pipe object isn't mutated - you get a fresh pipe out, so you can fork the same pipe into multiple branches with different tweaks without them fighting.

When you'd reach for it

Three recurring jobs:

• Per-branch seeds. Feed the same base pipe into two FullPipeIn nodes, give each a different seed, and generate variations without a second loader.
• Injecting an image late. A pipe from a loader has no image; FullPipeIn is how you drop one in before a detailer or inpaint node reads it.
• Swapping conditioning. Replace just the positive slot when a prompt node sits before you but the negative should stay.

It pairs with FullPipeOut when you need to escape the pipe at the end, and with FullPipePack when you're building a pipe from raw parts.

Installing it

Same pack as everything else here - ComfyUI Manager, search comfyui-mudknight-utils, restart. No extra dependencies:

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

Where people get burned

Two habits to avoid. First, empty-string inputs are deliberately skipped - so if you wire a text field in expecting it to clear a slot, it won't; nothing clears a slot, you just overwrite. Second, remember that seed is an integer slot, so wire it from a seed source or set it in the widget; a leftover string wire will error. It's a tiny node with a tiny failure surface - once you internalize "copy and overwrite," you've got it.