{ "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": "IronClaw scores 66.7 (B) on agent readiness against Grok Bot's 45.2 (E), and leads in 6 of 7 scored categories.", "b": { "slug": "ironclaw", "name": "IronClaw", "vendor": "NEAR AI", "vendorUrl": "https://www.ironclaw.com", "kind": "harness", "category": "personal-assistants", "summary": "IronClaw is an open-source personal AI assistant written in Rust by NEAR AI. The owner runs it as a local service with a web interface, Slack and Telegram channels, Google and GitHub extensions, scheduled automations and persistent memory.", "url": "https://www.anchorterminal.com/tools/ironclaw", "markdownUrl": "https://www.anchorterminal.com/tools/ironclaw.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/ironclaw.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/ironclaw.json", "repo": "https://github.com/nearai/ironclaw", "license": "MIT OR Apache-2.0", "transports": [ "http" ], "packages": [], "auth": "mixed", "authNotes": "`ironclaw onboard` writes a bearer token to `~/.ironclaw/reborn/webui-token` and prints a login link that carries it as a `token` query parameter. The same token authorises the web interface and the Responses API with operator rights. Multi-user deployments can add Google or GitHub single sign-on and per-user API tokens with owner, admin or member roles. Connected accounts use OAuth (Google, Slack), a Telegram pairing code, or keys held in the encrypted secret store. The web interface binds to 127.0.0.1:3000 unless `--host` is changed (https://docs.ironclaw.com/using/webui.md).", "pricing": "freemium", "pricingNotes": "Free to self-host under MIT or Apache-2.0, with model usage billed by whichever provider the owner selects, or nothing with Ollama. NEAR AI sells hosted instances on ironclaw.com as Starter (shown as $5 beside $0 a month, 1 agent, $5 credits), Basic at $20 a month (2 agents, $20 credits) and Pro+ at $200 a month (5 agents, $200 credits). The page does not say whether a card is needed. NEAR AI Cloud inference is priced per million tokens on near.ai/pricing (checked 2026-10-12).", "priceSummary": "$20 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs or the release notes (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 12648, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://docs.ironclaw.com", "llmsTxt": "https://docs.ironclaw.com/llms.txt", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory", "assistant.self-hosted", "agent.mcp-client" ], "tags": [ "open-source", "self-hosted", "rust", "wasm", "telegram", "slack", "gmail", "mcp", "hosted-option", "llms-txt" ], "lastRelease": "2026-09-29", "graded": true, "anchor": { "graded": true, "score": 66.7, "grade": "B", "agentReady": false, "rank": 288, "ranked": true, "rankOf": 986, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 74, "payments": 60, "reliability": 67, "schema": 74, "security": 66, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": -2, "negativeNotes": [ "2026-10-12. The ironclaw.com home page lists Discord and Signal among integrations, while the channel docs for the current release say Discord, Signal, WeChat and WeCom are not part of the 1.0 release, which shipped on 27 July 2026. The docs site also says it documents the latest stable release while its heartbeat, cron, shell and WASM pages name settings absent from the 1.4.1 source. A misleading claim, at the minimum, -2. https://www.ironclaw.com/; https://docs.ironclaw.com/channels/overview.md; https://github.com/nearai/ironclaw/blob/ironclaw-v1.4.1/docs/capabilities/routines/heartbeat.mdx" ], "verdict": "Credentials stay in an encrypted store and are injected at the host boundary, and extensions declare per-tool permissions, network targets and OAuth scopes. The global auto-approve setting defaults to on in the 1.4.1 source, so tools marked ask, such as `gmail.send_message`, run unprompted until the owner turns it off.", "bestFor": "One technical owner who wants a self-hosted assistant over Gmail, Calendar, Slack and Telegram with credentials kept out of the model's reach.", "strengths": [ "Dual MIT or Apache-2.0 licence, with installers for seven targets on GitHub releases and no account needed to run it", "Each extension tool declares a default permission, effects, network targets and OAuth scopes in `manifest.toml`. Gmail reads use `gmail.readonly` and sends use `gmail.send`", "Secrets are encrypted with AES-256-GCM per the README, with the master key in the OS keychain, and are injected into requests outside the sandbox", "No analytics library was found in the 1.4.1 source. Trace Commons is opt-in and has no default endpoint", "Six stable releases between 27 July and 29 September 2026, each with dated notes and upgrade steps" ], "weaknesses": [ "Global auto-approve defaults to on in the 1.4.1 source, so tools marked ask (send, trash, delete) run without a prompt. Only financial, approval and budget effects always ask", "The `main` branch has had no commit since 10 September 2026, and open reports filed since mid-September show no replies. 1,363 issues and 183 pull requests are open", "Docs pages for heartbeat, cron, shell and WASM limits name settings such as `HEARTBEAT_ENABLED` and `ALLOW_LOCAL_TOOLS` that do not appear in the 1.4.1 source", "No SECURITY.md, security.txt or published GitHub advisory was found", "The home page lists Discord and Signal integrations, while the channel docs say both are not part of the 1.0 release" ], "agentNotes": [ "Open Settings and turn off global auto-approve, or set send and delete tools to ask each time, before connecting mail or chat accounts", "Install with the release installer and run `ironclaw onboard`. 1.x does not migrate 0.29 data, so use a fresh home directory", "Call `POST /api/v1/responses` with the bearer token from `~/.ironclaw/reborn/webui-token`. Keep under 30 requests in 60 seconds", "Resolve approval and OAuth gates in the web interface. The Responses API fails the turn instead of surfacing them", "Connect MCP servers over HTTP only. The stdio transport is rejected" ], "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": 66.7 } ], "editorialScores": { "ergonomics": 69, "maintenance": 74, "payments": 60, "reliability": 67, "schema": 74, "security": 66, "transparency": 79 }, "provenanceScore": 71 }, "connect": { "install": "IRONCLAW_RELEASE_TAG=ironclaw-v1.4.1\ncurl --proto '=https' --tlsv1.2 -LsSf \"https://github.com/nearai/ironclaw/releases/download/${IRONCLAW_RELEASE_TAG}/ironclaw-installer.sh\" | sh\nironclaw onboard" }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/ironclaw" }, "area": "frameworks", "unitPrices": [ { "item": "Hosted Basic plan (2 agents, $20 credits)", "unit": "month", "usd": 20, "note": "NEAR AI Cloud, per ironclaw.com" }, { "item": "Hosted Pro+ plan (5 agents, $200 credits)", "unit": "month", "usd": 200, "note": "NEAR AI Cloud, per ironclaw.com" } ], "provenance": { "legalEntity": "Jasnah, Inc. d/b/a NEAR AI", "domain": "ironclaw.com", "domainRegistered": "2018-01-04", "endpointOnVendorDomain": null, "terms": "", "privacy": "https://near.ai/privacy-policy", "statusPage": "", "changelog": "https://github.com/nearai/ironclaw/releases", "securityTxt": "none", "checked": "2026-10-12", "notes": [ "The NEAR AI terms of service (updated 24 September 2026) name Jasnah, Inc. d/b/a NEAR AI under Delaware law and cover NEAR AI Cloud and its API. They do not mention IronClaw or agent hosting, so no terms link is set and the MIT or Apache-2.0 licence stands in for the self-hosted software.", "The privacy policy (updated 4 September 2026) lists ironclaw.com, agent.near.ai, the IronClaw framework and IronHub among what it covers.", "The ironclaw.com home page says Built by Near Foundation and its footer says by NEAR AI.", "security.txt answered 404 on www.ironclaw.com, docs.ironclaw.com and near.ai.", "RDAP for ironclaw.com gives a registration date of 2018-01-04 and Cloudflare, Inc. as registrar, last changed 2026-04-20.", "A self-hosted instance answers on its owner's own host. Hosted instances answer at \u003cinstance-id\u003e.agents.near.ai per the quickstart." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/ironclaw.json" }, "facts": [ { "a": "Platform", "b": "Agent harness", "name": "Kind" }, { "a": "SpaceXAI and Cursor (Anysphere, Inc.)", "b": "NEAR AI", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary", "b": "MIT OR Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-09-29", "name": "Last release" }, { "a": "2026-09-03", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-09-29", "b": "no date given", "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": "13k stars", "name": "Popularity" } ], "faq": [ { "answer": "IronClaw scores 66.7 (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 IronClaw?" }, { "answer": "No open-source release is listed for Grok Bot. IronClaw is open source (MIT OR Apache-2.0).", "question": "Are Grok Bot and IronClaw open source?" } ], "goodFor": [ { "aheadOn": null, "also": null, "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, 67 against 40", "Schema \u0026 documentation, 74 against 40", "Agent ergonomics, 69 against 50", "Payments \u0026 pricing, 60 against 25", "Maintenance \u0026 community, 74 against 20", "Transparency \u0026 trust, 75 against 66" ], "also": [ "Open source" ], "goodFor": "One technical owner who wants a self-hosted assistant over Gmail, Calendar, Slack and Telegram with credentials kept out of the model's reach.", "slug": "ironclaw", "watchFor": "Global auto-approve defaults to on in the 1.4.1 source, so tools marked ask (send, trash, delete) run without a prompt. Only financial, approval and budget effects always ask" } ], "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-ironclaw.json", "title": "AstrBot vs IronClaw", "url": "https://www.anchorterminal.com/compare/astrbot-vs-ironclaw" }, { "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-ironclaw.json", "title": "CowAgent vs IronClaw", "url": "https://www.anchorterminal.com/compare/cowagent-vs-ironclaw" }, { "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-ironclaw.json", "title": "GAIA vs IronClaw", "url": "https://www.anchorterminal.com/compare/gaia-vs-ironclaw" }, { "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-ironclaw.json", "title": "Gemini Spark vs IronClaw", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-ironclaw" }, { "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-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-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-ironclaw.json", "title": "Haven vs IronClaw", "url": "https://www.anchorterminal.com/compare/haven-vs-ironclaw" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-ironclaw.json", "title": "Hermes Agent vs IronClaw", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-ironclaw" }, { "json": "https://www.anchorterminal.com/compare/instinct-vs-ironclaw.json", "title": "Instinct vs IronClaw", "url": "https://www.anchorterminal.com/compare/instinct-vs-ironclaw" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-leon.json", "title": "IronClaw vs Leon", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-leon" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-lindy.json", "title": "IronClaw vs Lindy", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-lindy" }, { "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-nanoclaw.json", "title": "IronClaw vs NanoClaw", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-openai-dots.json", "title": "IronClaw vs Dots", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-openai-dots" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-openclaw.json", "title": "IronClaw vs OpenClaw", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-openclaw" }, { "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/ironclaw-vs-poke.json", "title": "IronClaw vs Poke", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-poke" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-qwenpaw.json", "title": "IronClaw vs QwenPaw", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-qwenpaw" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-zeroclaw.json", "title": "IronClaw vs ZeroClaw", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-zeroclaw" }, { "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" } ], "scores": [ { "by": 27, "edge": "ironclaw", "grok-bot": 40, "ironclaw": 67, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 34, "edge": "ironclaw", "grok-bot": 40, "ironclaw": 74, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 19, "edge": "ironclaw", "grok-bot": 50, "ironclaw": 69, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 2, "edge": "grok-bot", "grok-bot": 68, "ironclaw": 66, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 35, "edge": "ironclaw", "grok-bot": 25, "ironclaw": 60, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 54, "edge": "ironclaw", "grok-bot": 20, "ironclaw": 74, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 9, "edge": "ironclaw", "grok-bot": 66, "ironclaw": 75, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "IronClaw scores 66.7 (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.", "ironclaw": "Credentials stay in an encrypted store and are injected at the host boundary, and extensions declare per-tool permissions, network targets and OAuth scopes. The global auto-approve setting defaults to on in the 1.4.1 source, so tools marked ask, such as `gmail.send_message`, run unprompted until the owner turns it off." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw", "json": "https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw.md", "slim": "https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw.min.md" }, "markdown": "IronClaw scores 66.7 (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- IronClaw: grade B, 66.7/100, rank #288 of 986. Markdown https://www.anchorterminal.com/tools/ironclaw.md · JSON https://www.anchorterminal.com/api/v1/tools/ironclaw.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\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### IronClaw (B)\n\nGood for: One technical owner who wants a self-hosted assistant over Gmail, Calendar, Slack and Telegram with credentials kept out of the model's reach.\n\nAhead on:\n- Reliability, 67 against 40\n- Schema \u0026 documentation, 74 against 40\n- Agent ergonomics, 69 against 50\n- Payments \u0026 pricing, 60 against 25\n- Maintenance \u0026 community, 74 against 20\n- Transparency \u0026 trust, 75 against 66\n\nAlso in its favour:\n- Open source\n\nWatch for: Global auto-approve defaults to on in the 1.4.1 source, so tools marked ask (send, trash, delete) run without a prompt. Only financial, approval and budget effects always ask\n\n\n## Score by category\n\n| Category | Weight | Grok Bot | IronClaw | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 67 | IronClaw +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 74 | IronClaw +34 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 69 | IronClaw +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 66 | Grok Bot +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 60 | IronClaw +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 74 | IronClaw +54 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 75 | IronClaw +9 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **45.2 · E** | **66.7 · B** | |\n\n## Facts side by side\n\n| Fact | Grok Bot | IronClaw |\n| --- | --- | --- |\n| Kind | Platform | Agent harness |\n| Vendor | SpaceXAI and Cursor (Anysphere, Inc.) | NEAR AI |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary | MIT OR Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-09-29 |\n| Terms last updated | 2026-09-03 | no document linked |\n| Privacy policy last updated | 2026-09-29 | no date given |\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 | 13k 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**IronClaw.** Credentials stay in an encrypted store and are injected at the host boundary, and extensions declare per-tool permissions, network targets and OAuth scopes. The global auto-approve setting defaults to on in the 1.4.1 source, so tools marked ask, such as `gmail.send_message`, run unprompted until the owner turns it off.\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### IronClaw\n\n1. Open Settings and turn off global auto-approve, or set send and delete tools to ask each time, before connecting mail or chat accounts\n2. Install with the release installer and run `ironclaw onboard`. 1.x does not migrate 0.29 data, so use a fresh home directory\n3. Call `POST /api/v1/responses` with the bearer token from `~/.ironclaw/reborn/webui-token`. Keep under 30 requests in 60 seconds\n4. Resolve approval and OAuth gates in the web interface. The Responses API fails the turn instead of surfacing them\n5. Connect MCP servers over HTTP only. The stdio transport is rejected\n\n## Questions\n\n### Which is better for AI agents, Grok Bot or IronClaw?\n\nIronClaw scores 66.7 (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 IronClaw open source?\n\nNo open-source release is listed for Grok Bot. IronClaw is open source (MIT OR Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw.json, and with the fewest tokens: https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"grok-bot\", \"b\": \"ironclaw\"}`. From a terminal: `anchor compare grok-bot ironclaw`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/grok-bot.json and https://www.anchorterminal.com/api/v1/tools/ironclaw.json\n\n## Other comparisons with Grok Bot or IronClaw\n\n- [AstrBot vs Grok Bot](https://www.anchorterminal.com/compare/astrbot-vs-grok-bot.md)\n- [AstrBot vs IronClaw](https://www.anchorterminal.com/compare/astrbot-vs-ironclaw.md)\n- [CowAgent vs Grok Bot](https://www.anchorterminal.com/compare/cowagent-vs-grok-bot.md)\n- [CowAgent vs IronClaw](https://www.anchorterminal.com/compare/cowagent-vs-ironclaw.md)\n- [GAIA vs Grok Bot](https://www.anchorterminal.com/compare/gaia-vs-grok-bot.md)\n- [GAIA vs IronClaw](https://www.anchorterminal.com/compare/gaia-vs-ironclaw.md)\n- [Gemini Spark vs Grok Bot](https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot.md)\n- [Gemini Spark vs IronClaw](https://www.anchorterminal.com/compare/gemini-spark-vs-ironclaw.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 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 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 IronClaw](https://www.anchorterminal.com/compare/haven-vs-ironclaw.md)\n- [Hermes Agent vs IronClaw](https://www.anchorterminal.com/compare/hermes-agent-vs-ironclaw.md)\n- [Instinct vs IronClaw](https://www.anchorterminal.com/compare/instinct-vs-ironclaw.md)\n- [IronClaw vs Leon](https://www.anchorterminal.com/compare/ironclaw-vs-leon.md)\n- [IronClaw vs Lindy](https://www.anchorterminal.com/compare/ironclaw-vs-lindy.md)\n- [IronClaw vs nanobot](https://www.anchorterminal.com/compare/ironclaw-vs-nanobot.md)\n- [IronClaw vs NanoClaw](https://www.anchorterminal.com/compare/ironclaw-vs-nanoclaw.md)\n- [IronClaw vs Dots](https://www.anchorterminal.com/compare/ironclaw-vs-openai-dots.md)\n- [IronClaw vs OpenClaw](https://www.anchorterminal.com/compare/ironclaw-vs-openclaw.md)\n- [IronClaw vs PicoClaw](https://www.anchorterminal.com/compare/ironclaw-vs-picoclaw.md)\n- [IronClaw vs Poke](https://www.anchorterminal.com/compare/ironclaw-vs-poke.md)\n- [IronClaw vs QwenPaw](https://www.anchorterminal.com/compare/ironclaw-vs-qwenpaw.md)\n- [IronClaw vs ZeroClaw](https://www.anchorterminal.com/compare/ironclaw-vs-zeroclaw.md)\n- [IronClaw vs Zo Computer](https://www.anchorterminal.com/compare/ironclaw-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 IronClaw", "url": "" } ], "description": "IronClaw scores 66.7 (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", "IronClaw B 66.7", "scores" ], "h1": "Grok Bot vs IronClaw", "image": "https://www.anchorterminal.com/assets/og/compare-grok-bot-vs-ironclaw.png", "path": "/compare/grok-bot-vs-ironclaw", "published": "2026-10-01", "section": "tools", "title": "Grok Bot vs IronClaw for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw" }, "tokens": { "markdown": 2600, "slim": 630 }, "version": 1 }