asaply vs ZeroClaw

asaply

asaply is a text-only errand assistant in early access that orders, books and pays through Apple Pay after showing the total, and can read and change a connected Google Calendar and Gmail. No outside agent can call it, the service fee isn't published, and no status page or security contact was found.

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.

asaply

1. Don't plan to call asaply from another agent. It answers only texts from the owner's phone number and group chats it joins.
2. Tell the owner each errand adds an unpublished service fee to the order total.

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