📝AGSoft Show Text
A text debug node that shows the actual prompt, right on the node
- STRING
The most common ComfyUI lie is your prompt: you typed one thing, the node upstream transformed it, and what actually reaches the text encoder is something else entirely. 📝AGSoft Show Text exists to catch that lie - a plain output node that takes a string and displays it in the canvas, so you can see exactly what's about to be encoded. It's the text-only little sibling of the pack's Show Any node.
How it works
One input, text (a STRING), and it displays that text on the node through its frontend JS. It's an output node, so the value also lands in your workflow history - useful when a prompt came out garbled and you want to check what it was last run, not just now.
Two small details make it nicer than it looks:
- It writes the value back into the node's
widgets_valuesin the workflow JSON - so the last-seen text survives a save/reload instead of being a phantom display. - The output is a
STRINGlist (a one-element list, really), meaning you can keep chaining off the node after it. You can park it between a prompt builder and the text encoder - the encoder still gets its string through the node's output, and you get visibility for free. That's the setup you'll actually want.
When to reach for it
Whenever a prompt is doing something unexpected - a wildcard or dynamic-prompt node expanding to garbage, a concatenate inserting stray delimiters, a translation coming back wrong. Park it after the suspect node, queue, read, fix. It also pulls double duty as a "terminal" display node for text you just want to eyeball at the end of a graph (a filename, a caption), since it's lighter than a whole preview node.
Installing
It's the same pack install as everything else here:
cd ComfyUI/custom_nodes
git clone https://github.com/Art-xmaster/comfyui-AGSoft
Restart ComfyUI, or ComfyUI Manager → "comfyui-AGSoft". No models, no dependencies beyond the pack's usual ones. The only thing that trips people up: the output is a list, and most text inputs will accept a list fine, but if a downstream node rejects it, that's why - use it as a monitor, or take the string off a different node when you need a plain single string.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| STRING | STRING | — |