AZAll File Browser

The transparency node, and one of the pack's most underrated. AgentAZAll_FileBrowser renders the agent's mailbox directory as a Unix-style tree - inbox, outbox, sent, remember, notes, the works - with inline annotations: message files get their From/To and subject appended, memory and note files get a preview of their first line. One run and you can see exactly what your agent knows and what's sitting in its outbox, without opening a terminal.

The pack's whole bet is that filesystem-as-memory is inspectable and portable; this node is how that bet pays off inside ComfyUI. When something's wrong, this is your diagnostic tool.

How it works

Point it at a config and it walks the agent's data folder recursively, printing the tree with the box-drawing connectors (├──, └──) you know from tree. Hidden files are filtered except the .agent_key (the agent's signing key - it shows up in the tree, and now you know where to look if you ever want to see it). Message files in inbox/outbox/sent get annotated with direction and subject - <- From: editor@localhost | Review notes - and remember/notes files get a # preview of their first 60 characters.

By default it shows only the current agent's tree. Flip show_all_agents to true and it renders the whole mailbox_dir - every agent in the system - which is the right view for debugging multi-agent workflows to confirm Relay actually dropped the message where you expected.

The inputs that matter

• config (required) - from AZAll Setup.
• show_all_agents - false = just this agent's tree; true = the whole mailbox directory.

The tree output is the rendered string - wire it into a Text Display to actually see it (it's not an output node, so nothing shows unless you display it).

Installing it

In cronos3k/comfyui-agentazall - 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 models, no keys.

Common issues

The main gotcha is expecting it to show something and getting (empty - no mailbox directory found) - that means the config points at a mailbox that hasn't been created, usually because Setup ran with a different working directory (the pack-wide cwd issue) or the agent name changed. Also remember the tree reflects disk at the moment it runs: if you want to verify a Send landed in the recipient's inbox, you need Relay to have run first, and if you want to see the result of this run's writes, order the nodes accordingly. It's read-only - nothing here modifies files, which is exactly why it's safe to throw into any workflow as a debug view.