Orbits vs ZeroClaw

Orbits

Orbits is a family household app whose assistant, Bit, runs shared calendars, lists and meals, reads household email and places restaurant calls after approval, with iOS releases every week or two. No outside agent can call it, prices appear only as App Store in-app purchases, and no status page, security contact or named subprocessors were 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.

Orbits

1. Don't plan to call Orbits from another agent. llms.txt says no public agent API is offered.
2. Tell the owner the assistant needs an Orbits subscription bought in the app, and that any trial appears only at purchase.

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