AstrBot vs ZeroClaw

AstrBot

Fourteen official messaging adapters, scheduled tasks and scoped API keys come in one AGPL-3.0 program with releases most weeks. No tool call asks for approval, no mail, calendar or long-term memory connector is built in, and usage statistics, including the machine's hostname, are sent by default.

ZeroClaw

Supervised autonomy is the default, so tools outside a short read-only list wait for the owner's approval, and secrets are encrypted in the config file. The docs state that command execution is not written to an audit log, and the project publishes no privacy policy or terms.

AstrBot

1. Set ASTRBOT_DISABLE_METRICS=1 before the first start. Statistics, including the hostname, are sent to tickstats.soulter.top by default
2. Set dashboard.host to 127.0.0.1 in data/cmd_config.json, or the DASHBOARD_HOST variable, unless remote access is intended. The default is 0.0.0.0
3. Create an abk_ key in Settings, OpenAPI with only the scopes needed, and send it as Authorization: Bearer or X-API-Key
4. Include username in every POST /api/v1/chat body. Without the chat:admin scope an administrator ID is rejected
5. Check Extensions, Future Tasks after asking for a schedule. One-off tasks are deleted after their run even when the run fails

ZeroClaw

1. Keep [risk_profiles.<alias>] level = "supervised". full runs every tool not listed in always_ask, and the YOLO preset removes the sandbox and path rules too
2. Add sending and account tools such as send_via, google_workspace and http_request to always_ask so a session-level Always grant cannot skip the prompt
3. List senders in [peer_groups.<name>] external_peers. ["*"] accepts anyone on that channel
4. Set [web_fetch].allowed_domains and [http_request].allowed_domains. Fetches run unprompted and the OS sandbox does not block egress
5. Run one-shot tasks with zeroclaw agent -a <alias> -m "<task>". A cron or webhook turn has no prompt, so shell calls fall to the command policy