Inspect Text
A peek into your string pipeline that doesn't break it
- text
Splice this into your prompt chain and see what's really flowing
Inspect Text (ETInspectTextNode) is the passthrough sibling of the pack's Show Data. It takes a string input, displays it on the node, and - here's the useful part - hands it straight through to an output. It's a debugging node you can leave in a working pipeline without breaking it.
That's its whole advantage over Show Data, which is terminal. Inspect Text lets you answer "what does my prompt actually look like at this point in the graph?" without rewiring anything. In a ComfyUI ecosystem where debugging usually means deleting nodes and rerunning (the core principle: change one thing at a time and see what breaks), a passthrough inspector is the gentler option - you add one node, read, and leave it or delete it.
Where you'll actually use it
- Between a dynamic prompt generator and CLIP Text Encode. Confirm the substitutions actually happened and the string is what you think it is before it gets tokenized.
- After a tagger or captioner. Check that the tags you expected made it through, and whether they arrived as one string or a list.
- Anywhere a string changes hands. If a node is supposed to transform text and the output looks wrong, the fastest way to find out is to look at both sides of it.
How it works
One required input, text (a STRING that accepts input from other nodes), plus a display widget that acts as the readout. The node renders the text and passes it through unchanged to its text output.
List handling is worth knowing: feed it multiple strings and it renders them as a readable List:\n- item block while passing the list through intact - so you can tell at a glance whether a node handed you a single prompt or a batch, which is exactly the kind of thing that quietly breaks text pipelines.
The readout is pushed to the display widget by the pack's small frontend extension on every run, so don't treat it as something you edit - next run overwrites it.
How to install it
Ships in Info Utils (exectails/comfyui-et_infoutils), no dependencies, no model downloads. Install via ComfyUI Manager (search "Info Utils") or:
cd ComfyUI/custom_nodes
git clone https://github.com/exectails/comfyui-et_infoutils
Restart ComfyUI and look for Inspect Text under exectails/Info.
The caveats
Two honest ones. First, it's a STRING node - the text input won't accept an image or a tensor, so for arbitrary data you want Show Data. Second, it only shows you the text; it won't warn you if your prompt is about to get truncated by a CLIP encoder's 77-token limit. If that's your worry, pair it with the pack's Token Counter. Together they cover both halves: what your prompt is, and how much of it will survive the encoder.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | — | |
| display | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| text | STRING | — |