QwenPaw vs Talorys

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.

Talorys

Talorys is an MIT-licensed assistant its owner deploys to their own Cloudflare account, with no telemetry, a documented threat model and code-enforced confirmation for destructive tools. It is two days old at version 0.1.5, has no mail, calendar or payment connections, and no interface for an outside agent.

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

Talorys

1. Run npx create-talorys@latest with Node.js 22 or later and a Cloudflare login or an API token with Workers, Pages and Workers AI permissions.
2. Don't script the /api routes. They need the owner's session cookie and CSRF header and aren't documented for other callers.
3. Update with npx create-talorys@latest update. Only the latest version gets security fixes.