π RH Text Display
Actually see the text your cloud task returned
- text
RH Text Display is the pack's "show me the text" node. It takes a STRING, prints it to the ComfyUI console in a neat bordered block, and passes it straight through as output. That's it - no cloud calls, no transformation, nothing clever. It's in the pack for one practical reason: RH Execute returns a text output (prompts, captions, LLM-style results, or error strings that come back from a cloud workflow), and if you just ignore that output, you'll never see what it said.
Text outputs in ComfyUI are easy to lose. Images show up as previews, audio and video have their own plumbing, but a STRING just⦠exists. If you've ever wired a text output to nothing and wondered what the cloud workflow actually produced, this node is the missing inspection step.
Inputs and output
One input, text (multiline STRING, default empty), and one output, text, which is the same string passed through unchanged. Because it's an OUTPUT_NODE, the value also shows in the UI when the workflow runs - so it doubles as an on-canvas text viewer. It prints the content to the console wrapped in decorative lines (π and such), which is where you'd actually read it on a headless run.
How it works
Nothing to reverse-engineer: the display() method logs the text to the console and returns it. The pass-through is the subtlely useful part - you can drop this node in the middle of a chain purely as an inspection tap without changing the data flow, since whatever you feed in comes out untouched.
When it matters
Three concrete uses:
- Check what a text-returning cloud workflow (captioning, prompt rewriting, LLM nodes on RunningHub) actually returned.
- Read the
ERROR: ...strings that RH Download stuffs into itstextoutput when a task fails - a failed batch "succeeds" with an error message hidden in text, and this node is how you surface it. - Inspect any string at any point in a graph, RunningHub-related or not.
Gotchas
There's no formatting, no file saving, no "copy to clipboard." The console output is the real deliverable - on a normal ComfyUI launch that means the terminal window you started it from, which many beginners forget exists. Also, because the output is a pass-through, it does not truncate or clean anything; huge text blobs get printed in full. If you want to save the text to a file, you'll be reaching for a Save Text node after this one, not this node's own doing.
Install is pack-wide: ComfyUI Manager (search ComfyUI_RH_API) or git clone https://github.com/xuchenxu168/ComfyUI_RH_API.git into custom_nodes + pip install -r requirements.txt, restart.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | Text to display |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| text | STRING | β |