Data storage

Host data directory

The daemon stores everything under a single host data directory — $HOME/.dispatchmy.ai by default — bind-mounted into the container at /data. Container restarts and image updates leave that directory untouched, so agents and credentials survive both.

Agent data

Each agent gets its own subdirectory holding the agent config, the generated Dockerfile and compose file, runtime data, session history, logs, memory data, and artifacts produced during runs.

Lifecycle and persistence

Inside the agent container, only /app/data is bind-mounted from the host (it points at the agent's runtime-data/ subdirectory). Files written there persist across restarts; anything written elsewhere is part of the container's filesystem and resets when the image rebuilds.

Stopping an agent leaves its container in place so you can still read logs. Starting it again triggers a fresh image build — fast in steady state thanks to Docker's layer cache, but only /app/data survives the rebuild.

Deleting an agent removes its container, image, and entire subdirectory under the host data folder. Configuration, sessions, logs, memory, and artifacts all go with it — there's no soft delete.

Backups

Back up the host data directory to preserve agent configuration and history. Treat logs and artifacts as potentially sensitive — they can include task content, tool output, and provider responses.