Pause Text Pixaroma

Pause Text Pixaroma is the checkpoint for words that Pause Image Pixaroma is for pictures. When text comes out of an LLM prompt node and heads into the rest of your workflow, you have no control over the exact words - and one bad sentence in a prompt quietly spoils the whole render. This node drops into the wire between the text source and whatever uses it, stops the workflow, and lets you read the text in an editable box before it goes on.

The name is the honest description: an inline gate. Wire your text source into the input, your next text consumer out of the output, and press Run. It pauses there, showing the text; tidy it up and hit Continue to send your edited version on. Because the slow LLM step is skipped on Continue, it's fast - you're not re-rolling anything, just approving words.

The buttons that matter

• Pass - flip the toggle and it runs straight through without stopping, useful once you trust the prompt.
• Continue - send your edited text on.
• Regenerate - don't like what it wrote? This finds the node that made the text, rolls its seed, and produces a fresh one. You never have to touch the seed yourself.
• Keep - reuse the same text and make a new image every run. That's the one you want when you're trying one prompt many times and don't want the wording to change out from under you.

There are Copy and Revert buttons right on the node, so you can grab the approved text or roll your edits back.

Inputs and outputs

• text (STRING, optional) - the text to gate. Wire your text source (an LLM or prompt node) here.
• text output - the text continuing downstream: the model's text in Pause/Pass, or your edited text in Continue.

It's an output node, so it can sit at the end of a text chain as a review station, or inline before a CLIPTextEncode.

Install

It ships in the Pixaroma pack: ComfyUI Manager → search Pixaroma → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://gitlab.com/pixaroma/comfyui-pixaroma.git

No models, no dependencies. The pack-wide gotcha: after an update, hard-refresh the browser tab (Ctrl+Shift+R / Cmd+Shift+R) - the browser caches old node visuals, and "it looks broken right after updating" is almost always that, not a real bug.

Where people get tripped up: forgetting the node is there and wondering why a run "stalled." If you see a paused workflow with no error, look for the pause gate - it's doing its job.