AZAll Setup

You can't do anything in this pack without it. AgentAZAll_Setup is the bootstrap: it creates your agent's identity, builds its mailbox folders, and hands every other AZAll node the config object they demand on their first input. If a workflow you loaded is full of red input sockets, the missing piece is almost always one of these at the top.

The mental model is email. Your agent gets an address (comfyui-agent@localhost by default), and all its memories, notes, and messages live in a folder tree under that address. Setup is where that address is born and where the tree gets planted.

How it works

Give it an agent name, and it builds a config dict, writes it to config.json next to the data folder, and creates the whole mailbox directory structure - inbox, outbox, sent, remember, notes, and friends. It also generates a per-agent key used to sign outgoing messages (Ed25519, via the agentazall package's PyNaCl dependency). Nothing about this touches the network or needs a key; it's all local files.

One thing worth knowing: the default mailbox location is ./agentazall_data/mailboxes, resolved against ComfyUI's current working directory - not your home folder, not AppData. If you launch ComfyUI from a different directory one day, Setup quietly creates a fresh, empty mailbox there and your agent "forgets" everything until you point mailbox_dir back at the old one. That's the single most common "where did my memories go" moment with this pack.

The inputs that matter

• agent_name (required) - your agent's address. Use something@localhost form; the Relay node looks up recipients by this exact string, so keep it consistent across agents in the same workflow.
• mailbox_dir - where everything is stored. Leave blank for the default ./agentazall_data/mailboxes. Set it explicitly if you want your agent's brain in a fixed, shareable location.
• config_path - if you already have an agentazall config file from the core library, point here to reuse it instead of generating a new one.

Its one output is config (type AZALL_CONFIG) - a custom type that only the other AZAll nodes accept. That single wire is how Setup is meant to be used: one Setup per agent, its config threaded into every node that agent uses.

Installing it

It ships in the cronos3k/comfyui-agentazall pack. ComfyUI Manager: search "AgentAZAll", install, restart. Or by hand:

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

The agentazall package is the only dependency, and it pulls in PyNaCl for message signing. There are no models to download and no API keys. Seven drag-and-drop demo workflows ship in the pack's workflows/ folder, and every one of them starts with Setup for a reason.

Common issues

The cwd gotcha above is the big one - if state vanishes, check where ComfyUI's working directory is and pin mailbox_dir. Also, Setup always re-runs on every queue execution (it returns nan from IS_CHANGED), which is what you want for a stateful node like this, but it means the config it emits is regenerated fresh each run rather than cached. Agent names are case-sensitive strings - Writer@localhost and writer@localhost are different agents with different mailboxes. Keep them tidy from the start and the rest of the pack behaves.