AZAll Relay (Local Delivery)

The node that makes the pack's messaging actually work. Send queues a message in the sender's outbox, but nothing happens until a Relay runs: it scans the outbox, copies each message into the recipient's inbox (using the To: header to find the right mailbox folder), ensures the recipient's copy is marked new, and moves the original to the sender's sent/ folder. Then it reports what it delivered.

If you've built a multi-agent workflow and messages never arrive, Relay is almost always the missing piece. It's the mailman, and like a mailman it only does local delivery - both agents have to share the same mailbox_dir.

How it works

Feed it a config and it walks the agent's dated outbox folders, newest first. For each message it parses the headers, reads the To: address, builds the path mailbox_dir/<recipient>/<date>/inbox/, and copies the file there. It patches in a Status: new header if the message lacks one, so the recipient's Inbox node will show it correctly. The original gets moved to sent/ so it isn't re-delivered next run. The delivery_report output summarizes what happened: how many delivered, to whom, with which subject - or No messages to deliver. when the outbox is empty.

It's OUTPUT_NODE, so it's designed to sit at the end of a chain and report. Note the exact-address rule carries over from Send: the To: header must match the recipient agent's name character-for-character, because that string is the folder name.

The inputs that matter

• config (required) - from AZAll Setup. Which agent's outbox it drains depends on this config, so make sure it's the sender's config, not the recipient's.

That's it - no optional inputs. The delivery_report output is your log; wire it to a Text Display to watch the deliveries happen.

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 three classic failures: no Relay node in the graph at all (messages just accumulate in outbox); mismatched agent addresses (nothing finds the recipient's folder); and different mailbox_dir values between agents (the recipient's inbox isn't in the same tree Relay is writing to). If delivery reports an error per message, read the error text - it's per-file, so one bad message won't take down the batch. And a small gotcha: delivery is copy-based, not move-based for the recipient's copy, so both agents end up with the file; the sender's copy moves to sent/, the recipient's lands in inbox/. The pack's own demos (Novel Crafter, Agent Debate) show the intended placement - Relay on the sender's side, after Send.