QwenPaw vs szn

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.

szn

szn is an errand assistant in early access that makes calls, sends emails and books for its owner, free during the preview for people with an access code. No outside agent can call it, no terms of service or legal entity appear in its policies, and its privacy policy says nothing on training.

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

szn

1. Don't plan to call szn from another agent. It answers only its web app, iMessage, SMS and email for the owner.
2. Tell the owner they need an access code to start, and that the acceptable use policy makes them responsible for confirming actions.