Head to head · Assistants that remember you · October 2026 research run
nanobot vs Talorys
nanobot scores 62.4 (B) on agent readiness against Talorys's 28.9 (F), and leads in 4 of 7 scored categories. Both do assistants that remember you.
Best AI personal assistants that act for one person · All 314 assistants comparisons
Which one, for what
nanobot B
Best for A technical owner who wants an assistant on their own machine across many chat apps, with file-based memory and a free choice of model.
Ahead on
- Reliability, 70 against 41
- Schema & documentation, 77 against 0
- Agent ergonomics, 74 against 0
- Security & auth, 63 against 8
Also in its favour
- No key needed to call it
Watch for
No per-action approval was found in the docs or source. The agent sends messages, runs shell commands and edits files without asking
Talorys F
Best for A single person who wants a private assistant for memory, tasks, notes and reminders on their own Cloudflare account.
Also in its favour
- No incidents deducted, where nanobot loses 6 points for them
Watch for
No API key, MCP server or A2A endpoint, and the /api routes need the owner's browser session.
Score by category
| Category | Weight this run | nanobot | Talorys | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 41 | nanobot +29 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 77 | 0 | nanobot +77 |
| Agent ergonomics | 13%16.2 | 74 | 0 | nanobot +74 |
| Security & auth | 14%17.5 | 63 | 8 | nanobot +55 |
| Payments & pricing | 10%12.5 | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 82 | 83 | Talorys +1 |
| Transparency & trust | 7%8.8 | 48 | 52 | Talorys +4 |
| Negative events | ≤15 | -6 | 0 | |
| Total | B 62.4/100 | F 28.9/100 |
Facts side by side
| Fact | nanobot | Talorys |
|---|---|---|
| Kind | Agent harness | Platform |
| Vendor | HKUDS | Roc Yu (rociiu) and contributors |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | OAuth or key |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | MIT | MIT (Copyright 2026 The Talorys contributors). It runs on the owner's Cloudflare account under Cloudflare's own terms. |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-09-15 | 2026-10-12 |
| 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 | 49k stars | 978 npm/wk |
Verdicts
nanobot
nanobot runs on the owner's machine under the MIT licence, with no telemetry found in its source and memory kept as files the owner can read and restore. No per-action approval step was found, and the shell sandbox and workspace restriction are off by default. Five security advisories were published between March and September 2026, all with fixes.
Talorys
Talorys is an MIT-licensed assistant its owner deploys to their own Cloudflare account, with no telemetry, a documented threat model and code-enforced confirmation for destructive tools. It is two days old at version 0.1.5, has no mail, calendar or payment connections, and no interface for an outside agent.
Before you call either
nanobot
- Set
tools.restrictToWorkspaceto true andtools.exec.sandboxtobwraporseatbeltbefore giving it real accounts. Both are off by default - Run 0.3.0 or later. Earlier versions carry the published SSRF flaw in web fetch (GHSA-vc5v-6vwm-wf9m)
- Keep
allowFromnarrow on every channel and never set["*"]on Email, which has no pairing - Write secrets as
${VAR}references in~/.nanobot/config.json. Plain values are stored in clear text - Use
nanobot -m "..."for a one-shot run, and keepnanobot gatewayrunning for channels, schedules and heartbeat
Talorys
- Run
npx create-talorys@latestwith Node.js 22 or later and a Cloudflare login or an API token with Workers, Pages and Workers AI permissions. - Don't script the /api routes. They need the owner's session cookie and CSRF header and aren't documented for other callers.
- Update with
npx create-talorys@latest update. Only the latest version gets security fixes.
Questions
Which is better for AI agents, nanobot or Talorys?
nanobot scores 62.4 (B) on agent readiness against Talorys's 28.9 (F), and leads in 4 of 7 scored categories.
Are nanobot and Talorys open source?
Yes. nanobot is open source (MIT). Talorys is open source (MIT (Copyright 2026 The Talorys contributors). It runs on the owner's Cloudflare account under Cloudflare's own terms.).
Other comparisons with nanobot or Talorys
- AstrBot vs nanobot
- CowAgent vs nanobot
- GAIA vs nanobot
- Gemini Spark vs nanobot
- Grok Bot vs nanobot
- Haven vs nanobot
- Hermes Agent vs nanobot
- Instinct vs nanobot
- IronClaw vs nanobot
- Leon vs nanobot
- Lindy vs nanobot
- nanobot vs NanoClaw
- nanobot vs Dots
- nanobot vs OpenClaw
- nanobot vs PicoClaw
- nanobot vs Poke
- nanobot vs QwenPaw
- nanobot vs ZeroClaw
- nanobot vs Zo Computer
- nanobot vs Natura tinyNature
- nanobot vs Pally
- nanobot vs Tomo
- nanobot vs Wajo (Fo)
- CowAgent vs Talorys
- GAIA vs Talorys
- Gemini Spark vs Talorys
- Grok Bot vs Talorys
- Haven vs Talorys
- Hermes Agent vs Talorys
- Instinct vs Talorys
- IronClaw vs Talorys
- Leon vs Talorys
- Lindy vs Talorys
- NanoClaw vs Talorys
- Natura tinyNature vs Talorys
- Dots vs Talorys
- OpenClaw vs Talorys
- Pally vs Talorys
- PicoClaw vs Talorys
- Poke vs Talorys
- QwenPaw vs Talorys
- Talorys vs Tomo
- Talorys vs Wajo (Fo)
- Talorys vs ZeroClaw
- Talorys vs Zo Computer
- AstrBot vs Talorys
Disclosure
Talorys 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
- This page as Markdown
/compare/nanobot-vs-talorys.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/nanobot.json·/api/v1/tools/talorys.json - From a terminal
anchor compare nanobot talorys(the CLI) - Over MCP
compare_tools {"a": "nanobot", "b": "talorys"}at/mcp, no key