CFG Plan Readout

You chained four guidance nodes. The image got worse. Nothing in ComfyUI will tell you which of them survived, because CFG Megapack works like a plan, not a chain of transforms.

CFG Plan Readout prints that plan. Drop it next to any MODEL wire, queue once, and a text panel on the node shows every stage - when, weak branch, mix, where, correct, govern, measure - in the order they'll run, with what each one is set to. That's the whole node. It's a debugger, and on a pack with one node per stage it's the first thing to reach for when something looks off.

Why the plan matters

Every node in this pack clones the MODEL and writes its own stage of a guidance plan into the model's options. The stages always execute in a fixed order at each sampler step, no matter how you draw the wires, and for most stages a later node of the same stage replaces an earlier one. So SEG then STG gives you STG. Two mix rules give you the second one. Corrections are the exception - those stack.

Which means the graph you drew and the guidance that ran are two different objects. The Readout shows the second one.

It's also how you catch the classic nothing-happened case: another pack's CFG-function node - ComfyUI's own RescaleCFG, Mahiro, RenormCFG - shares ComfyUI's single CFG-function slot with this pack, and whichever got there last wins. If your Megapack node looks dead, check the plan first, then check what you chained after it.

Inputs and output

One input: model. Tap a MODEL wire anywhere between the loader and the sampler.

One output: plan (STRING). The node is a terminal output node, so it has no MODEL output and you can't chain through it - it hangs off the wire as a branch, not in it. It renders the plan as a preview in the node itself when you queue, and you can also wire the string into a text-display node if you want it somewhere handier.

Compare it to CFG Measure: Per-Step Probe in the same category, which is the other half of the picture: the Probe writes per-step numbers (scale used, size of the difference, angles, how often the angle governor fired) to output/cfg_probe/. Readout tells you what you configured; Probe tells you what it did. When you're chasing "why is this image different", you want both.

Install

From ComfyUI Manager, search CFG Megapack and restart. By hand:

cd ComfyUI/custom_nodes
git clone https://github.com/AbstractEyes/comfy-cfg-megapack

Restart ComfyUI, then double-click the canvas and type "CFG Plan Readout". The pack also ships as comfy-cfg-megapack on the Comfy Registry, so comfy node install comfy-cfg-megapack works if you live in the CLI.

There's no requirements.txt because there's nothing to install - it uses torch and the standard library. The catch is the opposite of the usual one: it needs a newer ComfyUI than most packs, since it's built on comfy_api.latest (tested on 0.38.0). On an old build the pack won't import at all and the node won't appear.

Where people get burned

• The panel is empty. Nothing was installed on this model. Either you tapped the wire before the nodes, or every node you chained is bypassed with Ctrl+B, or another pack took the CFG slot.
• The plan doesn't list your weak branch. Because two weak-branch nodes can't coexist - the later one replaced it. That's expected, not a bug.
• The Readout run takes time. It's an output node, so adding it queues a job. It costs nothing but a click, though - no sampling.
• It shows a plan but your image didn't change. A stage can be installed and still be neutral: scale of -1 with the sampler at cfg 1, factors of 1, a governor band of [0, 180], a window of 0 to 1 with everywhere-guidance. Neutral settings reproduce plain sampling on purpose, pixel for pixel.

Don't leave six Readouts in a finished workflow. One, while you're tuning, then delete it.