Head to head · Assistant proactive · October 2026 research run
Leon vs NanoClaw
NanoClaw scores 68.3 (B) on agent readiness against Leon's 41 (E), and leads in 6 of 7 scored categories. Both do assistant proactive.
Best AI personal assistants that act for one person · All 190 assistants comparisons
Which one, for what
Leon E
Best for A developer who wants a self-hosted assistant with memory, computer use and a local model, and who will read the source.
Also in its favour
- No incidents deducted, where NanoClaw loses 5 points for them
Watch for
No tagged release of the core since 1.0.0-beta.8 on 1 May 2023. The 2.0 Developer Preview is installed by cloning the develop branch
NanoClaw B
Best for A technical owner who wants an assistant on their own machine, reachable from chat apps, with container isolation and scheduled tasks, and who is willing to keep a fork.
Ahead on
- Reliability, 78 against 32
- Schema & documentation, 82 against 33
- Agent ergonomics, 70 against 57
- Security & auth, 74 against 34
- Maintenance & community, 78 against 15
- Transparency & trust, 65 against 60
Watch for
The Claude provider runs with permissionMode: 'bypassPermissions', so shell, file and web tools run inside the container with no prompt
Score by category
| Category | Weight this run | Leon | NanoClaw | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 32 | 78 | NanoClaw +46 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 33 | 82 | NanoClaw +49 |
| Agent ergonomics | 13%16.2 | 57 | 70 | NanoClaw +13 |
| Security & auth | 14%17.5 | 34 | 74 | NanoClaw +40 |
| Payments & pricing | 10%12.5 | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 15 | 78 | NanoClaw +63 |
| Transparency & trust | 7%8.8 | 60 | 65 | NanoClaw +5 |
| Negative events | ≤15 | 0 | -5 | |
| Total | E 41/100 | B 68.3/100 |
Facts side by side
| Fact | Leon | NanoClaw |
|---|---|---|
| Kind | Agent harness | Agent harness |
| Vendor | Louis Grenard (Leon AI) | NanoCo, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2023-05-01 | 2026-10-09 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no 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 | ||
| Popularity | 18k stars | 31k stars |
Verdicts
Leon
Connected-app credentials are encrypted per profile and the Gmail connection is read-only. The 2.0 Developer Preview has no tagged release, runs tools and a 30-minute proactive pulse with no approval step, listens on every network interface with client authentication off, and sends telemetry by default.
NanoClaw
Each session runs in an unprivileged Docker container and API keys stay in a credential gateway on the host, so a manipulated agent cannot read them. Inside the container the agent runs with permission prompts off, network egress is open by default, and it can message any chat it is wired to without approval.
Before you call either
Leon
- Clone the develop branch for 2.0.
npm install --global @leon-ai/cliand docs.getleon.ai install and describe the legacy 1.0 betas - Set
client_interface.auth.enabled: trueand aLEON_PROFILE_TOKENbefore the machine joins a shared network. The server binds 0.0.0.0 - Set
telemetry_enabled: falseandruntime.pulse_enabled: falsein the profileconfig.ymlfor an unattended or private run - Use
availability.tools.allowedto limit tools. Shell, file writes, computer use and browser control are otherwise available to the agent with no approval prompt - Back up
LEON_CONNECTIONS_ENCRYPTION_KEYfrom the profile.env. Without it the stored connections cannot be read
NanoClaw
- Install with
git cloneandbash nanoclaw.sh. There is no registry package, and setup needs Docker, Node 22 or later and a Claude or Codex credential - Set
NANOCLAW_EGRESS_LOCKDOWN=truebefore giving an agent credentials or an audience of strangers. The default leaves egress open - Put chats with different audiences in separate agent groups. Every session of a group shares one read-write workspace and memory tree
- Turn on per-request approval for a secret in the gateway when its use should wait for a person. It is off unless configured
- On OneCLI installs, move the gateway to 1.42.0 by the upgrade guide before updating to 2026.10.0. The updater stops until that is done
Questions
Which is better for AI agents, Leon or NanoClaw?
NanoClaw scores 68.3 (B) on agent readiness against Leon's 41 (E), and leads in 6 of 7 scored categories.
Are Leon and NanoClaw open source?
Yes. Leon is open source (MIT). NanoClaw is open source (MIT).
Other comparisons with Leon or NanoClaw
- AstrBot vs Leon
- AstrBot vs NanoClaw
- CowAgent vs Leon
- CowAgent vs NanoClaw
- GAIA vs Leon
- GAIA vs NanoClaw
- Gemini Spark vs Leon
- Gemini Spark vs NanoClaw
- Grok Bot vs Leon
- Grok Bot vs NanoClaw
- Haven vs Leon
- Haven vs NanoClaw
- Hermes Agent vs Leon
- Hermes Agent vs NanoClaw
- Instinct vs Leon
- Instinct vs NanoClaw
- IronClaw vs Leon
- IronClaw vs NanoClaw
- Leon vs Lindy
- Leon vs nanobot
- Leon vs Dots
- Leon vs OpenClaw
- Leon vs PicoClaw
- Leon vs Poke
- Leon vs QwenPaw
- Leon vs ZeroClaw
- Leon vs Zo Computer
- Lindy vs NanoClaw
- nanobot vs NanoClaw
- NanoClaw vs Dots
- NanoClaw vs OpenClaw
- NanoClaw vs PicoClaw
- NanoClaw vs Poke
- NanoClaw vs QwenPaw
- NanoClaw vs ZeroClaw
- NanoClaw vs Zo Computer
Machine-readable
- This page as Markdown
/compare/leon-vs-nanoclaw.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/leon.json·/api/v1/tools/nanoclaw.json - From a terminal
anchor compare leon nanoclaw(the CLI) - Over MCP
compare_tools {"a": "leon", "b": "nanoclaw"}at/mcp, no key