{ "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": "PicoClaw and Grok Bot score within a point of each other on agent readiness, 46.1 (D) and 45.2 (E). Grok Bot leads on security \u0026 auth and 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": "Platform", "b": "Agent harness", "name": "Kind" }, { "a": "SpaceXAI and Cursor (Anysphere, Inc.)", "b": "Sipeed", "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": "no", "name": "llms.txt" }, { "a": "none", "b": "2026-07-03", "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": "30k stars", "name": "Popularity" } ], "faq": [ { "answer": "PicoClaw and Grok Bot score within a point of each other on agent readiness, 46.1 (D) and 45.2 (E). Grok Bot leads on security \u0026 auth and transparency \u0026 trust.", "question": "Which is better for AI agents, Grok Bot or PicoClaw?" }, { "answer": "No open-source release is listed for Grok Bot. PicoClaw is open source (MIT).", "question": "Are Grok Bot and PicoClaw open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 68 against 51", "Transparency \u0026 trust, 66 against 56" ], "also": [ "No incidents deducted, where PicoClaw loses 7 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, 54 against 40", "Schema \u0026 documentation, 51 against 40", "Agent ergonomics, 66 against 50", "Payments \u0026 pricing, 60 against 25" ], "also": [ "No key needed to call it", "Free to start without a card", "Open source" ], "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-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-picoclaw.json", "title": "AstrBot vs PicoClaw", "url": "https://www.anchorterminal.com/compare/astrbot-vs-picoclaw" }, { "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-picoclaw.json", "title": "CowAgent vs PicoClaw", "url": "https://www.anchorterminal.com/compare/cowagent-vs-picoclaw" }, { "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-picoclaw.json", "title": "GAIA vs PicoClaw", "url": "https://www.anchorterminal.com/compare/gaia-vs-picoclaw" }, { "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-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-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-nanoclaw.json", "title": "Grok Bot vs NanoClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw" }, { "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-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-picoclaw.json", "title": "Haven vs PicoClaw", "url": "https://www.anchorterminal.com/compare/haven-vs-picoclaw" }, { "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-picoclaw.json", "title": "Instinct vs PicoClaw", "url": "https://www.anchorterminal.com/compare/instinct-vs-picoclaw" }, { "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-picoclaw.json", "title": "Leon vs PicoClaw", "url": "https://www.anchorterminal.com/compare/leon-vs-picoclaw" }, { "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-picoclaw.json", "title": "nanobot vs PicoClaw", "url": "https://www.anchorterminal.com/compare/nanobot-vs-picoclaw" }, { "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": 14, "edge": "picoclaw", "grok-bot": 40, "key": "reliability", "name": "Reliability", "picoclaw": 54, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "edge": "picoclaw", "grok-bot": 40, "key": "schema", "name": "Schema \u0026 documentation", "picoclaw": 51, "weight": 13 }, { "by": 16, "edge": "picoclaw", "grok-bot": 50, "key": "ergonomics", "name": "Agent ergonomics", "picoclaw": 66, "weight": 13 }, { "by": 17, "edge": "grok-bot", "grok-bot": 68, "key": "security", "name": "Security \u0026 auth", "picoclaw": 51, "weight": 14 }, { "by": 35, "edge": "picoclaw", "grok-bot": 25, "key": "payments", "name": "Payments \u0026 pricing", "picoclaw": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "edge": "picoclaw", "grok-bot": 20, "key": "maintenance", "name": "Maintenance \u0026 community", "picoclaw": 22, "weight": 7 }, { "by": 10, "edge": "grok-bot", "grok-bot": 66, "key": "transparency", "name": "Transparency \u0026 trust", "picoclaw": 56, "weight": 7 } ], "summary": "PicoClaw and Grok Bot score within a point of each other on agent readiness, 46.1 (D) and 45.2 (E). Grok Bot leads on security \u0026 auth and transparency \u0026 trust. 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.", "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/grok-bot-vs-picoclaw", "json": "https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.md", "slim": "https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.min.md" }, "markdown": "PicoClaw and Grok Bot score within a point of each other on agent readiness, 46.1 (D) and 45.2 (E). Grok Bot leads on security \u0026 auth and transparency \u0026 trust. 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- 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### 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\nAhead on:\n- Security \u0026 auth, 68 against 51\n- Transparency \u0026 trust, 66 against 56\n\nAlso in its favour:\n- No incidents deducted, where PicoClaw loses 7 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### 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- Reliability, 54 against 40\n- Schema \u0026 documentation, 51 against 40\n- Agent ergonomics, 66 against 50\n- Payments \u0026 pricing, 60 against 25\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: 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 | Grok Bot | PicoClaw | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 54 | PicoClaw +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 51 | PicoClaw +11 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 66 | PicoClaw +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 51 | Grok Bot +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 60 | PicoClaw +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 22 | PicoClaw +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 56 | Grok Bot +10 |\n| Negative events | ≤15 | 0 | -7 | |\n| **Total** | | **45.2 · E** | **46.1 · D** | |\n\n## Facts side by side\n\n| Fact | Grok Bot | PicoClaw |\n| --- | --- | --- |\n| Kind | Platform | Agent harness |\n| Vendor | SpaceXAI and Cursor (Anysphere, Inc.) | Sipeed |\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 | no |\n| Last release | none | 2026-07-03 |\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 | 30k 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**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### 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### 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, Grok Bot or PicoClaw?\n\nPicoClaw and Grok Bot score within a point of each other on agent readiness, 46.1 (D) and 45.2 (E). Grok Bot leads on security \u0026 auth and transparency \u0026 trust.\n\n### Are Grok Bot and PicoClaw open source?\n\nNo open-source release is listed for Grok Bot. PicoClaw is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.json, and with the fewest tokens: https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"grok-bot\", \"b\": \"picoclaw\"}`. From a terminal: `anchor compare grok-bot picoclaw`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/grok-bot.json and https://www.anchorterminal.com/api/v1/tools/picoclaw.json\n\n## Other comparisons with Grok Bot or PicoClaw\n\n- [AstrBot vs Grok Bot](https://www.anchorterminal.com/compare/astrbot-vs-grok-bot.md)\n- [AstrBot vs PicoClaw](https://www.anchorterminal.com/compare/astrbot-vs-picoclaw.md)\n- [CowAgent vs Grok Bot](https://www.anchorterminal.com/compare/cowagent-vs-grok-bot.md)\n- [CowAgent vs PicoClaw](https://www.anchorterminal.com/compare/cowagent-vs-picoclaw.md)\n- [GAIA vs Grok Bot](https://www.anchorterminal.com/compare/gaia-vs-grok-bot.md)\n- [GAIA vs PicoClaw](https://www.anchorterminal.com/compare/gaia-vs-picoclaw.md)\n- [Gemini Spark vs Grok Bot](https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot.md)\n- [Gemini Spark vs PicoClaw](https://www.anchorterminal.com/compare/gemini-spark-vs-picoclaw.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 NanoClaw](https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw.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 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 PicoClaw](https://www.anchorterminal.com/compare/haven-vs-picoclaw.md)\n- [Hermes Agent vs PicoClaw](https://www.anchorterminal.com/compare/hermes-agent-vs-picoclaw.md)\n- [Instinct vs PicoClaw](https://www.anchorterminal.com/compare/instinct-vs-picoclaw.md)\n- [IronClaw vs PicoClaw](https://www.anchorterminal.com/compare/ironclaw-vs-picoclaw.md)\n- [Leon vs PicoClaw](https://www.anchorterminal.com/compare/leon-vs-picoclaw.md)\n- [Lindy vs PicoClaw](https://www.anchorterminal.com/compare/lindy-vs-picoclaw.md)\n- [nanobot vs PicoClaw](https://www.anchorterminal.com/compare/nanobot-vs-picoclaw.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": "Grok Bot vs PicoClaw", "url": "" } ], "description": "PicoClaw and Grok Bot score within a point of each other for assistant proactive, 46.1 and 45.2 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grok Bot E 45.2", "PicoClaw D 46.1", "scores" ], "h1": "Grok Bot vs PicoClaw", "image": "https://www.anchorterminal.com/assets/og/compare-grok-bot-vs-picoclaw.png", "path": "/compare/grok-bot-vs-picoclaw", "published": "2026-10-01", "section": "tools", "title": "Grok Bot vs PicoClaw for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw" }, "tokens": { "markdown": 2650, "slim": 730 }, "version": 1 }