PC: Prompt (without scheduling)

You're here because ComfyUI Prompt Control's headline node, PC: Schedule Prompt, does more than your prompt needs. This is the stripped-down sibling: a CLIP and a prompt in, one conditioning out, and the [a:b:c] scheduling grammar deliberately ignored along the way. The display name is the entire story - "Prompt (without scheduling)".

What it's for

Prompt Control is famous for letting you write prompts like [cat:dog:0.3] and having one prompt box switch what's being generated halfway through sampling. That power comes from a scheduling parser that splits your text into segments and builds a graph of encoders, one per segment, then merges the conditionings.

PCLazyTextEncodeSingle skips all of that. It assumes your text is a single, unchanging prompt and just encodes it. If you look at the two side by side - this node and PC: Schedule Prompt - the only difference in inputs is that there's no scheduling machinery to trip over.

How it works

Under the hood it runs your text through the same graph-building path the scheduler uses, minus the schedule parsing and the ConditioningSetTimestepRange wrapper the scheduler tags each segment with. It expands the pack's DEF macros first - a feature the plain PCTextEncode node deliberately doesn't support - then builds a small graph that lands on PCTextEncode with your text unless you've used a NODE() call to swap in a different encoder. Because it goes through that graph path, you still get the pack's other text niceties (AND, BREAK, TE(), STYLE(), CAT/AVG) from a single encode.

The one trap

If your prompt contains scheduling syntax like [red hair:blonde hair:0.5], this node will not do what PC: Schedule Prompt does with it. No scheduling means the brackets are passed through as literal text - you'll get square brackets in your tokens, not a mid-sampling wardrobe change. That's the single most common confusion, and it's right there in the name. Want prompt switching? Use PC: Schedule Prompt (PCLazyTextEncode). Just want one prompt, no fuss? This works.

Inputs and outputs

There's only what you'd expect:

• clip - your text encoder (typically straight out of a CLIP Loader or after LoRA hooks).
• text - the prompt, multiline. Everything else is done for you.

Output is a single CONDITIONING that wires into your KSampler's positive or negative input.

One honesty note: the node is flagged experimental and dev_only in the source, and the pack's own docs don't cover it. For a plain prompt with no macros, the plain PCTextEncode node is the documented, equivalent choice - reach for this one when you specifically want the macro/NODE() expansion path on an unscheduled prompt. Expect to see it more often in downloaded workflows than in the Add Node menu.

Getting it installed

It's part of ComfyUI Prompt Control by asagi4, so you install the pack, not this node. Fastest route: ComfyUI Manager → Install Custom Nodes → search ComfyUI Prompt Control, then restart. Manual route:

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

Restart ComfyUI after cloning. There are no model downloads and no extra pip dependencies - the parser is vendored inside the repo. The one real requirement, from the README: you need ComfyUI 0.8.0 or newer for the v3 node schema. If the nodes don't appear after a fresh install, update ComfyUI and try again - that fixes most load failures with this pack.