Orbits vs QwenPaw

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.

QwenPaw

Mail tools ask for approval by default, automatic mail handling may not delete permanently, and the security docs list what each sandbox backend fails to enforce. Usage data is sent by default, the default approval level passes every tool call no rule flags, and no privacy policy or security advisory is published.

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.

QwenPaw

1. Set QWENPAW_TELEMETRY_DISABLED=true before qwenpaw init --defaults or qwenpaw app. Both send usage data without asking
2. Set approval_level to STRICT or SMART in agent.json. The default AUTO runs every tool call no guard rule flags
3. Set dm_policy and group_policy to allowlist with allow_from on each channel. Both default to open
4. Set QWENPAW_AUTH_ENABLED=true before binding beyond 127.0.0.1. Requests from localhost skip login even then
5. Keep mail tools on ask for send_message, delete_message and delete_thread, and turn on Mail Access Control with automatic handling