How does comfyui-prompt-control schedule prompts and LoRAs over sampling steps, and what are its syntax limits and version pin?
Problem. Changing prompts or LoRA strength during sampling (A1111-style prompt editing) inside ComfyUI. Conditions. asagi4/comfyui-prompt-control at commit 71f464c3 (pushed 2026-10-13), version 3.0.0-beta.10, GPL-3.0, requires Python >= 3.10. Method. Available only with the PC: Schedule Prompt and PC: Schedule LoRAs nodes (and advanced variants). Syntax [before:after:X] switches at fraction X of the timesteps (0.0-1.0); nesting is allowed; [cat:0.5] means empty then cat; range form [before:during:after:0.3,0.7]; LoRAs are scheduled by placing <lora:name:strength> inside a scheduling expression. Only fractions are supported in the basic nodes; the Advanced nodes accept step numbers if num_steps is non-zero (values with a decimal point below 1 are percentages, otherwise absolute steps), converted to percentages internally. FilterSchedule can select by tag (e.g. SECOND_PASS). Comments start with #, and # : \\ can be escaped. Failure modes. Whitespace is stripped (use NOSTRIP() to keep ...
Structured fields
{
"citations": [
{
"url": "https://raw.githubusercontent.com/asagi4/comfyui-prompt-control/71f464c3206cce850387792fd9ae6219edae560a/doc/schedules.md",
"note": "Scheduled prompts; intro; [project]"
},
{
"url": "https://raw.githubusercontent.com/asagi4/comfyui-prompt-control/71f464c3206cce850387792fd9ae6219edae560a/pyproject.toml",
"note": "Scheduled prompts; intro; [project]"
}
]
}Evidence claims
- [sourced_fact] Problem. Changing prompts or LoRA strength during sampling (A1111-style prompt editing) inside ComfyUI. Conditions. asagi4/comfyui-prompt-control at commit 71f464c3 (pushed 2026-10-13), version 3.0.0-beta.10, GPL-3.0, requires Python >= 3.10. Method. Available only with the PC: Schedule Prompt and PC: Schedule LoRAs nodes (and advanced variants). Syntax [before:after:X] switches at fraction X of the timesteps (0.0-1.0); nesting is allowed; [cat:0.5] means empty then cat; range form [before:during:after:0.3,0.7]; LoRAs are scheduled by placing <lora:name:strength> inside a scheduling expression. Only fractions are supported in the basic nodes; the Advanced nodes accept step numbers if num_steps is non-zero (values with a decimal point below 1 are percentages, otherwise absolute steps), converted to percentages internally. FilterSchedule can select by tag (e.g. SECOND_PASS). Comments start with #, and # : \\ can be escaped. Failure modes. Whitespace is stripped (use NOSTRIP() to keep it); a pre-release version (beta) may change behaviour. Limitations. Documentation page only; interactions with other conditioning nodes untested. Version and date. Commit 71f464c3. · locator: Scheduled prompts; intro; [project] source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |