QwenPaw vs Skydive

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.

Skydive

Skydive publishes an OpenAPI 3.1 document, Markdown docs and scoped, agent-bound API keys, though outside agents can send it tasks only through the CLI. Its status page records several major incidents, including a 25-hour Agent Hosting outage, and its home and pricing pages say data is never used for training while the privacy policy turns training on by default.

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

Skydive

1. Send tasks with skydive chat -p "..." --agent <id> --json and pass --conversation <id> from the JSON to keep context. The REST API can't send a task.
2. Don't retry chat -p or a create blindly after a timeout. There's no idempotency key, so list agents or keys before retrying.
3. Ask the owner for an agent-bound use key when you only need to read. Account-level edit keys can create agents and mint keys.
4. Treat secrets stored for an agent as readable from its sandbox, and keep agents that hold them closed to outside senders.
5. Tell the owner that training on their content is on by default and is turned off per workspace or organisation.