KIE • Review Text

Most nodes in this pack can spend your money. This one exists to stop them.

KIE • Review Text takes a string, displays it in the graph in a readable panel, and passes it straight back out. No KIE call, no credits, no key required. It is deliberately, aggressively dumb - and if you're building a paid generation chain, it's the node you should be reaching for more often than you probably do.

Why a passthrough node matters

Look at a typical KIE Next pipeline: Script to Shot Draft produces a shot plan, Variation Matrix produces four prompts, Sound Cue Sheet produces a sound-design brief. Every one of those outputs is a JSON string, and every one of them eventually flows into a node that submits a real job to a paid API.

In a plain ComfyUI graph, that JSON is invisible. You queue, you pay, you look at the picture, and only then do you notice take 3 said "close-up framing" when you meant "close-up, no hat". Review Text puts the text on the canvas before that happens. It also persists the last reviewed text inside the workflow, so reopening the graph shows you what you actually approved rather than a blank box.

The label input is what makes it practical: set it to shot plan or SFX cue sheet and the panel headers itself, so a graph with four review nodes isn't four identical grey boxes.

Inputs and outputs

• text - a required, forced-input STRING. The socket is forceInput, meaning it takes a connection; it isn't a widget you type into. Wire it from any node that emits a string.
• label - plain string, default Review before generation. Cosmetic, but do fill it in.

One output: text, the same string in, the same string out, so you can keep the chain going. It's an output node, so it executes when you queue the prompt - which is the correct behaviour: you see the brief on the same run that would spend the credits.

Two habits worth building:

• Put it on the branch you're about to pay for, not a side branch you'll forget to look at.
• If the review reveals a problem, mute the downstream generation nodes before you queue again. Review Text tells you the truth; it doesn't stop anything.

Installing it

cd ComfyUI/custom_nodes
git clone https://github.com/felipederosilva/ComfyUI-KIE-Nodes-Next
cd ComfyUI-KIE-Nodes-Next
pip install -r requirements.txt

Restart ComfyUI, then find it under KIE Next / Studio / Production. Or search "KIE Next" in ComfyUI Manager - the README notes v0.6.1's Registry approval was still pending at release, so the git clone is the documented path if Manager comes up empty.

Dependencies are requests, Pillow, numpy and PyYAML for the whole pack. This node needs none of them specifically - it's about twenty lines of Python - so it will work on any ComfyUI install, including one where the KIE API is unreachable.

Gotchas

Nothing appears. Check the label widget first - it renders a header and body panel; if the connected string is empty you get an empty body, not an error. Feed it a node that always emits something.

You typed into text and it ignored you. forceInput sockets only accept connections. If you want to write your own brief by hand, use ComfyUI's core Primitive or a Note, and wire that into Review Text.

It's not a blocker. The node displays and forwards; it can't gate execution. If you want a hard stop, that's still you, watching the panel before you hit Queue.