Atticus vs QwenPaw

Atticus

Atticus runs a person's Mac by voice on their existing Claude or Devin plan, with a sandboxed safe mode and a local log of every command. It has no API, MCP server or documented command for another agent, it is five days old, and it rebuilds itself from the main branch every six hours by default.

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.

Atticus

1. Don't plan to call Atticus from another agent. It takes requests only from its own shortcut and typing box
2. If a user runs Atticus beside you, expect it to move windows and type into apps on the same Mac
3. Point a user who wants pinned versions to Settings > About & Updates to turn off self-update

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