OpenDuet vs QwenPaw

OpenDuet

Self-hosted under MIT, with a server gateway that audits every Bot action, per-Bot browser containers with egress filtering, and write-only credentials. Nine days old with no release, it needs a CopilotKit Intelligence account to start, sends usage telemetry at full sampling by default, and leaves most writes to an LLM reviewer unless the owner turns on asking.

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.

OpenDuet

1. Follow the README's Quick start (bun install, bash scripts/start.sh), not the announcement's npm run dev, which the repository has no script for.
2. Run bun openbot/scripts/setup-learning.ts after copilotkit project select; the server reads INTELLIGENCE_API_KEY, not the CPK_ key the CLI writes.
3. Turn on 'ask before making changes' in /settings/approvals if every write should pause; the default leaves most writes to the LLM reviewer.
4. To bring your own agent, register it as a remote-ag-ui Bot in agents.yaml; its tool calls still pass through the gateway's policy and audit.
5. Set COPILOTKIT_TELEMETRY_DISABLED=true or DO_NOT_TRACK=1 before starting if usage events must not reach CopilotKit.

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