{ "data": { "a": { "slug": "nanobot", "name": "nanobot", "vendor": "HKUDS", "vendorUrl": "https://nanobot.wiki", "kind": "harness", "category": "personal-assistants", "summary": "nanobot is an open-source, self-hosted personal AI agent written in Python by HKUDS. It runs as a gateway on the owner's machine and answers in a web UI, a terminal and chat apps, with tools, memory and scheduled automations.", "url": "https://www.anchorterminal.com/tools/nanobot", "markdownUrl": "https://www.anchorterminal.com/tools/nanobot.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nanobot.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nanobot.json", "repo": "https://github.com/HKUDS/nanobot", "license": "MIT", "transports": [], "packages": [ { "registry": "pypi", "name": "nanobot-ai" } ], "auth": "none", "authNotes": "No account with the project. The owner supplies model provider keys or an OAuth sign-in, and bot tokens or mailbox passwords for each channel, in `~/.nanobot/config.json`. The WebUI on localhost needs no password, and binding to all interfaces requires a token.", "pricing": "free", "pricingNotes": "Free under the MIT licence, with nothing to buy from the project. The owner pays the model provider, or nothing with a local model. The optional Render deployment needs a paid Render service.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs or the source (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 49000, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://nanobot.wiki/docs/latest/getting-started/nanobot-overview", "llmsTxt": "https://nanobot.wiki/llms.txt", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.memory", "assistant.self-hosted", "assistant.accounts", "agent.mcp-client" ], "tags": [ "open-source", "self-hosted", "local", "free", "python", "mit", "llms-txt", "docker", "alpha" ], "lastRelease": "2026-09-15", "graded": true, "anchor": { "graded": true, "score": 62.4, "grade": "B", "agentReady": false, "rank": 446, "ranked": true, "rankOf": 986, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 82, "payments": 60, "reliability": 70, "schema": 77, "security": 63, "transparency": 48 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": -6, "negativeNotes": [ "2026-09-02. GHSA-vc5v-6vwm-wf9m (critical, 9.3, no CVE). Web fetch did not block internal addresses, so cloud metadata and internal services could be read without authentication in versions before 0.3.0. Fixed in 0.3.0 of 25 July and published, -2. https://github.com/HKUDS/nanobot/security/advisories/GHSA-vc5v-6vwm-wf9m", "2026-03-27. GHSA-4gmr-2vc8-7qh3 (CVE-2026-33654, high). A spoofed email could inject instructions through email polling with no user action, up to command execution, in 0.1.4.post5 and earlier. Fixed in 0.1.4.post6 and published, more than six months ago, -2. https://github.com/HKUDS/nanobot/security/advisories/GHSA-4gmr-2vc8-7qh3", "2026-03-11. GHSA-g6cf-xjwr-pm77 (CVE-2026-31977, critical, 9.0). A sender ID containing `|` passed the `allowFrom` check in versions before 0.1.4.post4. Fixed and published, more than six months ago, -1. https://github.com/HKUDS/nanobot/security/advisories/GHSA-g6cf-xjwr-pm77", "2026-04-14 and 2026-05-24. GHSA-v5j3-4q66-58cf (CVE-2026-35589, high, 8.0), cross-site WebSocket hijacking of the WhatsApp bridge, fixed in 0.1.5, and GHSA-3f63-vcp3-hvqr (CVE-2026-48716, high, 8.7), file write through a WhatsApp document name. Both fixed and published, -1 together. https://github.com/HKUDS/nanobot/security/advisories" ], "verdict": "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.", "bestFor": "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.", "strengths": [ "MIT licence, runs on the owner's machine, and no telemetry code was found in the source at v0.3.5", "Long-term memory is plain files (`USER.md`, `SOUL.md`, `memory/MEMORY.md`) versioned with Git, with `/dream-log` and `/dream-restore` to inspect and roll back", "Chat channels deny unknown senders by default since v0.1.4.post4, with pairing codes the owner approves", "Email requires SPF and DKIM results from a named receiving service since v0.3.5, and mailbox access stays off until `consentGranted` is set", "Optional `bwrap` (Linux) and `seatbelt` (macOS) sandboxes for shell commands, and an SSRF guard on web fetches and HTTP MCP connections" ], "weaknesses": [ "No per-action approval was found in the docs or source. The agent sends messages, runs shell commands and edits files without asking", "`tools.restrictToWorkspace` defaults to false and `tools.exec.sandbox` to empty. Neither sandbox restricts network access, and Windows has none", "Five advisories published from 11 March to 2 September 2026, two rated critical, among them an allowlist bypass and unauthenticated SSRF in web fetch", "SECURITY.md lists plain-text API keys in `config.json`, no rate limiting and limited security event logging as known limitations", "Version 0.3.5 with an Alpha classifier, 214 open issues and 614 open pull requests on 12 October 2026" ], "agentNotes": [ "Set `tools.restrictToWorkspace` to true and `tools.exec.sandbox` to `bwrap` or `seatbelt` before 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 `allowFrom` narrow 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 keep `nanobot gateway` running for channels, schedules and heartbeat" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.4 } ], "editorialScores": { "ergonomics": 74, "maintenance": 82, "payments": 60, "reliability": 70, "schema": 77, "security": 63, "transparency": 69 }, "provenanceScore": 27 }, "connect": { "install": "python -m pip install nanobot-ai # or: uv tool install nanobot-ai # then: nanobot webui", "headless": { "command": "nanobot -m \"$TASK\"" } }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/nanobot" }, "area": "frameworks", "provenance": { "legalEntity": "", "domain": "nanobot.wiki", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/HKUDS/nanobot/releases", "securityTxt": "none", "checked": "2026-10-12", "notes": [ "No legal entity is named. The repository belongs to the GitHub organisation HKUDS, which a published advisory title calls the Hong Kong University Data Intelligence Lab. pyproject.toml names Xubin Ren and the nanobot contributors as authors.", "nanobot.wiki has no terms or privacy page linked from its home page or llms.txt, and `/.well-known/security.txt` answered with the site's not-found page on 12 October 2026.", "SECURITY.md in the repository asks for reports through a private GitHub advisory or by email and aims to respond within 48 hours.", "There is no hosted endpoint. A gateway answers on its owner's own host." ], "score": 27 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nanobot.json" }, "answer": "nanobot scores 62.4 (B) on agent readiness against PicoClaw's 46.1 (D), and leads in 5 of 7 scored categories. PicoClaw leads on transparency \u0026 trust.", "b": { "slug": "picoclaw", "name": "PicoClaw", "vendor": "Sipeed", "vendorUrl": "https://picoclaw.io", "kind": "harness", "category": "personal-assistants", "summary": "PicoClaw is an open-source personal AI assistant from Sipeed, a single Go binary for small Linux boards, desktops and Android, reached through chat apps. Its last commit on the main branch was on 19 August 2026.", "url": "https://www.anchorterminal.com/tools/picoclaw", "markdownUrl": "https://www.anchorterminal.com/tools/picoclaw.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/picoclaw.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/picoclaw.json", "repo": "https://github.com/sipeed/picoclaw", "license": "MIT", "transports": [], "packages": [ { "registry": "oci", "name": "docker.io/sipeed/picoclaw" }, { "registry": "oci", "name": "ghcr.io/sipeed/picoclaw" } ], "auth": "none", "authNotes": "No account with Sipeed. The owner supplies model provider keys, chat bot tokens and search keys, kept in `~/.picoclaw/.security.yml`. The web launcher asks for a password set on first run, stored as a bcrypt hash. Each channel's `allow_from` list decides who may talk to the assistant, and an empty list admits everyone.", "pricing": "free", "pricingNotes": "Free under the MIT licence, with nothing to buy from the project. The owner pays their model provider by usage, or nothing with a local model through Ollama or vLLM. Search keys are optional, and DuckDuckGo search needs none.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, docs or source (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 30000, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://docs.picoclaw.io", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.memory", "assistant.self-hosted", "agent.mcp-client" ], "tags": [ "open-source", "self-hosted", "local", "free", "no-card", "go", "docker", "pre-1.0" ], "lastRelease": "2026-07-03", "graded": true, "anchor": { "graded": true, "score": 46.1, "grade": "D", "agentReady": false, "rank": 879, "ranked": true, "rankOf": 986, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 22, "payments": 60, "reliability": 54, "schema": 51, "security": 51, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": -7, "negativeNotes": [ "2026-04-25 to 2026-07-19. 15 advisories are listed for PicoClaw in the GitHub Advisory Database. Two are reviewed, CVE-2026-36045 (high, 7.3, command injection past the exec deny list, 0.1.2 and earlier) and CVE-2026-6987 (moderate, injection through the launcher's `/api/gateway/restart`, 0.2.4 and earlier), and 13 unreviewed entries of 10 to 19 July name versions up to 0.2.9. None lists a patched version, the project has published no advisory of its own, and it has no security policy. We read four of the fifteen. Several concern old versions and some fixes are in the git history, so -5. https://github.com/advisories?query=picoclaw", "Current behaviour, checked 2026-10-12. The repository's configuration guide says `tools.exec.allow_remote` defaults to `false`. The source at v0.3.1 and on main sets it to `true`, and the docs site calls fully open the default, so a remote chat can run shell commands on a default install. A misleading claim on a security default, the minimum, -2. https://github.com/sipeed/picoclaw/blob/main/docs/guides/configuration.md; https://github.com/sipeed/picoclaw/blob/main/pkg/config/defaults.go" ], "verdict": "Self-hosted under the MIT licence, with 19 documented chat channels, scheduled and heartbeat tasks, and local file memory. The repository has had no commit since 19 August 2026 and no release since 3 July, and 15 CVEs are listed against it with no advisory or security policy from the project.", "bestFor": "A person who wants a chat-app assistant on a cheap Linux board, an old Android phone or a home server, with reminders, web search and file memory, and who accepts running software its maker calls pre-production.", "strengths": [ "MIT licence, one Go binary for x86-64, ARM, RISC-V, MIPS and LoongArch, with Docker images and an Android APK", "Conversations, memory, scheduled jobs and credentials stay in files under `~/.picoclaw` on the owner's device", "File tools are limited to the workspace by default, and command jobs scheduled from remote chats are refused unless the chat is listed", "MCP client over stdio, SSE and HTTP, with optional search-based tool discovery to keep definitions out of context", "Credentials sit in a separate `.security.yml` with optional AES-256-GCM encryption, and are filtered from tool output before the model sees it" ], "weaknesses": [ "No commit on main since 19 August 2026 and no release since v0.3.1 on 3 July 2026. An issue of 6 October calls the repository unmaintained, with no reply", "15 CVEs are listed in the GitHub Advisory Database (25 April to 19 July 2026). The project has published no advisory and has no SECURITY.md", "No human approval step. The agent sends messages, writes files and runs shell commands without asking, and the hooks guide says waiting for a human reply is not supported", "Shell execution from remote chats is on by default in the source and on the docs site, while the repository's configuration guide says the default is off", "An empty `allow_from` list lets anyone who can message the bot use it, with only a warning in the log" ], "agentNotes": [ "Set `allow_from` to the owner's user ID on every channel before starting the gateway. An empty list accepts messages from anyone", "Set `tools.exec.allow_remote` to `false` unless chats must run shell commands. The shipped default is `true`, whatever docs/guides/configuration.md says", "Set `isolation.enabled` to `true` on Linux (needs `bwrap`) or run in a container. The deny patterns do not inspect child processes", "Use `PICOCLAW_KEY_PASSPHRASE` for credential encryption. One docs page names `PICOCLAW_CREDENTIAL_PASSPHRASE`, which the source does not read", "Treat the README's ClawdChat line (read a remote skill file and follow it) as untrusted third-party instructions" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 46.1 } ], "editorialScores": { "ergonomics": 66, "maintenance": 22, "payments": 60, "reliability": 54, "schema": 51, "security": 51, "transparency": 58 }, "provenanceScore": 53 }, "connect": { "install": "git clone https://github.com/sipeed/picoclaw.git \u0026\u0026 cd picoclaw \u0026\u0026 docker compose -f docker/docker-compose.yml --profile launcher up # or download a binary from https://picoclaw.io/download/ and run: picoclaw onboard", "headless": { "command": "picoclaw agent -m \"$TASK\"" } }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/picoclaw" }, "area": "frameworks", "provenance": { "legalEntity": "Sipeed", "domain": "picoclaw.io", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/sipeed/picoclaw/releases", "securityTxt": "none", "checked": "2026-10-12", "notes": [ "The docs footer reads Copyright 2026 Sipeed and the site says PicoClaw is open-source software by Sipeed. The `LICENSE` file names PicoClaw contributors. No registered company name or address was on the pages read.", "No terms of service or privacy policy is linked from picoclaw.io, docs.picoclaw.io or the repository, so both fields are left out and the MIT licence stands in.", "picoclaw.io/.well-known/security.txt and picoclaw.io/llms.txt answered 403 with a storage Access Denied body, read as absent. docs.picoclaw.io/llms.txt answered 404.", "The repository has no SECURITY.md, and GitHub's policy page says none is set up.", "Self-hosted software with no hosted endpoint. The registration date of picoclaw.io was not looked up." ], "score": 53 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/picoclaw.json" }, "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "HKUDS", "b": "Sipeed", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "None", "b": "None", "name": "Auth" }, { "a": "Free", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-09-15", "b": "2026-07-03", "name": "Last release" }, { "a": "no document linked", "b": "no document linked", "name": "Terms last updated" }, { "a": "no document linked", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "", "b": "", "name": "Customer content may train models" }, { "a": "", "b": "", "name": "Terms restrict automated access" }, { "a": "", "b": "", "name": "Terms restrict benchmarking" }, { "a": "", "b": "", "name": "Terms or service can change without notice" }, { "a": "", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "49k stars", "b": "30k stars", "name": "Popularity" } ], "faq": [ { "answer": "nanobot scores 62.4 (B) on agent readiness against PicoClaw's 46.1 (D), and leads in 5 of 7 scored categories. PicoClaw leads on transparency \u0026 trust.", "question": "Which is better for AI agents, nanobot or PicoClaw?" }, { "answer": "Yes. nanobot is open source (MIT). PicoClaw is open source (MIT).", "question": "Are nanobot and PicoClaw open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 54", "Schema \u0026 documentation, 77 against 51", "Agent ergonomics, 74 against 66", "Security \u0026 auth, 63 against 51", "Maintenance \u0026 community, 82 against 22" ], "also": null, "goodFor": "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.", "slug": "nanobot", "watchFor": "No per-action approval was found in the docs or source. The agent sends messages, runs shell commands and edits files without asking" }, { "aheadOn": [ "Transparency \u0026 trust, 56 against 48" ], "also": [ "Free to start without a card" ], "goodFor": "A person who wants a chat-app assistant on a cheap Linux board, an old Android phone or a home server, with reminders, web search and file memory, and who accepts running software its maker calls pre-production.", "slug": "picoclaw", "watchFor": "No commit on main since 19 August 2026 and no release since v0.3.1 on 3 July 2026. An issue of 6 October calls the repository unmaintained, with no reply" } ], "job": { "capability": "assistant.proactive", "name": "Assistant proactive" }, "others": [ { "json": "https://www.anchorterminal.com/compare/astrbot-vs-nanobot.json", "title": "AstrBot vs nanobot", "url": "https://www.anchorterminal.com/compare/astrbot-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/astrbot-vs-picoclaw.json", "title": "AstrBot vs PicoClaw", "url": "https://www.anchorterminal.com/compare/astrbot-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/cowagent-vs-nanobot.json", "title": "CowAgent vs nanobot", "url": "https://www.anchorterminal.com/compare/cowagent-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/cowagent-vs-picoclaw.json", "title": "CowAgent vs PicoClaw", "url": "https://www.anchorterminal.com/compare/cowagent-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/gaia-vs-nanobot.json", "title": "GAIA vs nanobot", "url": "https://www.anchorterminal.com/compare/gaia-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/gaia-vs-picoclaw.json", "title": "GAIA vs PicoClaw", "url": "https://www.anchorterminal.com/compare/gaia-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/gemini-spark-vs-nanobot.json", "title": "Gemini Spark vs nanobot", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/gemini-spark-vs-picoclaw.json", "title": "Gemini Spark vs PicoClaw", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-nanobot.json", "title": "Grok Bot vs nanobot", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.json", "title": "Grok Bot vs PicoClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-nanobot.json", "title": "Haven vs nanobot", "url": "https://www.anchorterminal.com/compare/haven-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-picoclaw.json", "title": "Haven vs PicoClaw", "url": "https://www.anchorterminal.com/compare/haven-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-nanobot.json", "title": "Hermes Agent vs nanobot", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-picoclaw.json", "title": "Hermes Agent vs PicoClaw", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/instinct-vs-nanobot.json", "title": "Instinct vs nanobot", "url": "https://www.anchorterminal.com/compare/instinct-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/instinct-vs-picoclaw.json", "title": "Instinct vs PicoClaw", "url": "https://www.anchorterminal.com/compare/instinct-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-nanobot.json", "title": "IronClaw vs nanobot", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-picoclaw.json", "title": "IronClaw vs PicoClaw", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/leon-vs-nanobot.json", "title": "Leon vs nanobot", "url": "https://www.anchorterminal.com/compare/leon-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/leon-vs-picoclaw.json", "title": "Leon vs PicoClaw", "url": "https://www.anchorterminal.com/compare/leon-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-nanobot.json", "title": "Lindy vs nanobot", "url": "https://www.anchorterminal.com/compare/lindy-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-picoclaw.json", "title": "Lindy vs PicoClaw", "url": "https://www.anchorterminal.com/compare/lindy-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/nanobot-vs-nanoclaw.json", "title": "nanobot vs NanoClaw", "url": "https://www.anchorterminal.com/compare/nanobot-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/nanobot-vs-openai-dots.json", "title": "nanobot vs Dots", "url": "https://www.anchorterminal.com/compare/nanobot-vs-openai-dots" }, { "json": "https://www.anchorterminal.com/compare/nanobot-vs-openclaw.json", "title": "nanobot vs OpenClaw", "url": "https://www.anchorterminal.com/compare/nanobot-vs-openclaw" }, { "json": "https://www.anchorterminal.com/compare/nanobot-vs-poke.json", "title": "nanobot vs Poke", "url": "https://www.anchorterminal.com/compare/nanobot-vs-poke" }, { "json": "https://www.anchorterminal.com/compare/nanobot-vs-qwenpaw.json", "title": "nanobot vs QwenPaw", "url": "https://www.anchorterminal.com/compare/nanobot-vs-qwenpaw" }, { "json": "https://www.anchorterminal.com/compare/nanobot-vs-zeroclaw.json", "title": "nanobot vs ZeroClaw", "url": "https://www.anchorterminal.com/compare/nanobot-vs-zeroclaw" }, { "json": "https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.json", "title": "nanobot vs Zo Computer", "url": "https://www.anchorterminal.com/compare/nanobot-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/nanoclaw-vs-picoclaw.json", "title": "NanoClaw vs PicoClaw", "url": "https://www.anchorterminal.com/compare/nanoclaw-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/openai-dots-vs-picoclaw.json", "title": "Dots vs PicoClaw", "url": "https://www.anchorterminal.com/compare/openai-dots-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/openclaw-vs-picoclaw.json", "title": "OpenClaw vs PicoClaw", "url": "https://www.anchorterminal.com/compare/openclaw-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/picoclaw-vs-poke.json", "title": "PicoClaw vs Poke", "url": "https://www.anchorterminal.com/compare/picoclaw-vs-poke" }, { "json": "https://www.anchorterminal.com/compare/picoclaw-vs-qwenpaw.json", "title": "PicoClaw vs QwenPaw", "url": "https://www.anchorterminal.com/compare/picoclaw-vs-qwenpaw" }, { "json": "https://www.anchorterminal.com/compare/picoclaw-vs-zeroclaw.json", "title": "PicoClaw vs ZeroClaw", "url": "https://www.anchorterminal.com/compare/picoclaw-vs-zeroclaw" }, { "json": "https://www.anchorterminal.com/compare/picoclaw-vs-zo-computer.json", "title": "PicoClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/picoclaw-vs-zo-computer" } ], "scores": [ { "by": 16, "edge": "nanobot", "key": "reliability", "name": "Reliability", "nanobot": 70, "picoclaw": 54, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 26, "edge": "nanobot", "key": "schema", "name": "Schema \u0026 documentation", "nanobot": 77, "picoclaw": 51, "weight": 13 }, { "by": 8, "edge": "nanobot", "key": "ergonomics", "name": "Agent ergonomics", "nanobot": 74, "picoclaw": 66, "weight": 13 }, { "by": 12, "edge": "nanobot", "key": "security", "name": "Security \u0026 auth", "nanobot": 63, "picoclaw": 51, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "nanobot": 60, "picoclaw": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 60, "edge": "nanobot", "key": "maintenance", "name": "Maintenance \u0026 community", "nanobot": 82, "picoclaw": 22, "weight": 7 }, { "by": 8, "edge": "picoclaw", "key": "transparency", "name": "Transparency \u0026 trust", "nanobot": 48, "picoclaw": 56, "weight": 7 } ], "summary": "nanobot scores 62.4 (B) on agent readiness against PicoClaw's 46.1 (D), and leads in 5 of 7 scored categories. PicoClaw leads on transparency \u0026 trust. Both do assistant proactive.", "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.", "picoclaw": "Self-hosted under the MIT licence, with 19 documented chat channels, scheduled and heartbeat tasks, and local file memory. The repository has had no commit since 19 August 2026 and no release since 3 July, and 15 CVEs are listed against it with no advisory or security policy from the project." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/nanobot-vs-picoclaw", "json": "https://www.anchorterminal.com/compare/nanobot-vs-picoclaw.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/nanobot-vs-picoclaw.md", "slim": "https://www.anchorterminal.com/compare/nanobot-vs-picoclaw.min.md" }, "markdown": "nanobot scores 62.4 (B) on agent readiness against PicoClaw's 46.1 (D), and leads in 5 of 7 scored categories. PicoClaw leads on transparency \u0026 trust. Both do assistant proactive.\n\n- nanobot: grade B, 62.4/100, rank #446 of 986. Markdown https://www.anchorterminal.com/tools/nanobot.md · JSON https://www.anchorterminal.com/api/v1/tools/nanobot.json\n- PicoClaw: grade D, 46.1/100, rank #879 of 986. Markdown https://www.anchorterminal.com/tools/picoclaw.md · JSON https://www.anchorterminal.com/api/v1/tools/picoclaw.json\n- Best AI personal assistants that act for one person: https://www.anchorterminal.com/best/personal-assistants/index.md\n- All 190 assistants comparisons: https://www.anchorterminal.com/compare/personal-assistants/index.md\n\n## Which one, for what\n\n### nanobot (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 70 against 54\n- Schema \u0026 documentation, 77 against 51\n- Agent ergonomics, 74 against 66\n- Security \u0026 auth, 63 against 51\n- Maintenance \u0026 community, 82 against 22\n\nWatch for: No per-action approval was found in the docs or source. The agent sends messages, runs shell commands and edits files without asking\n\n### PicoClaw (D)\n\nGood for: A person who wants a chat-app assistant on a cheap Linux board, an old Android phone or a home server, with reminders, web search and file memory, and who accepts running software its maker calls pre-production.\n\nAhead on:\n- Transparency \u0026 trust, 56 against 48\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No commit on main since 19 August 2026 and no release since v0.3.1 on 3 July 2026. An issue of 6 October calls the repository unmaintained, with no reply\n\n\n## Score by category\n\n| Category | Weight | nanobot | PicoClaw | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 54 | nanobot +16 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 51 | nanobot +26 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 66 | nanobot +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 51 | nanobot +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 60 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 82 | 22 | nanobot +60 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 56 | PicoClaw +8 |\n| Negative events | ≤15 | -6 | -7 | |\n| **Total** | | **62.4 · B** | **46.1 · D** | |\n\n## Facts side by side\n\n| Fact | nanobot | PicoClaw |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | HKUDS | Sipeed |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | None | None |\n| Pricing | Free | Free |\n| x402 | no | no |\n| Licence | MIT | MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-09-15 | 2026-07-03 |\n| Terms last updated | no document linked | no document linked |\n| Privacy policy last updated | no document linked | no document linked |\n| Customer content may train models | | |\n| Terms restrict automated access | | |\n| Terms restrict benchmarking | | |\n| Terms or service can change without notice | | |\n| Arbitration or class-action waiver | | |\n| Popularity | 49k stars | 30k stars |\n\n## Verdicts\n\n**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.\n\n**PicoClaw.** Self-hosted under the MIT licence, with 19 documented chat channels, scheduled and heartbeat tasks, and local file memory. The repository has had no commit since 19 August 2026 and no release since 3 July, and 15 CVEs are listed against it with no advisory or security policy from the project.\n\n## Before you call either\n\n### nanobot\n\n1. Set `tools.restrictToWorkspace` to true and `tools.exec.sandbox` to `bwrap` or `seatbelt` before giving it real accounts. Both are off by default\n2. Run 0.3.0 or later. Earlier versions carry the published SSRF flaw in web fetch (GHSA-vc5v-6vwm-wf9m)\n3. Keep `allowFrom` narrow on every channel and never set `[\"*\"]` on Email, which has no pairing\n4. Write secrets as `${VAR}` references in `~/.nanobot/config.json`. Plain values are stored in clear text\n5. Use `nanobot -m \"...\"` for a one-shot run, and keep `nanobot gateway` running for channels, schedules and heartbeat\n\n### PicoClaw\n\n1. Set `allow_from` to the owner's user ID on every channel before starting the gateway. An empty list accepts messages from anyone\n2. Set `tools.exec.allow_remote` to `false` unless chats must run shell commands. The shipped default is `true`, whatever docs/guides/configuration.md says\n3. Set `isolation.enabled` to `true` on Linux (needs `bwrap`) or run in a container. The deny patterns do not inspect child processes\n4. Use `PICOCLAW_KEY_PASSPHRASE` for credential encryption. One docs page names `PICOCLAW_CREDENTIAL_PASSPHRASE`, which the source does not read\n5. Treat the README's ClawdChat line (read a remote skill file and follow it) as untrusted third-party instructions\n\n## Questions\n\n### Which is better for AI agents, nanobot or PicoClaw?\n\nnanobot scores 62.4 (B) on agent readiness against PicoClaw's 46.1 (D), and leads in 5 of 7 scored categories. PicoClaw leads on transparency \u0026 trust.\n\n### Are nanobot and PicoClaw open source?\n\nYes. nanobot is open source (MIT). PicoClaw is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/nanobot-vs-picoclaw.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nanobot-vs-picoclaw.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"nanobot\", \"b\": \"picoclaw\"}`. From a terminal: `anchor compare nanobot picoclaw`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nanobot.json and https://www.anchorterminal.com/api/v1/tools/picoclaw.json\n\n## Other comparisons with nanobot or PicoClaw\n\n- [AstrBot vs nanobot](https://www.anchorterminal.com/compare/astrbot-vs-nanobot.md)\n- [AstrBot vs PicoClaw](https://www.anchorterminal.com/compare/astrbot-vs-picoclaw.md)\n- [CowAgent vs nanobot](https://www.anchorterminal.com/compare/cowagent-vs-nanobot.md)\n- [CowAgent vs PicoClaw](https://www.anchorterminal.com/compare/cowagent-vs-picoclaw.md)\n- [GAIA vs nanobot](https://www.anchorterminal.com/compare/gaia-vs-nanobot.md)\n- [GAIA vs PicoClaw](https://www.anchorterminal.com/compare/gaia-vs-picoclaw.md)\n- [Gemini Spark vs nanobot](https://www.anchorterminal.com/compare/gemini-spark-vs-nanobot.md)\n- [Gemini Spark vs PicoClaw](https://www.anchorterminal.com/compare/gemini-spark-vs-picoclaw.md)\n- [Grok Bot vs nanobot](https://www.anchorterminal.com/compare/grok-bot-vs-nanobot.md)\n- [Grok Bot vs PicoClaw](https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.md)\n- [Haven vs nanobot](https://www.anchorterminal.com/compare/haven-vs-nanobot.md)\n- [Haven vs PicoClaw](https://www.anchorterminal.com/compare/haven-vs-picoclaw.md)\n- [Hermes Agent vs nanobot](https://www.anchorterminal.com/compare/hermes-agent-vs-nanobot.md)\n- [Hermes Agent vs PicoClaw](https://www.anchorterminal.com/compare/hermes-agent-vs-picoclaw.md)\n- [Instinct vs nanobot](https://www.anchorterminal.com/compare/instinct-vs-nanobot.md)\n- [Instinct vs PicoClaw](https://www.anchorterminal.com/compare/instinct-vs-picoclaw.md)\n- [IronClaw vs nanobot](https://www.anchorterminal.com/compare/ironclaw-vs-nanobot.md)\n- [IronClaw vs PicoClaw](https://www.anchorterminal.com/compare/ironclaw-vs-picoclaw.md)\n- [Leon vs nanobot](https://www.anchorterminal.com/compare/leon-vs-nanobot.md)\n- [Leon vs PicoClaw](https://www.anchorterminal.com/compare/leon-vs-picoclaw.md)\n- [Lindy vs nanobot](https://www.anchorterminal.com/compare/lindy-vs-nanobot.md)\n- [Lindy vs PicoClaw](https://www.anchorterminal.com/compare/lindy-vs-picoclaw.md)\n- [nanobot vs NanoClaw](https://www.anchorterminal.com/compare/nanobot-vs-nanoclaw.md)\n- [nanobot vs Dots](https://www.anchorterminal.com/compare/nanobot-vs-openai-dots.md)\n- [nanobot vs OpenClaw](https://www.anchorterminal.com/compare/nanobot-vs-openclaw.md)\n- [nanobot vs Poke](https://www.anchorterminal.com/compare/nanobot-vs-poke.md)\n- [nanobot vs QwenPaw](https://www.anchorterminal.com/compare/nanobot-vs-qwenpaw.md)\n- [nanobot vs ZeroClaw](https://www.anchorterminal.com/compare/nanobot-vs-zeroclaw.md)\n- [nanobot vs Zo Computer](https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.md)\n- [NanoClaw vs PicoClaw](https://www.anchorterminal.com/compare/nanoclaw-vs-picoclaw.md)\n- [Dots vs PicoClaw](https://www.anchorterminal.com/compare/openai-dots-vs-picoclaw.md)\n- [OpenClaw vs PicoClaw](https://www.anchorterminal.com/compare/openclaw-vs-picoclaw.md)\n- [PicoClaw vs Poke](https://www.anchorterminal.com/compare/picoclaw-vs-poke.md)\n- [PicoClaw vs QwenPaw](https://www.anchorterminal.com/compare/picoclaw-vs-qwenpaw.md)\n- [PicoClaw vs ZeroClaw](https://www.anchorterminal.com/compare/picoclaw-vs-zeroclaw.md)\n- [PicoClaw vs Zo Computer](https://www.anchorterminal.com/compare/picoclaw-vs-zo-computer.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-12", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "nanobot vs PicoClaw", "url": "" } ], "description": "nanobot scores 62.4 (B) to PicoClaw's 46.1 (D) for assistant proactive. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "nanobot B 62.4", "PicoClaw D 46.1", "scores" ], "h1": "nanobot vs PicoClaw", "image": "https://www.anchorterminal.com/assets/og/compare-nanobot-vs-picoclaw.png", "path": "/compare/nanobot-vs-picoclaw", "published": "2026-10-01", "section": "tools", "title": "nanobot vs PicoClaw for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/nanobot-vs-picoclaw" }, "tokens": { "markdown": 2550, "slim": 530 }, "version": 1 }