PC: Show Prompt

The display name gives it away: "PC: Show Prompt." Its internal class name, PCExtractScheduledPrompt, is less friendly but does the same thing - you feed it raw prompt text written with Prompt Control's syntax, and it shows you exactly what got parsed out of it at a given point in the schedule. If you're new to this pack's syntax and your generation isn't matching what you typed, this is the node to reach for before you touch anything else.

How it differs from PCPromptFromSchedule

PCPromptFromSchedule does something similar but takes an already-parsed PROMPT_SCHEDULE object. This node takes raw text directly and parses it itself, and - the part that makes it a genuinely useful debugging tool rather than just a duplicate - it adds three boolean toggles to expand parts of your prompt that would otherwise stay collapsed: segments, substitutions, and macros, all features the README groups under "organize complicated prompts."

The inputs that matter

• text (required, multiline) - your raw prompt, syntax and all.
• at (required, 0–1, default 1) - the point in the schedule to resolve. Note the default is 1, the end of the schedule, not the start - set it to 0 explicitly if you want to check the beginning instead.
• tags (optional, default empty) - pull just a tagged segment, same mechanism as FilterSchedule.
• expand_segs, expand_subs, expand_macros (all optional booleans, default false) - flip these on to see segments, substitutions, and macros expanded in the output rather than left as-written.

Output is a single STRING - wire it straight into a text-preview node and read it.

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

The resolved text looks nothing like your typed prompt. That's often exactly what this node is for catching - a macro or substitution expanded in a way you didn't expect. Flip expand_macros and expand_subs on and re-check; the difference between the collapsed and expanded view usually points straight at the misunderstanding.

You checked at=1 and it looks fine, but generation still looks wrong. Remember 1 is the end of the schedule. If your issue is with how the prompt starts or transitions mid-generation, you need to check other at values too - 0 for the start, and whatever fraction your suspect [a:b:X] swap happens at.

This node is listed under "tools," not core. That's accurate and deliberate - it's a debug utility, not part of your production graph. Once you've confirmed your syntax does what you meant, swap this out for the real encode/schedule path (PCLazyTextEncode or the primitive nodes) rather than leaving a debug node wired into your actual generation.