Natura tinyNature vs ZeroClaw

Natura tinyNature

tinyNature is Natura's hosted personal agent, reached by message today or by voice through $149 HumanPods earbuds, with a published retention table and subprocessor list. No outside agent can call it, and no status page, changelog or dated release 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.

Natura tinyNature

1. Don't plan to call tinyNature from another agent. @tinyNatureBot on Telegram is a chat for the owner, not an API.
2. Send security reports to ops@natura.inc. The security.txt the site links returns 404.
3. Check that tinyNature works on the owner's platform before they order HumanPods, as the HumanPods FAQ advises.

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