{ "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 Zo Computer's 43.1 (E), and leads in 6 of 7 scored categories. Zo Computer leads on transparency \u0026 trust.", "b": { "slug": "zo-computer", "name": "Zo Computer", "vendor": "Zo Computer Company", "vendorUrl": "https://www.zo.computer", "kind": "http-api", "category": "personal-assistants", "summary": "Hosted personal assistant from Zo Computer Company that runs on a cloud Linux computer assigned to each user. It answers by web chat, SMS, email, Slack, Discord and Telegram, runs scheduled automations, and has an HTTP API and MCP endpoint.", "url": "https://www.anchorterminal.com/tools/zo-computer", "markdownUrl": "https://www.anchorterminal.com/tools/zo-computer.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zo-computer.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zo-computer.json", "license": "Proprietary service under Zo Computer Company's terms of service", "transports": [ "http" ], "remoteUrl": "https://api.zo.computer/mcp", "packages": [], "auth": "api-key", "authNotes": "A bearer access token with the prefix `zo_sk_`, created by the owner under Settings \u003e Advanced and shown once. The same token is used for the HTTP API and the MCP endpoint, and both guides say it grants full access to the workspace. No scoped, read-only or expiring token and no OAuth flow for outside clients were found in the docs. Whether a token can be revoked individually is not stated on the pages read. `GET /models/catalog` needs no authentication. Sign-up is in a browser behind Cloudflare Turnstile.", "pricing": "freemium", "pricingNotes": "Free Trial is $0 for 14 days with no card, then ordinary computer access ends. Basic is $18 a month with $10 of AI credit, Pro $64 with $40 and Ultra $200 with $100. API and MCP access are included on all plans. Chat is billed at per-token rates on the models pages, which we did not read, and media at fixed per-request prices from $0.035. A user's own model API key can replace Zo-billed usage (checked 2026-10-12).", "priceSummary": "$18 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API guide, the OpenAPI file, the billing guide or the pricing page, checked 12 October 2026. Billing is a Stripe subscription with prepaid credits.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://www.zo.computer/guide", "llmsTxt": "https://www.zo.computer/llms.txt", "openapi": "https://www.zo.computer/docs-assets/openapi.json", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory", "agent.mcp-client" ], "tags": [ "official", "hosted", "closed-source", "assistant", "mcp", "openapi", "llms-txt", "free-trial" ], "lastRelease": "2026-09-14", "graded": true, "anchor": { "graded": true, "score": 43.1, "grade": "E", "agentReady": false, "rank": 911, "ranked": true, "rankOf": 986, "categoryRank": 13, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 34, "maintenance": 68, "payments": 40, "reliability": 15, "schema": 73, "security": 37, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": 0, "verdict": "Zo publishes an OpenAPI file, Markdown docs, plan prices and a named list of the providers that receive user content. One access token grants full access to the workspace, no approval step before sending or buying was found in the reviewed docs, and no status page, rate limit or SLA is published.", "bestFor": "One person who wants a hosted assistant with its own Linux machine, reachable by text message and chat apps, and who accepts that the assistant acts on connected accounts without a documented approval step.", "strengths": [ "OpenAPI 3.1 file, llms.txt and a Markdown copy of every guide and reference page are public", "Persona permissions remove tools from a conversation, with 19 named scopes and a Read only preset", "The security page names each infrastructure, inference and tool provider and states which can see user content", "Plan prices, included AI credit and per-request media prices are public, with a 14-day trial that needs no card", "Dated weekly changelog, with nine weekly entries between 20 July and 14 September 2026" ], "weaknesses": [ "The access token for the API and MCP endpoint grants full access to the workspace, with no scoped or read-only token documented", "No approval step before sending mail, posting or buying was found. The browser guide says Zo can buy and send on signed-in sites", "No status page, incident history, rate limit figures or SLA were found on the pages read", "The privacy policy lists only email address, trackers, usage data and SMS data, and does not describe workspace files, memory or connected accounts", "Memory storage and deletion are not documented beyond a design aim and whole-account deletion or factory reset" ], "agentNotes": [ "Send `POST https://api.zo.computer/zo/ask` with `Authorization: Bearer zo_sk_...` and an `input` string. The owner creates the token under Settings \u003e Advanced", "Pass `persona_id` for a persona with a narrow tool set. The token itself carries every permission the owner has", "Set `memory_mode` to `off` to keep workspace memory out of a request. The field is in the OpenAPI file and absent from the API guide", "Do not retry `/zo/ask` blindly after a timeout. No idempotency key is documented and the request may already have sent a message", "Append `.md` to any guide or reference URL for Markdown" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.1 } ], "editorialScores": { "ergonomics": 34, "maintenance": 68, "payments": 40, "reliability": 15, "schema": 73, "security": 37, "transparency": 46 }, "provenanceScore": 73 }, "connect": { "http": "curl -X POST https://api.zo.computer/zo/ask \\\n -H \"Authorization: Bearer zo_sk_your_key_here\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"input\": \"Hello, Zo!\"}'", "claudeCode": "claude mcp add --transport http zo https://api.zo.computer/mcp --header \"Authorization: Bearer zo_sk_your_key_here\"", "config": { "mcpServers": { "zo": { "headers": { "Authorization": "Bearer zo_sk_your_key_here" }, "type": "http", "url": "https://api.zo.computer/mcp" } } } }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/zo-computer" }, "area": "frameworks", "unitPrices": [ { "item": "Basic plan", "unit": "month", "usd": 18, "note": "Includes $10 of AI credit a month." }, { "item": "Pro plan", "unit": "month", "usd": 64, "note": "Includes $40 of AI credit a month." }, { "item": "Ultra plan", "unit": "month", "usd": 200, "note": "Includes $100 of AI credit a month." } ], "provenance": { "legalEntity": "Zo Computer Company", "domain": "zo.computer", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.zo.computer/reference/information/terms", "privacy": "https://www.zo.computer/reference/information/privacy-policy", "statusPage": "", "changelog": "https://www.zo.computer/updates", "securityTxt": "valid", "checked": "2026-10-12", "notes": [ "The terms of service name Zo Computer Company at 13 Grattan St Unit 102, Brooklyn, NY 11206, under New York law. They were last updated on 8 August 2025.", "The terms refer to an Acceptable Use Policy that we did not find linked from the pages read.", "security.txt at www.zo.computer/.well-known/security.txt gives a contact, a policy link and an expiry of 8 April 2027.", "No status page is linked from the home page, the docs index, the security page or the help centre home page.", "The API and MCP endpoint are on api.zo.computer. The domain's registration date was not looked up.", "The X handle is the one the home page footer links." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zo-computer.json", "live": { "slug": "zo-computer", "probe": { "target": "https://api.zo.computer/mcp", "method": "get", "lastAt": "2026-10-12T19:01:35.563750129Z", "lastOk": true, "lastStatus": 405, "lastMs": 472, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 320, "p95ms24h": 1228, "samples24h": 18, "samples30d": 18, "days": [ { "date": "2026-10-12", "probes": 18, "ok": 18 } ] }, "updatedAt": "2026-10-12T19:01:35.563750129Z" } }, "facts": [ { "a": "Agent harness", "b": "HTTP API", "name": "Kind" }, { "a": "HKUDS", "b": "Zo Computer Company", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.zo.computer/mcp", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP", "name": "Transports" }, { "a": "None", "b": "API key", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "Proprietary service under Zo Computer Company's terms of service", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-15", "b": "2026-09-14", "name": "Last release" }, { "a": "no document linked", "b": "2025-08-08", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-05-20", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "49k stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "nanobot scores 62.4 (B) on agent readiness against Zo Computer's 43.1 (E), and leads in 6 of 7 scored categories. Zo Computer leads on transparency \u0026 trust.", "question": "Which is better for AI agents, nanobot or Zo Computer?" }, { "answer": "No hosted endpoint is listed for nanobot. Zo Computer has a hosted endpoint at https://api.zo.computer/mcp.", "question": "Can an agent call nanobot and Zo Computer without installing anything?" }, { "answer": "nanobot is open source (MIT). No open-source release is listed for Zo Computer.", "question": "Are nanobot and Zo Computer open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 15", "Agent ergonomics, 74 against 34", "Security \u0026 auth, 63 against 37", "Payments \u0026 pricing, 60 against 40", "Maintenance \u0026 community, 82 against 68" ], "also": [ "No key needed to call it", "Open source" ], "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, 60 against 48" ], "also": [ "A hosted endpoint, with nothing to install", "No incidents deducted, where nanobot loses 6 points for them" ], "goodFor": "One person who wants a hosted assistant with its own Linux machine, reachable by text message and chat apps, and who accepts that the assistant acts on connected accounts without a documented approval step.", "slug": "zo-computer", "watchFor": "The access token for the API and MCP endpoint grants full access to the workspace, with no scoped or read-only token documented" } ], "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-zo-computer.json", "title": "AstrBot vs Zo Computer", "url": "https://www.anchorterminal.com/compare/astrbot-vs-zo-computer" }, { "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-zo-computer.json", "title": "CowAgent vs Zo Computer", "url": "https://www.anchorterminal.com/compare/cowagent-vs-zo-computer" }, { "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-zo-computer.json", "title": "GAIA vs Zo Computer", "url": "https://www.anchorterminal.com/compare/gaia-vs-zo-computer" }, { "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-zo-computer.json", "title": "Gemini Spark vs Zo Computer", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-zo-computer" }, { "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-zo-computer.json", "title": "Grok Bot vs Zo Computer", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer" }, { "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-zo-computer.json", "title": "Haven vs Zo Computer", "url": "https://www.anchorterminal.com/compare/haven-vs-zo-computer" }, { "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-zo-computer.json", "title": "Hermes Agent vs Zo Computer", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-zo-computer" }, { "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-zo-computer.json", "title": "Instinct vs Zo Computer", "url": "https://www.anchorterminal.com/compare/instinct-vs-zo-computer" }, { "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-zo-computer.json", "title": "IronClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-zo-computer" }, { "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-zo-computer.json", "title": "Leon vs Zo Computer", "url": "https://www.anchorterminal.com/compare/leon-vs-zo-computer" }, { "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-zo-computer.json", "title": "Lindy vs Zo Computer", "url": "https://www.anchorterminal.com/compare/lindy-vs-zo-computer" }, { "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-picoclaw.json", "title": "nanobot vs PicoClaw", "url": "https://www.anchorterminal.com/compare/nanobot-vs-picoclaw" }, { "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/nanoclaw-vs-zo-computer.json", "title": "NanoClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/nanoclaw-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/openai-dots-vs-zo-computer.json", "title": "Dots vs Zo Computer", "url": "https://www.anchorterminal.com/compare/openai-dots-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/openclaw-vs-zo-computer.json", "title": "OpenClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/openclaw-vs-zo-computer" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/poke-vs-zo-computer.json", "title": "Poke vs Zo Computer", "url": "https://www.anchorterminal.com/compare/poke-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/qwenpaw-vs-zo-computer.json", "title": "QwenPaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/qwenpaw-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/zeroclaw-vs-zo-computer.json", "title": "ZeroClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/zeroclaw-vs-zo-computer" } ], "scores": [ { "by": 55, "edge": "nanobot", "key": "reliability", "name": "Reliability", "nanobot": 70, "weight": 16, "zo-computer": 15 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "edge": "nanobot", "key": "schema", "name": "Schema \u0026 documentation", "nanobot": 77, "weight": 13, "zo-computer": 73 }, { "by": 40, "edge": "nanobot", "key": "ergonomics", "name": "Agent ergonomics", "nanobot": 74, "weight": 13, "zo-computer": 34 }, { "by": 26, "edge": "nanobot", "key": "security", "name": "Security \u0026 auth", "nanobot": 63, "weight": 14, "zo-computer": 37 }, { "by": 20, "edge": "nanobot", "key": "payments", "name": "Payments \u0026 pricing", "nanobot": 60, "weight": 10, "zo-computer": 40 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 14, "edge": "nanobot", "key": "maintenance", "name": "Maintenance \u0026 community", "nanobot": 82, "weight": 7, "zo-computer": 68 }, { "by": 12, "edge": "zo-computer", "key": "transparency", "name": "Transparency \u0026 trust", "nanobot": 48, "weight": 7, "zo-computer": 60 } ], "summary": "nanobot scores 62.4 (B) on agent readiness against Zo Computer's 43.1 (E), and leads in 6 of 7 scored categories. Zo Computer 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.", "zo-computer": "Zo publishes an OpenAPI file, Markdown docs, plan prices and a named list of the providers that receive user content. One access token grants full access to the workspace, no approval step before sending or buying was found in the reviewed docs, and no status page, rate limit or SLA is published." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/nanobot-vs-zo-computer", "json": "https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.md", "slim": "https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.min.md" }, "markdown": "nanobot scores 62.4 (B) on agent readiness against Zo Computer's 43.1 (E), and leads in 6 of 7 scored categories. Zo Computer 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- Zo Computer: grade E, 43.1/100, rank #911 of 986. Markdown https://www.anchorterminal.com/tools/zo-computer.md · JSON https://www.anchorterminal.com/api/v1/tools/zo-computer.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 15\n- Agent ergonomics, 74 against 34\n- Security \u0026 auth, 63 against 37\n- Payments \u0026 pricing, 60 against 40\n- Maintenance \u0026 community, 82 against 68\n\nAlso in its favour:\n- No key needed to call it\n- Open source\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### Zo Computer (E)\n\nGood for: One person who wants a hosted assistant with its own Linux machine, reachable by text message and chat apps, and who accepts that the assistant acts on connected accounts without a documented approval step.\n\nAhead on:\n- Transparency \u0026 trust, 60 against 48\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where nanobot loses 6 points for them\n\nWatch for: The access token for the API and MCP endpoint grants full access to the workspace, with no scoped or read-only token documented\n\n\n## Score by category\n\n| Category | Weight | nanobot | Zo Computer | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 15 | nanobot +55 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 77 | 73 | nanobot +4 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 34 | nanobot +40 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 37 | nanobot +26 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 40 | nanobot +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 82 | 68 | nanobot +14 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 60 | Zo Computer +12 |\n| Negative events | ≤15 | -6 | 0 | |\n| **Total** | | **62.4 · B** | **43.1 · E** | |\n\n## Facts side by side\n\n| Fact | nanobot | Zo Computer |\n| --- | --- | --- |\n| Kind | Agent harness | HTTP API |\n| Vendor | HKUDS | Zo Computer Company |\n| Hosted endpoint | no (local only) | `https://api.zo.computer/mcp` |\n| Transports | | HTTP |\n| Auth | None | API key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | MIT | Proprietary service under Zo Computer Company's terms of service |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-15 | 2026-09-14 |\n| Terms last updated | no document linked | 2025-08-08 |\n| Privacy policy last updated | no document linked | 2026-05-20 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | not found in the text |\n| Popularity | 49k stars | none |\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**Zo Computer.** Zo publishes an OpenAPI file, Markdown docs, plan prices and a named list of the providers that receive user content. One access token grants full access to the workspace, no approval step before sending or buying was found in the reviewed docs, and no status page, rate limit or SLA is published.\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### Zo Computer\n\n1. Send `POST https://api.zo.computer/zo/ask` with `Authorization: Bearer zo_sk_...` and an `input` string. The owner creates the token under Settings \u003e Advanced\n2. Pass `persona_id` for a persona with a narrow tool set. The token itself carries every permission the owner has\n3. Set `memory_mode` to `off` to keep workspace memory out of a request. The field is in the OpenAPI file and absent from the API guide\n4. Do not retry `/zo/ask` blindly after a timeout. No idempotency key is documented and the request may already have sent a message\n5. Append `.md` to any guide or reference URL for Markdown\n\n## Questions\n\n### Which is better for AI agents, nanobot or Zo Computer?\n\nnanobot scores 62.4 (B) on agent readiness against Zo Computer's 43.1 (E), and leads in 6 of 7 scored categories. Zo Computer leads on transparency \u0026 trust.\n\n### Can an agent call nanobot and Zo Computer without installing anything?\n\nNo hosted endpoint is listed for nanobot. Zo Computer has a hosted endpoint at https://api.zo.computer/mcp.\n\n### Are nanobot and Zo Computer open source?\n\nnanobot is open source (MIT). No open-source release is listed for Zo Computer.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"nanobot\", \"b\": \"zo-computer\"}`. From a terminal: `anchor compare nanobot zo-computer`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nanobot.json and https://www.anchorterminal.com/api/v1/tools/zo-computer.json\n\n## Other comparisons with nanobot or Zo Computer\n\n- [AstrBot vs nanobot](https://www.anchorterminal.com/compare/astrbot-vs-nanobot.md)\n- [AstrBot vs Zo Computer](https://www.anchorterminal.com/compare/astrbot-vs-zo-computer.md)\n- [CowAgent vs nanobot](https://www.anchorterminal.com/compare/cowagent-vs-nanobot.md)\n- [CowAgent vs Zo Computer](https://www.anchorterminal.com/compare/cowagent-vs-zo-computer.md)\n- [GAIA vs nanobot](https://www.anchorterminal.com/compare/gaia-vs-nanobot.md)\n- [GAIA vs Zo Computer](https://www.anchorterminal.com/compare/gaia-vs-zo-computer.md)\n- [Gemini Spark vs nanobot](https://www.anchorterminal.com/compare/gemini-spark-vs-nanobot.md)\n- [Gemini Spark vs Zo Computer](https://www.anchorterminal.com/compare/gemini-spark-vs-zo-computer.md)\n- [Grok Bot vs nanobot](https://www.anchorterminal.com/compare/grok-bot-vs-nanobot.md)\n- [Grok Bot vs Zo Computer](https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer.md)\n- [Haven vs nanobot](https://www.anchorterminal.com/compare/haven-vs-nanobot.md)\n- [Haven vs Zo Computer](https://www.anchorterminal.com/compare/haven-vs-zo-computer.md)\n- [Hermes Agent vs nanobot](https://www.anchorterminal.com/compare/hermes-agent-vs-nanobot.md)\n- [Hermes Agent vs Zo Computer](https://www.anchorterminal.com/compare/hermes-agent-vs-zo-computer.md)\n- [Instinct vs nanobot](https://www.anchorterminal.com/compare/instinct-vs-nanobot.md)\n- [Instinct vs Zo Computer](https://www.anchorterminal.com/compare/instinct-vs-zo-computer.md)\n- [IronClaw vs nanobot](https://www.anchorterminal.com/compare/ironclaw-vs-nanobot.md)\n- [IronClaw vs Zo Computer](https://www.anchorterminal.com/compare/ironclaw-vs-zo-computer.md)\n- [Leon vs nanobot](https://www.anchorterminal.com/compare/leon-vs-nanobot.md)\n- [Leon vs Zo Computer](https://www.anchorterminal.com/compare/leon-vs-zo-computer.md)\n- [Lindy vs nanobot](https://www.anchorterminal.com/compare/lindy-vs-nanobot.md)\n- [Lindy vs Zo Computer](https://www.anchorterminal.com/compare/lindy-vs-zo-computer.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 PicoClaw](https://www.anchorterminal.com/compare/nanobot-vs-picoclaw.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- [NanoClaw vs Zo Computer](https://www.anchorterminal.com/compare/nanoclaw-vs-zo-computer.md)\n- [Dots vs Zo Computer](https://www.anchorterminal.com/compare/openai-dots-vs-zo-computer.md)\n- [OpenClaw vs Zo Computer](https://www.anchorterminal.com/compare/openclaw-vs-zo-computer.md)\n- [PicoClaw vs Zo Computer](https://www.anchorterminal.com/compare/picoclaw-vs-zo-computer.md)\n- [Poke vs Zo Computer](https://www.anchorterminal.com/compare/poke-vs-zo-computer.md)\n- [QwenPaw vs Zo Computer](https://www.anchorterminal.com/compare/qwenpaw-vs-zo-computer.md)\n- [ZeroClaw vs Zo Computer](https://www.anchorterminal.com/compare/zeroclaw-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 Zo Computer", "url": "" } ], "description": "nanobot scores 62.4 (B) to Zo Computer's 43.1 (E) for assistant proactive. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "nanobot B 62.4", "Zo Computer E 43.1", "scores" ], "h1": "nanobot vs Zo Computer", "image": "https://www.anchorterminal.com/assets/og/compare-nanobot-vs-zo-computer.png", "path": "/compare/nanobot-vs-zo-computer", "published": "2026-10-01", "section": "tools", "title": "nanobot vs Zo Computer for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/nanobot-vs-zo-computer" }, "tokens": { "markdown": 2700, "slim": 730 }, "version": 1 }