AZAll Text Display

The simplest node in the pack and the one you'll use constantly while building. AgentAZAll_TextDisplay is a sink: text goes in, the text appears in the node's UI, and nothing comes out. That's the whole job. It exists because ComfyUI's native text output options are inconsistent and this pack's nodes - and especially its LLM - produce strings you want to look at before wiring them somewhere permanent.

Every demo workflow in the pack uses it, usually at the end of a chain, precisely because when you're debugging a multi-agent pipeline, seeing the actual text at each stage beats guessing.

How it works

You feed it a string and it returns {"ui": {"text": [...]}} - the ComfyUI display mechanism that renders the value on the node. There are no outputs, because it's an OUTPUT_NODE: the node's entire effect is showing you what flowed through. The text input is marked forceInput, so it must come from an upstream node - you can't hand-type the value and expect it to display.

The inputs that matter

• text (required) - the string to display. Wire it from the LLM's response, from Recall's results, from Inbox's listing, from FileBrowser's tree, from ChatHistory's formatted_history - anything that emits STRING.

There are no outputs and no optional inputs. If you've used WAS Node Suite or rgthree-style text display nodes, this is the same idea without any bells.

Installing it

It's part of cronos3k/comfyui-agentazall - you get it when you install the pack. Manager search "AgentAZAll", or:

cd ComfyUI/custom_nodes
git clone https://github.com/cronos3k/comfyui-agentazall.git
pip install "agentazall>=1.0.13"
# restart ComfyUI

No dependencies beyond agentazall, no models, no keys.

Common issues

The only real trap is expecting it to do more than display. It won't save text to disk, format it, or route it anywhere - for those, the pack gives you Remember, Note, Text Combine, and the Conditional Router. If you wire it up and see nothing, check the node is actually connected upstream (with forceInput, an empty unconnected widget displays nothing) and that the run actually executed the chain. Also worth knowing: it re-runs on every queue execution like the rest of the pack, so it's always showing you the current value, which for a debug view is exactly what you want.