Terminal

Full honesty up front: the pack's README never mentions this node once. Not in the Usage examples, not in the Parameters section, not in the changelog. Everything below comes from reading its actual schema, so take it as an informed read rather than documented fact - and its low traffic (16 impressions, zero clicks) suggests basically nobody has needed to look it up either.

What it looks like it does

The schema is about as minimal as a node gets: one required input, a multiline STRING called text, and one output, an IMAGE. It's also flagged as an output node, which in ComfyUI just means it's allowed to be a legitimate dead end in your graph - the same category as Preview Image or Save Image - rather than needing something wired downstream of it.

Put those together and the plain reading is a text-to-image debug utility: type or wire in a string, and it renders that text as an image you can view directly in the ComfyUI canvas. Given it lives in a pack this focused on inpainting internals, a reasonable guess is it started life as a way to dump some debug output - a status message, a value from elsewhere in the graph - somewhere visible, without needing a separate logging setup. Nothing in the pack ties it structurally to BrushNet or PowerPaint; it reads as a standalone utility that happened to ship in the same repo.

Inputs and outputs

• text - a multiline string field. Type directly into it, or wire text from elsewhere in your graph into it.
• Output: a single image, generated from that text.

That's the entire node.

Installing it

It comes bundled with the whole pack - no separate install. ComfyUI Manager: search "BrushNet," install, restart. Manually: cd ComfyUI/custom_nodes && git clone https://github.com/nullquant/ComfyUI-BrushNet && pip install -r requirements.txt, then restart ComfyUI. If the pack loaded successfully, Terminal is available under the same node menu as BrushNet and the rest.

Common issues

There's genuinely nothing to report here with confidence - no README section describing expected behavior, and "Terminal" is too generic a search term to reliably surface community discussion specific to this node rather than unrelated posts. If it doesn't behave the way you expect, don't assume you're misconfiguring something documented; you're probably just running into the limits of an internal utility nobody wrote usage notes for. It's a small enough node that it's easy to just wire something into it and see what comes out rather than hunting for documentation that doesn't exist.

If you're just trying to leave yourself a note on a complex BrushNet or PowerPaint graph - "this run is testing scale 2.0" or similar - dropping a Terminal node next to the relevant section and typing that note into text is a reasonable use, since it renders visibly on the canvas rather than sitting invisibly in a field you'd have to click into. Whether that's what the author actually built it for is a different question, but it's a harmless way to find out what it's good for without risking anything in the rest of your graph - it's a leaf node, so a mistake here can't ripple into your actual inpainting pipeline.