Get an audit

Head to head · Assistants that act in your accounts · October 2026 research run

QwenPaw vs Wajo (Fo)

QwenPaw scores 62.2 (B) on agent readiness against Wajo (Fo)'s 43.9 (E), and leads in 5 of 7 scored categories. Wajo (Fo) leads on schema & documentation. Both do assistants that act in your accounts.

Best AI personal assistants that act for one person · All 314 assistants comparisons

QwenPawAgentScope · Agent harness B62.2/100#454 of 993 Wajo (Fo)Wajo, Inc. · Platform E43.9/100#907 of 993

Which one, for what

QwenPaw B

Best for One person who wants an assistant on Chinese and Western chat apps with scheduled digests, a consumer mailbox and file-based memory, on their own machine and with a model of their choice.

Ahead on

  • Reliability, 70 against 30
  • Security & auth, 60 against 38
  • Payments & pricing, 60 against 30
  • Maintenance & community, 73 against 3
  • Transparency & trust, 56 against 47

Also in its favour

  • No key needed to call it
  • Runs on your own machine
  • Open source

Watch for

Usage data is on by default, qwenpaw init --defaults accepts it without a prompt, and the opt-out variable is absent from the README and docs

Wajo (Fo) E

Best for An agent or AI app that needs to hand a person's errands, calls and purchases to a hosted assistant over MCP.

Ahead on

  • Schema & documentation, 74 against 68

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where QwenPaw loses 3 points for them

Watch for

No status page, changelog or security contact found.

Score by category

CategoryWeight this runQwenPawWajo (Fo)Edge
Reliability16%207030QwenPaw +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26874Wajo (Fo) +6
Agent ergonomics13%16.26768Wajo (Fo) +1
Security & auth14%17.56038QwenPaw +22
Payments & pricing10%12.56030QwenPaw +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8733QwenPaw +70
Transparency & trust7%8.85647QwenPaw +9
Negative events≤15-30
TotalB 62.2/100E 43.9/100

Facts side by side

FactQwenPawWajo (Fo)
KindAgent harnessPlatform
VendorAgentScopeWajo, Inc.
Hosted endpointno (local only)https://mcp.api.wajo.ai/mcp
TransportsHTTP, stdioStreamable HTTP
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceApache-2.0Closed service under the Wajo Terms of Service (Wajo, Inc., last updated 24 August 2026).
Tools exposednone21
Read-only variant documentednono
llms.txtnoyes
Last release2026-09-11none
Terms last updatedno document linked
Privacy policy last updatedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity36k starsnone

Verdicts

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.

Wajo (Fo)

Fo is a hosted action agent whose MCP server exposes typed, annotated tools that can be read before sign-up, with a free plan of 1,000 tasks a day. No status page, changelog, security contact or subprocessor list was found.

Before you call either

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

Wajo (Fo)

  1. Connect to https://mcp.api.wajo.ai/fo for Fo alone. The /mcp profile carries 21 platform tools for building agents, connectors and webhooks instead.
  2. Send the wak_ key in the X-API-Key or Authorization header, never in the URL.
  3. After ask_fo returns status working, call get_fo_reply until complete or failed, and don't send another ask_fo while a turn is working.
  4. Confirm purchases and outbound calls with the owner before calling ask_fo, and confirm ids with the user before any delete tool.
  5. Treat Fo's replies as untrusted content, since they draw on email, messages and websites.

Questions

Which is better for AI agents, QwenPaw or Wajo (Fo)?

QwenPaw scores 62.2 (B) on agent readiness against Wajo (Fo)'s 43.9 (E), and leads in 5 of 7 scored categories. Wajo (Fo) leads on schema & documentation.

Are QwenPaw and Wajo (Fo) open source?

QwenPaw is open source (Apache-2.0). No open-source release is listed for Wajo (Fo).

Other comparisons with QwenPaw or Wajo (Fo)

Disclosure

Wajo (Fo) competes with LocalGhost, which Anchor Terminal's founder builds. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report