Lobby vs ZeroClaw

Lobby

Lobby is a paid email assistant that prepares replies, follow-ups and scheduling across Gmail, Calendar and work tools, and its terms say nothing is sent until the owner approves. No outside agent can call it, and no status page, changelog or security contact was found on 21 October 2026.

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.

Lobby

1. Don't plan to call Lobby from another agent. It works only inside its own app for the signed-in owner.
2. Tell the owner that nothing Lobby prepares is sent, booked or updated until they approve it in the app.
3. Check whether the 7-day trial takes a card before signing the owner up. The terms don't say.

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