Nodes/NodeGPT/DisplayText
ComfyUI Node

DisplayText

Finally, a way to actually see what your agent said

By antonym-git·Created 3 years ago·Updated 2 years ago· 355
DisplayText
  • text

    Here's a small but very real pain point NodeGPT hit: the pack's agents do their talking in the terminal, not on the canvas. The author's own screenshots show the output "displayed in the terminal." So if you want to see what your Chat node actually produced, you need something to surface it in the UI - and that's this node. DisplayString (listed on the registry as "DisplayText") takes a TEXT input and renders it where you can read it.

    It's an output node, which in ComfyUI-speak means it's a dead end on purpose: no outputs, nothing to wire onward. Its entire job is to make a value visible. You'll reach for it at the end of a chain, after Chat or llava, to actually check what the model returned before you decide what to do with it.

    Using it

    One input: text (TEXT). That's it. Take the output of a Chat node, or an llava caption, and drop it in. Run the workflow and the response appears on the node. It's the ComfyUI equivalent of a print() statement - indispensable for debugging an agent that's talking nonsense, which this pack was prone to. Community reports from the era described agents echoing input back and chats that never terminated; a display node is how you'd catch both happening in real time.

    Why it exists at all

    NodeGPT's early builds didn't even have this - output went to the terminal and a text file. The display node came along as the author matured the pack's ergonomics. That's worth knowing because it tells you how raw the rest of the pack is: if showing the text on screen was a feature addition, the surrounding agent nodes are about as rough as their reputation.

    The install story is the pack's story. The README says:

    cd ComfyUI/custom_nodes
    git clone https://github.com/xXAdonesXx/NodeGPT
    

    Restart and requirements auto-install. But as of this writing the repo returns 404 - the author's account is gone - so the clone fails and ComfyUI Manager won't find it. The surviving fork (Guizmus/NodeGPT) only has the early text-gen build, without these AutoGen-era nodes. If you load an old workflow, this is still your eyeball into the graph; if you're building new, ComfyUI's built-in ShowText or any of the maintained display nodes do the same job without the archaeology.

    CategoryAutoGen

    Inputs (1)

    NameTypeDefaultDescription
    textTEXT

    Outputs (0)

    No outputs