Dots vs ZeroClaw

Dots

Actions that affect accounts or share information pass an automatic review, and custom rules can require approval or a hand-off. Dots is a beta on Pro plans from $100 a month, and no status page, terms, privacy policy or way to delete individual saved notes was found in the pages we could read.

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.

Dots

1. Say what may be sent. Asking a dot to draft replies does not permit sending them, and an action outside a stated scope needs another decision
2. Stop three things separately. Pause stops the main task only, delegated tasks stop in Activity and recurring tasks in Scheduled, and completed actions are not undone
3. Connect each thing separately. A messaging channel grants no access to an inbox, an app or a computer
4. Sign out of websites and disconnect apps yourself when removing access. Revoking dots access or disconnecting an app does not delete information already obtained
5. Keep the connected computer online with the ChatGPT app open for local work. Only one personal computer can be connected at a time

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