{ "data": { "a": { "slug": "grok-bot", "name": "Grok Bot", "vendor": "SpaceXAI and Cursor (Anysphere, Inc.)", "vendorUrl": "https://x.ai/bot", "kind": "platform", "category": "personal-assistants", "summary": "Hosted assistant from SpaceXAI and Cursor. Named Bots work on a persistent cloud computer with a browser, files and terminal, reached from desktop and mobile apps, Slack and X, with routines that run on a schedule.", "url": "https://www.anchorterminal.com/tools/grok-bot", "markdownUrl": "https://www.anchorterminal.com/tools/grok-bot.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/grok-bot.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/grok-bot.json", "license": "Proprietary", "transports": [], "packages": [], "auth": "mixed", "authNotes": "A person signs in with a Cursor account in the browser, or with Sign in with Grok for a Grok Business seat. SAML 2.0 single sign-on applies to teams, and SCIM is Enterprise only. Connectors are added from Connect apps and authenticated in the browser by OAuth, or configured with a key or token. OAuth tokens stay on Cursor's backend. For passwords, passkeys, two-factor codes, CAPTCHAs and payment confirmations the Bot hands the computer to the owner, and a secure secret request masks a value and keeps it out of the transcript and away from the model. Browser sessions then persist on the cloud computer shared by all of the user's Bots (https://docs.x.ai/grok-bot/security; https://docs.x.ai/grok-bot/approvals-security-and-privacy; https://docs.x.ai/grok-bot/team-bots). No API key or public API for the assistant was found. An Admin API for team settings is linked from the docs and was not read.", "pricing": "paid", "pricingNotes": "No separate subscription. Grok Bot is included with every paid individual Cursor plan (Pro, Pro+, Ultra) and with Cursor Teams, or through a linked individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription, or a seat on a self-serve Grok Business plan. Cursor's pricing page shows Individual at $20 a month and Teams at $40 a user a month. The Pro+ and Ultra prices sit behind tabs our reader did not see. Each tier includes weekly usage with no amount published, metered by agent steps and tokens. After that, on-demand usage is billed through Cursor up to a monthly limit the owner sets, which is not a hard stop in the middle of a run. A free trial is a usage credit with a 7-day window and never becomes a paid plan. SuperGrok Lite is not included, and a SuperGrok link cannot be undone or moved (https://cursor.com/help/grok-bot/plans; https://cursor.com/pricing; checked 2026-10-12).", "priceSummary": "$20 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Grok Bot docs, the plans page or the Grok Bot Terms (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://docs.x.ai/grok-bot/overview", "llmsTxt": "https://docs.x.ai/llms.txt", "capabilities": [ "assistant.proactive", "assistant.accounts", "assistant.memory", "assistant.messaging", "agent.mcp-client" ], "tags": [ "hosted", "closed-source", "desktop-app", "mobile-app", "computer-use", "scheduled-routines", "slack", "status-page", "iso27001", "soc2", "llms-txt", "paid" ], "graded": true, "anchor": { "graded": true, "score": 45.2, "grade": "E", "agentReady": false, "rank": 893, "ranked": true, "rankOf": 986, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 20, "payments": 25, "reliability": 40, "schema": 40, "security": 68, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": 0, "verdict": "Connector tokens stay on Cursor's backend and each user gets a separate microVM, with approvals, drafts and a review model before risky actions. All of a user's Bots share one computer and its sign-ins, the review model skips memory writes, and the status page shows seven major Grok Bot incidents since 3 September 2026.", "bestFor": "A person or team already paying for Cursor or SuperGrok who wants named assistants that keep working on a cloud computer, with routines and Slack or X entry points, and who will write approval rules.", "strengths": [ "Connector OAuth tokens stay on Cursor's backend. Bots call tools without receiving them, and tokens are never stored on the cloud computer", "Each user's work runs in a dedicated Firecracker microVM. A Bot has no identity of its own and holds no more access than the signed-in member", "Approvals from routines, triggers or other Bots expire after about 10 minutes and the action does not run", "Email and Slack messages can appear as editable drafts with Send and Discard buttons, and passwords, two-factor codes and payment confirmations are handed to the owner", "Markdown copies of every docs page and an llms.txt, with a security page that states what the controls do not cover" ], "weaknesses": [ "All of one user's Bots share one cloud computer, with its files, browser sessions and command-line credentials. The docs say separate Bots are not a security boundary", "The review model does not check memory writes or most settings changes, and the Grok Bot Terms call approval controls aids only", "Deleting a Bot leaves shared files and browser sessions on the computer. No way to view or delete single memories was found in the docs read", "Seven incidents marked major named Grok Bot on status.cursor.com between 3 September and 6 October 2026, the longest about six and a half hours", "Audit logs, Action Recording, network allowlists and enforced review rules are Enterprise only. Other teams default to allow-all network access", "Cursor chooses the model with no picker and no fixed set of model vendors, and no Grok Bot changelog was found" ], "agentNotes": [ "State in each request what the Bot may change and where it must stop. Which actions pause for approval depends on the tool, the risk and the owner's Auto-review rules", "Add narrow Ask first rules for sending, publishing, purchasing and deleting. Ask first wins over Allow automatically when both match", "Treat any sign-in or file on the cloud computer as available to every Bot on the account. Give a workload its own Cursor user when it needs separate credentials", "Run Test run with safe inputs. A test run performs real work and can call connected tools", "To remove access, pause routines, sign out of sites on the computer, uninstall connectors and revoke them at the source service. Deleting the Bot is not enough" ], "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": 45.2 } ], "editorialScores": { "ergonomics": 50, "maintenance": 20, "payments": 25, "reliability": 40, "schema": 40, "security": 68, "transparency": 48 }, "provenanceScore": 84 }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/grok-bot" }, "sameCompany": [ "cursor-cli" ], "area": "frameworks", "unitPrices": [ { "item": "Cursor Individual plan, as shown on the pricing page", "unit": "month", "usd": 20, "note": "Includes Grok Bot with weekly usage. On-demand usage extra" }, { "item": "Cursor Teams plan", "unit": "seat-month", "usd": 40, "note": "Includes Grok Bot for every member. On-demand usage on by default" } ], "provenance": { "legalEntity": "Anysphere, Inc.", "domain": "cursor.com", "domainRegistered": "1995-12-20", "endpointOnVendorDomain": null, "terms": "https://cursor.com/en-US/terms/grok-bot", "privacy": "https://cursor.com/privacy", "statusPage": "https://status.cursor.com", "changelog": "", "securityTxt": "valid", "checked": "2026-10-12", "notes": [ "The Grok Bot Terms (last updated 3 September 2026) supplement the agreement that governs the customer's use of the Services and define the Provider as the entity under that agreement. For a Cursor account that agreement is Cursor's Terms of Service (last updated 3 September 2026), which name Anysphere, Inc., 2261 Market Street STE 86466, San Francisco, CA 94114 (https://cursor.com/terms-of-service).", "The product docs are on docs.x.ai, titled SpaceXSI Docs, and name SpaceXAI. The Grok Bot Terms say they create no contractual relationship between the customer and any affiliate of the Provider. No page read states how the two companies are related.", "The privacy policy (last updated 11 October 2026) is Anysphere's and says it does not apply where Anysphere processes data for commercial customers as a processor.", "cursor.com/.well-known/security.txt gives a GitHub security page and security-reports@cursor.com as contacts and has no Expires field.", "The docs name api2.cursor.sh and *.cursorvm.com as the hosts the app and the cloud computer use. There is no endpoint an outside agent calls.", "RDAP for cursor.com gives a registration date of 1995-12-20.", "No changelog for Grok Bot was found. Cursor's changelog entries from 29 July to 6 October 2026 do not mention it.", "docs.x.ai's robots.txt allows every path with Content-Signal ai-input=yes. x.ai's robots.txt does the same, but x.ai/bot and status.x.ai answered HTTP 403." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/grok-bot.json", "live": { "slug": "grok-bot", "vendorStatus": { "page": "https://status.cursor.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-12T18:56:36.692375788Z" }, "updatedAt": "2026-10-12T18:56:36.692375788Z" } }, "answer": "NanoClaw scores 68.3 (B) on agent readiness against Grok Bot's 45.2 (E), and leads in 6 of 7 scored categories.", "b": { "slug": "nanoclaw", "name": "NanoClaw", "vendor": "NanoCo, Inc.", "vendorUrl": "https://nanoclaw.dev", "kind": "harness", "category": "personal-assistants", "summary": "Open-source personal assistant that the owner runs on their own machine. It answers on messaging apps, runs each agent session in a Docker container, keeps Markdown memory on disk and runs scheduled tasks.", "url": "https://www.anchorterminal.com/tools/nanoclaw", "markdownUrl": "https://www.anchorterminal.com/tools/nanoclaw.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nanoclaw.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nanoclaw.json", "repo": "https://github.com/nanocoai/nanoclaw", "license": "MIT", "transports": [], "packages": [], "auth": "none", "authNotes": "No account is needed to run it. Owners and admins are rows in a local `user_roles` table, and strangers are handled by each chat's `unknown_sender_policy` (https://docs.nanoclaw.dev/concepts/security). Model and service credentials are registered with a credential gateway on the host, OneCLI Agent Vault by default, which adds them to outbound HTTPS requests. Containers receive placeholders such as `onecli-managed` (https://docs.nanoclaw.dev/operate/credentials). Channel tokens stay in the host's `.env`. An optional free NanoClaw account, used for a prebuilt agent image and a managed Slack app, keeps its token in `~/.config/nanoclaw/account.json` with mode 0600 (https://github.com/nanocoai/nanoclaw/blob/main/README.md).", "pricing": "free", "pricingNotes": "Free under the MIT licence, with nothing on sale. The optional NanoClaw account, the Echo image and the managed Slack app are free of charge per the terms of 31 July 2026 (https://nanoclaw.dev/terms). The owner pays the model provider through a Claude subscription, an API key or another provider, and any service a channel or tool uses, such as Dial. Since 2.4.0 Claude groups default to Opus 5.5 (checked 2026-10-12).", "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": 30929, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://docs.nanoclaw.dev", "llmsTxt": "https://docs.nanoclaw.dev/llms.txt", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.memory", "assistant.self-hosted", "agent.mcp-client", "assistant.accounts" ], "tags": [ "open-source", "local", "free", "no-card", "docker", "llms-txt" ], "lastRelease": "2026-10-09", "graded": true, "anchor": { "graded": true, "score": 68.3, "grade": "B", "agentReady": false, "rank": 229, "ranked": true, "rankOf": 986, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 78, "payments": 60, "reliability": 78, "schema": 82, "security": 74, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": -5, "negativeNotes": [ "2026-10-09. Release 2026.10.0 fixed four symlink flaws through which a manipulated agent could make the host read, write or delete files outside its folders, plus an admin-command bypass, a cross-group read through `ncl` and a command injection in Mattermost setup. Fixed and described in the changelog within the week, but the advisories it links (GHSA-frvf-5rf5-89fq and seven others) were not public on 12 October 2026. -5. https://github.com/nanocoai/nanoclaw/blob/main/CHANGELOG.md" ], "verdict": "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.", "bestFor": "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.", "strengths": [ "Each session runs in a non-root Docker container with all capabilities dropped, and the project root and `.env` are never mounted", "API keys sit in a credential gateway on the host, which adds them to outbound requests, so the container holds only placeholders", "Installing packages, adding an MCP server and admitting a new chat each wait for an admin's approval, and no reachable approver means denial", "Memory is plain Markdown under `groups/\u003cfolder\u003e/memory/`, which the owner can read, edit or delete on the host", "The security page states what the design does not stop, including messages to wired chats and spending through granted credentials" ], "weaknesses": [ "The Claude provider runs with `permissionMode: 'bypassPermissions'`, so shell, file and web tools run inside the container with no prompt", "Egress lockdown is off by default, so a container can reach the internet directly unless `NANOCLAW_EGRESS_LOCKDOWN=true` is set", "The 2026.10.0 changelog links eight advisories on the repository, and on 12 October 2026 the advisories page listed none and one linked advisory returned 404", "Setup sends events to PostHog unless `NANOCLAW_NO_DIAGNOSTICS=1` is set, and the privacy policy does not mention them", "The docs say trunk has no Gmail or Google Calendar integration, while the GitHub repository description still names Gmail", "294 open issues and 750 open pull requests on 12 October 2026, and 10 of the 12 newest open issues had no reply" ], "agentNotes": [ "Install with `git clone` and `bash 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=true` before 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" ], "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": 68.3 } ], "editorialScores": { "ergonomics": 70, "maintenance": 78, "payments": 60, "reliability": 78, "schema": 82, "security": 74, "transparency": 77 }, "provenanceScore": 53 }, "connect": { "install": "git clone https://github.com/nanocoai/nanoclaw.git nanoclaw-v2 \u0026\u0026 cd nanoclaw-v2 \u0026\u0026 bash nanoclaw.sh" }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/nanoclaw" }, "area": "frameworks", "provenance": { "legalEntity": "NanoCo, Inc.", "domain": "nanoclaw.dev", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/nanocoai/nanoclaw/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-12", "notes": [ "The terms and privacy policy at nanoclaw.dev name NanoCo, Inc. and Delaware law. Both say they cover the website and the optional account, not the software, so neither is linked and the MIT licence stands in.", "nanoclaw.dev/.well-known/security.txt returned 404 on 12 October 2026. The repository's SECURITY.md points to GitHub private vulnerability reporting.", "There is no hosted endpoint. The assistant runs on the owner's machine, and the optional account service is at portal.nanoclaw.dev, which we did not open.", "The registration date of nanoclaw.dev was not checked." ], "score": 53 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nanoclaw.json" }, "facts": [ { "a": "Platform", "b": "Agent harness", "name": "Kind" }, { "a": "SpaceXAI and Cursor (Anysphere, Inc.)", "b": "NanoCo, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "None", "name": "Auth" }, { "a": "Paid", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary", "b": "MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-09", "name": "Last release" }, { "a": "2026-09-03", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-09-29", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "31k stars", "name": "Popularity" } ], "faq": [ { "answer": "NanoClaw scores 68.3 (B) on agent readiness against Grok Bot's 45.2 (E), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Grok Bot or NanoClaw?" }, { "answer": "No open-source release is listed for Grok Bot. NanoClaw is open source (MIT).", "question": "Are Grok Bot and NanoClaw open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No incidents deducted, where NanoClaw loses 5 points for them" ], "goodFor": "A person or team already paying for Cursor or SuperGrok who wants named assistants that keep working on a cloud computer, with routines and Slack or X entry points, and who will write approval rules.", "slug": "grok-bot", "watchFor": "All of one user's Bots share one cloud computer, with its files, browser sessions and command-line credentials. The docs say separate Bots are not a security boundary" }, { "aheadOn": [ "Reliability, 78 against 40", "Schema \u0026 documentation, 82 against 40", "Agent ergonomics, 70 against 50", "Security \u0026 auth, 74 against 68", "Payments \u0026 pricing, 60 against 25", "Maintenance \u0026 community, 78 against 20" ], "also": [ "No key needed to call it", "Free to start without a card", "Open source" ], "goodFor": "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.", "slug": "nanoclaw", "watchFor": "The Claude provider runs with `permissionMode: 'bypassPermissions'`, so shell, file and web tools run inside the container with no prompt" } ], "job": { "capability": "assistant.proactive", "name": "Assistant proactive" }, "others": [ { "json": "https://www.anchorterminal.com/compare/astrbot-vs-grok-bot.json", "title": "AstrBot vs Grok Bot", "url": "https://www.anchorterminal.com/compare/astrbot-vs-grok-bot" }, { "json": "https://www.anchorterminal.com/compare/astrbot-vs-nanoclaw.json", "title": "AstrBot vs NanoClaw", "url": "https://www.anchorterminal.com/compare/astrbot-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/cowagent-vs-grok-bot.json", "title": "CowAgent vs Grok Bot", "url": "https://www.anchorterminal.com/compare/cowagent-vs-grok-bot" }, { "json": "https://www.anchorterminal.com/compare/cowagent-vs-nanoclaw.json", "title": "CowAgent vs NanoClaw", "url": "https://www.anchorterminal.com/compare/cowagent-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/gaia-vs-grok-bot.json", "title": "GAIA vs Grok Bot", "url": "https://www.anchorterminal.com/compare/gaia-vs-grok-bot" }, { "json": "https://www.anchorterminal.com/compare/gaia-vs-nanoclaw.json", "title": "GAIA vs NanoClaw", "url": "https://www.anchorterminal.com/compare/gaia-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot.json", "title": "Gemini Spark vs Grok Bot", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot" }, { "json": "https://www.anchorterminal.com/compare/gemini-spark-vs-nanoclaw.json", "title": "Gemini Spark vs NanoClaw", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-haven.json", "title": "Grok Bot vs Haven", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-haven" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent.json", "title": "Grok Bot vs Hermes Agent", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-instinct.json", "title": "Grok Bot vs Instinct", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-instinct" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw.json", "title": "Grok Bot vs IronClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-leon.json", "title": "Grok Bot vs Leon", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-leon" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-lindy.json", "title": "Grok Bot vs Lindy", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-lindy" }, { "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-openai-dots.json", "title": "Grok Bot vs Dots", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-openai-dots" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-openclaw.json", "title": "Grok Bot vs OpenClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-openclaw" }, { "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/grok-bot-vs-poke.json", "title": "Grok Bot vs Poke", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-poke" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-qwenpaw.json", "title": "Grok Bot vs QwenPaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-qwenpaw" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-zeroclaw.json", "title": "Grok Bot vs ZeroClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-zeroclaw" }, { "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-nanoclaw.json", "title": "Haven vs NanoClaw", "url": "https://www.anchorterminal.com/compare/haven-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-nanoclaw.json", "title": "Hermes Agent vs NanoClaw", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/instinct-vs-nanoclaw.json", "title": "Instinct vs NanoClaw", "url": "https://www.anchorterminal.com/compare/instinct-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-nanoclaw.json", "title": "IronClaw vs NanoClaw", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/leon-vs-nanoclaw.json", "title": "Leon vs NanoClaw", "url": "https://www.anchorterminal.com/compare/leon-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-nanoclaw.json", "title": "Lindy vs NanoClaw", "url": "https://www.anchorterminal.com/compare/lindy-vs-nanoclaw" }, { "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/nanoclaw-vs-openai-dots.json", "title": "NanoClaw vs Dots", "url": "https://www.anchorterminal.com/compare/nanoclaw-vs-openai-dots" }, { "json": "https://www.anchorterminal.com/compare/nanoclaw-vs-openclaw.json", "title": "NanoClaw vs OpenClaw", "url": "https://www.anchorterminal.com/compare/nanoclaw-vs-openclaw" }, { "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/nanoclaw-vs-poke.json", "title": "NanoClaw vs Poke", "url": "https://www.anchorterminal.com/compare/nanoclaw-vs-poke" }, { "json": "https://www.anchorterminal.com/compare/nanoclaw-vs-qwenpaw.json", "title": "NanoClaw vs QwenPaw", "url": "https://www.anchorterminal.com/compare/nanoclaw-vs-qwenpaw" }, { "json": "https://www.anchorterminal.com/compare/nanoclaw-vs-zeroclaw.json", "title": "NanoClaw vs ZeroClaw", "url": "https://www.anchorterminal.com/compare/nanoclaw-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" } ], "scores": [ { "by": 38, "edge": "nanoclaw", "grok-bot": 40, "key": "reliability", "name": "Reliability", "nanoclaw": 78, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 42, "edge": "nanoclaw", "grok-bot": 40, "key": "schema", "name": "Schema \u0026 documentation", "nanoclaw": 82, "weight": 13 }, { "by": 20, "edge": "nanoclaw", "grok-bot": 50, "key": "ergonomics", "name": "Agent ergonomics", "nanoclaw": 70, "weight": 13 }, { "by": 6, "edge": "nanoclaw", "grok-bot": 68, "key": "security", "name": "Security \u0026 auth", "nanoclaw": 74, "weight": 14 }, { "by": 35, "edge": "nanoclaw", "grok-bot": 25, "key": "payments", "name": "Payments \u0026 pricing", "nanoclaw": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 58, "edge": "nanoclaw", "grok-bot": 20, "key": "maintenance", "name": "Maintenance \u0026 community", "nanoclaw": 78, "weight": 7 }, { "by": 1, "edge": "grok-bot", "grok-bot": 66, "key": "transparency", "name": "Transparency \u0026 trust", "nanoclaw": 65, "weight": 7 } ], "summary": "NanoClaw scores 68.3 (B) on agent readiness against Grok Bot's 45.2 (E), and leads in 6 of 7 scored categories. Both do assistant proactive.", "verdicts": { "grok-bot": "Connector tokens stay on Cursor's backend and each user gets a separate microVM, with approvals, drafts and a review model before risky actions. All of a user's Bots share one computer and its sign-ins, the review model skips memory writes, and the status page shows seven major Grok Bot incidents since 3 September 2026.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw", "json": "https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw.md", "slim": "https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw.min.md" }, "markdown": "NanoClaw scores 68.3 (B) on agent readiness against Grok Bot's 45.2 (E), and leads in 6 of 7 scored categories. Both do assistant proactive.\n\n- Grok Bot: grade E, 45.2/100, rank #893 of 986. Markdown https://www.anchorterminal.com/tools/grok-bot.md · JSON https://www.anchorterminal.com/api/v1/tools/grok-bot.json\n- NanoClaw: grade B, 68.3/100, rank #229 of 986. Markdown https://www.anchorterminal.com/tools/nanoclaw.md · JSON https://www.anchorterminal.com/api/v1/tools/nanoclaw.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### Grok Bot (E)\n\nGood for: A person or team already paying for Cursor or SuperGrok who wants named assistants that keep working on a cloud computer, with routines and Slack or X entry points, and who will write approval rules.\n\nAlso in its favour:\n- No incidents deducted, where NanoClaw loses 5 points for them\n\nWatch for: All of one user's Bots share one cloud computer, with its files, browser sessions and command-line credentials. The docs say separate Bots are not a security boundary\n\n### NanoClaw (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 78 against 40\n- Schema \u0026 documentation, 82 against 40\n- Agent ergonomics, 70 against 50\n- Security \u0026 auth, 74 against 68\n- Payments \u0026 pricing, 60 against 25\n- Maintenance \u0026 community, 78 against 20\n\nAlso in its favour:\n- No key needed to call it\n- Free to start without a card\n- Open source\n\nWatch for: The Claude provider runs with `permissionMode: 'bypassPermissions'`, so shell, file and web tools run inside the container with no prompt\n\n\n## Score by category\n\n| Category | Weight | Grok Bot | NanoClaw | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 78 | NanoClaw +38 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 82 | NanoClaw +42 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 70 | NanoClaw +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 74 | NanoClaw +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 60 | NanoClaw +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 78 | NanoClaw +58 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 65 | Grok Bot +1 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **45.2 · E** | **68.3 · B** | |\n\n## Facts side by side\n\n| Fact | Grok Bot | NanoClaw |\n| --- | --- | --- |\n| Kind | Platform | Agent harness |\n| Vendor | SpaceXAI and Cursor (Anysphere, Inc.) | NanoCo, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | OAuth or key | None |\n| Pricing | Paid | Free |\n| x402 | no | no |\n| Licence | Proprietary | MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-09 |\n| Terms last updated | 2026-09-03 | no document linked |\n| Privacy policy last updated | 2026-09-29 | no document linked |\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 | none | 31k stars |\n\n## Verdicts\n\n**Grok Bot.** Connector tokens stay on Cursor's backend and each user gets a separate microVM, with approvals, drafts and a review model before risky actions. All of a user's Bots share one computer and its sign-ins, the review model skips memory writes, and the status page shows seven major Grok Bot incidents since 3 September 2026.\n\n**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.\n\n## Before you call either\n\n### Grok Bot\n\n1. State in each request what the Bot may change and where it must stop. Which actions pause for approval depends on the tool, the risk and the owner's Auto-review rules\n2. Add narrow Ask first rules for sending, publishing, purchasing and deleting. Ask first wins over Allow automatically when both match\n3. Treat any sign-in or file on the cloud computer as available to every Bot on the account. Give a workload its own Cursor user when it needs separate credentials\n4. Run Test run with safe inputs. A test run performs real work and can call connected tools\n5. To remove access, pause routines, sign out of sites on the computer, uninstall connectors and revoke them at the source service. Deleting the Bot is not enough\n\n### NanoClaw\n\n1. Install with `git clone` and `bash nanoclaw.sh`. There is no registry package, and setup needs Docker, Node 22 or later and a Claude or Codex credential\n2. Set `NANOCLAW_EGRESS_LOCKDOWN=true` before giving an agent credentials or an audience of strangers. The default leaves egress open\n3. Put chats with different audiences in separate agent groups. Every session of a group shares one read-write workspace and memory tree\n4. Turn on per-request approval for a secret in the gateway when its use should wait for a person. It is off unless configured\n5. 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\n\n## Questions\n\n### Which is better for AI agents, Grok Bot or NanoClaw?\n\nNanoClaw scores 68.3 (B) on agent readiness against Grok Bot's 45.2 (E), and leads in 6 of 7 scored categories.\n\n### Are Grok Bot and NanoClaw open source?\n\nNo open-source release is listed for Grok Bot. NanoClaw is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw.json, and with the fewest tokens: https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"grok-bot\", \"b\": \"nanoclaw\"}`. From a terminal: `anchor compare grok-bot nanoclaw`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/grok-bot.json and https://www.anchorterminal.com/api/v1/tools/nanoclaw.json\n\n## Other comparisons with Grok Bot or NanoClaw\n\n- [AstrBot vs Grok Bot](https://www.anchorterminal.com/compare/astrbot-vs-grok-bot.md)\n- [AstrBot vs NanoClaw](https://www.anchorterminal.com/compare/astrbot-vs-nanoclaw.md)\n- [CowAgent vs Grok Bot](https://www.anchorterminal.com/compare/cowagent-vs-grok-bot.md)\n- [CowAgent vs NanoClaw](https://www.anchorterminal.com/compare/cowagent-vs-nanoclaw.md)\n- [GAIA vs Grok Bot](https://www.anchorterminal.com/compare/gaia-vs-grok-bot.md)\n- [GAIA vs NanoClaw](https://www.anchorterminal.com/compare/gaia-vs-nanoclaw.md)\n- [Gemini Spark vs Grok Bot](https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot.md)\n- [Gemini Spark vs NanoClaw](https://www.anchorterminal.com/compare/gemini-spark-vs-nanoclaw.md)\n- [Grok Bot vs Haven](https://www.anchorterminal.com/compare/grok-bot-vs-haven.md)\n- [Grok Bot vs Hermes Agent](https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent.md)\n- [Grok Bot vs Instinct](https://www.anchorterminal.com/compare/grok-bot-vs-instinct.md)\n- [Grok Bot vs IronClaw](https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw.md)\n- [Grok Bot vs Leon](https://www.anchorterminal.com/compare/grok-bot-vs-leon.md)\n- [Grok Bot vs Lindy](https://www.anchorterminal.com/compare/grok-bot-vs-lindy.md)\n- [Grok Bot vs nanobot](https://www.anchorterminal.com/compare/grok-bot-vs-nanobot.md)\n- [Grok Bot vs Dots](https://www.anchorterminal.com/compare/grok-bot-vs-openai-dots.md)\n- [Grok Bot vs OpenClaw](https://www.anchorterminal.com/compare/grok-bot-vs-openclaw.md)\n- [Grok Bot vs PicoClaw](https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.md)\n- [Grok Bot vs Poke](https://www.anchorterminal.com/compare/grok-bot-vs-poke.md)\n- [Grok Bot vs QwenPaw](https://www.anchorterminal.com/compare/grok-bot-vs-qwenpaw.md)\n- [Grok Bot vs ZeroClaw](https://www.anchorterminal.com/compare/grok-bot-vs-zeroclaw.md)\n- [Grok Bot vs Zo Computer](https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer.md)\n- [Haven vs NanoClaw](https://www.anchorterminal.com/compare/haven-vs-nanoclaw.md)\n- [Hermes Agent vs NanoClaw](https://www.anchorterminal.com/compare/hermes-agent-vs-nanoclaw.md)\n- [Instinct vs NanoClaw](https://www.anchorterminal.com/compare/instinct-vs-nanoclaw.md)\n- [IronClaw vs NanoClaw](https://www.anchorterminal.com/compare/ironclaw-vs-nanoclaw.md)\n- [Leon vs NanoClaw](https://www.anchorterminal.com/compare/leon-vs-nanoclaw.md)\n- [Lindy vs NanoClaw](https://www.anchorterminal.com/compare/lindy-vs-nanoclaw.md)\n- [nanobot vs NanoClaw](https://www.anchorterminal.com/compare/nanobot-vs-nanoclaw.md)\n- [NanoClaw vs Dots](https://www.anchorterminal.com/compare/nanoclaw-vs-openai-dots.md)\n- [NanoClaw vs OpenClaw](https://www.anchorterminal.com/compare/nanoclaw-vs-openclaw.md)\n- [NanoClaw vs PicoClaw](https://www.anchorterminal.com/compare/nanoclaw-vs-picoclaw.md)\n- [NanoClaw vs Poke](https://www.anchorterminal.com/compare/nanoclaw-vs-poke.md)\n- [NanoClaw vs QwenPaw](https://www.anchorterminal.com/compare/nanoclaw-vs-qwenpaw.md)\n- [NanoClaw vs ZeroClaw](https://www.anchorterminal.com/compare/nanoclaw-vs-zeroclaw.md)\n- [NanoClaw vs Zo Computer](https://www.anchorterminal.com/compare/nanoclaw-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": "Grok Bot vs NanoClaw", "url": "" } ], "description": "NanoClaw scores 68.3 (B) to Grok Bot's 45.2 (E) for assistant proactive. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grok Bot E 45.2", "NanoClaw B 68.3", "scores" ], "h1": "Grok Bot vs NanoClaw", "image": "https://www.anchorterminal.com/assets/og/compare-grok-bot-vs-nanoclaw.png", "path": "/compare/grok-bot-vs-nanoclaw", "published": "2026-10-01", "section": "tools", "title": "Grok Bot vs NanoClaw for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw" }, "tokens": { "markdown": 2650, "slim": 680 }, "version": 1 }