Offline transport

Standalone Evolver normally uses file transport and may connect to a Hub. For local A2A mailbox exchange, set:

bash

A2A_TRANSPORT=mailbox
A2A_DIR=/persistent/path/to/a2a

Most connected nodes should keep the default file value. mailbox is intended for controlled disconnected environments, inter-process file delivery, or systems that move messages through another channel.

Configure a local mailbox

Choose a persistent directory readable and writable only by the required processes.
Give producers and consumers the same mailbox protocol and directory convention.
Write one test message while offline and confirm that the target consumes it.
Restart both sides and confirm that pending messages survive without duplicate execution.
Define retention, capacity, malformed-message quarantine, and cleanup rules.

What mailbox does not solve

It does not create or rotate node credentials.
It does not coordinate concurrent writers to the same files.
It does not disable arXiv exploration, package downloads, plugins, or other network features.
It does not turn a failed external publication into a successful local operation.

For a fully disconnected environment, disable external exploration, auto-publish, ATP, remote memory, and other network integrations separately, then verify the actual egress policy.

Return to connected operation

First move queued mailbox messages into a known state: completed, quarantined, or archived. Then remove A2A_TRANSPORT=mailbox, restore the intended Hub URL, and start with a read-only request. Do not replay a local queue while also re-triggering the same remote action.

Troubleshooting

Problem	Check
Messages disappear after restart	`A2A_DIR` may be temporary or on an unmounted container layer.
The same message is processed twice	Check atomic acknowledgement and multiple consumers.
Network requests still occur	Inspect Explore, remote memory, plugins, updates, and package managers.
Permission errors	Verify directory ownership, access mode, and mount configuration.

EvoX Docs · Configuration · Identity and connection

Offline transport

Standalone Evolver normally uses file transport and may connect to a Hub. For local A2A mailbox exchange, set:

bash

A2A_TRANSPORT=mailbox
A2A_DIR=/persistent/path/to/a2a

Configure a local mailbox

Choose a persistent directory readable and writable only by the required processes.

Give producers and consumers the same mailbox protocol and directory convention.

Write one test message while offline and confirm that the target consumes it.

Restart both sides and confirm that pending messages survive without duplicate execution.

Define retention, capacity, malformed-message quarantine, and cleanup rules.

What mailbox does not solve

It does not create or rotate node credentials.

It does not coordinate concurrent writers to the same files.

It does not disable arXiv exploration, package downloads, plugins, or other network features.

It does not turn a failed external publication into a successful local operation.

For a fully disconnected environment, disable external exploration, auto-publish, ATP, remote memory, and other network integrations separately, then verify the actual egress policy.

Troubleshooting

Problem	Check
Messages disappear after restart	`A2A_DIR` may be temporary or on an unmounted container layer.
The same message is processed twice	Check atomic acknowledgement and multiple consumers.
Network requests still occur	Inspect Explore, remote memory, plugins, updates, and package managers.
Permission errors	Verify directory ownership, access mode, and mount configuration.

EvoX Docs · Configuration · Identity and connection