PC: Configure Logging (for debug)

This one doesn't encode anything, patch a model, or touch your prompt at all. It's a volume knob for Prompt Control's own console output, and you'll only ever need it when something in a PC workflow is behaving weird and you want to see what the pack is actually doing under the hood.

What it does

Prompt Control does a fair amount of invisible work - parsing your schedule syntax, building graphs of PCTextEncode and SetConditioningTimestepRange nodes, resolving LoRA hooks, matching up masks to IMASK() calls. Normally you don't see any of that; it just runs. This node sets the pack's internal logging level so more of that process gets printed to your ComfyUI console, which is the difference between "my schedule silently did the wrong thing" and "I can see exactly which segment it parsed and where it went sideways."

It's a pass-through node by design, following the same pattern several other tools in this pack use - attach some configuration to the CLIP object rather than transforming it. The CLIP you feed in comes back out unchanged in every functional sense; it just now carries a logging-level setting that Prompt Control's other nodes pick up.

Inputs and outputs

One required input, clip, and one optional field, level - a dropdown that defaults to INFO. One output: CLIP, unmodified data-wise, passed straight through.

Because this node has to sit before the PC nodes you're debugging in the graph for the setting to take effect, the pack's own description is blunt about it: pass your CLIP through this node before you run any other PC nodes, then feed its output into your PCLazyTextEncode / PCLazyLoraLoader / whatever you're actually debugging.

Installing it

Same as every node in this pack - it ships as part of the single extension, no separate install. ComfyUI Manager: search "ComfyUI Prompt Control", install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/asagi4/comfyui-prompt-control

Nothing extra to download - this node in particular has zero external dependencies, it's a couple of lines of Python setting a log level.

Where it actually earns its slot

Reach for this specifically when a schedule isn't producing the timing you expect, when LoRA hooks don't seem to be applying over the range you scheduled, or when a NODE(...) macro swap in a text prompt isn't picking up the node you named. Wire PCSetLogLevel in front of the chain, bump it up from INFO, rerun, and read the console - Prompt Control's graph-generation approach means the actual mechanics (which conditioning ranges got created, which hooks got attached) are printed rather than hidden inside opaque tensor math, so the log is usually more informative here than it would be for most custom nodes. Once you've found the problem, there's no cost to leaving it wired in - it only affects log verbosity, not generation output or speed.