PCWrapGuider

This is the smallest-surface node in the whole pack: one GUIDER in, one GUIDER out. No text, no schedule, no settings - just a wrapper. GUIDER is ComfyUI's own type for advanced/custom sampling, the kind you build with SamplerCustomAdvanced and nodes like CFGGuider or BasicGuider instead of a plain KSampler.

Why it exists

Prompt Control's scheduling only means anything if the conditioning and hooks driving your generation actually change at the right points across the denoise. A plain KSampler is the path Prompt Control's lazy graph generation naturally integrates with - that's what most of the pack's examples assume. A custom guider-based sampling setup runs its own step loop instead, built out of core Guider/Sampler nodes rather than a KSampler, and going by where this node sits in the graph - wrapping a GUIDER and handing back the same type - its job is making sure a scheduled Prompt Control graph still gets read correctly inside that alternative sampling path.

Who actually needs this

If you're using a plain KSampler fed by Prompt Control's outputs, you almost certainly never touch this node. It exists specifically for people building SamplerCustomAdvanced graphs - common if you're chasing a newer sampler, a CFG++-style setup, or just want manual control over how noise and guidance compose - who still want their Prompt Control scheduling to behave correctly inside that setup.

The input and output

• guider (required) - a GUIDER, from CFGGuider, BasicGuider, or wherever your custom sampling graph builds one.

Output: a GUIDER - the same guider, wrapped, ready to feed into SamplerCustomAdvanced in place of the original.

How to install it

• ComfyUI Manager - search "ComfyUI Prompt Control", install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/asagi4/comfyui-prompt-control, restart ComfyUI.

Requires ComfyUI v0.8.0+.

Common issues & troubleshooting

Your schedule seems frozen at one point through the whole generation. If you're on a custom SamplerCustomAdvanced graph and a [cat:dog:0.5]-style swap never seems to happen - the output looks like it's stuck at either the start or end state the entire time - check whether the guider feeding your sampler has actually been passed through PCWrapGuider. This is the most likely reason scheduling that works fine under KSampler doesn't take effect once you switch to a custom guider setup.

You don't know where to put it in the chain. It goes between whatever node produces your GUIDER (CFGGuider, etc.) and SamplerCustomAdvanced itself - wrap the guider right before it goes into the sampler, not earlier in the chain.

Everything works fine on plain KSampler and you don't need this at all. Correct - leave it out. It solves a specific problem with a specific sampling setup, not a general Prompt Control requirement.