{ "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": "Hermes Agent scores 67.9 (B) on agent readiness against Grok Bot's 45.2 (E), and leads in 6 of 7 scored categories.", "b": { "slug": "hermes-agent", "name": "Hermes Agent", "vendor": "Nous Research", "vendorUrl": "https://hermes-agent.nousresearch.com", "kind": "harness", "category": "personal-assistants", "summary": "Open-source personal agent from Nous Research that the owner runs on a computer or server. It answers on messaging apps, keeps memory between sessions, runs scheduled jobs and connects to accounts, models and MCP servers the owner configures.", "url": "https://www.anchorterminal.com/tools/hermes-agent", "markdownUrl": "https://www.anchorterminal.com/tools/hermes-agent.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hermes-agent.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hermes-agent.json", "repo": "https://github.com/NousResearch/hermes-agent", "license": "MIT", "transports": [], "packages": [ { "registry": "oci", "name": "nousresearch/hermes-agent" } ], "auth": "none", "authNotes": "No account of its own. Model and channel keys go in `~/.hermes/.env` or come from Bitwarden, 1Password or a command helper at start-up. Google Workspace, MCP servers and Nous Portal sign in by OAuth, with tokens stored under `~/.hermes/`. The optional API server takes a bearer key set in `API_SERVER_KEY`.", "pricing": "free", "pricingNotes": "Free under the MIT licence. The owner pays the model provider chosen, or nothing with a local model. Nous Portal plans ($0, $20, $100 and $200 a month in credits) and Hermes Cloud hosting ($0.51 a day running on the Standard size, plus inference) are optional and sold separately.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on Hermes Agent's own interfaces. An optional skill lets the agent pay other services over MPP, which is a client and not a way to pay for Hermes (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 253000, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://hermes-agent.nousresearch.com/docs/", "llmsTxt": "https://hermes-agent.nousresearch.com/llms.txt", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory", "assistant.self-hosted", "agent.mcp-client" ], "tags": [ "open-source", "self-hosted", "local", "free", "no-card", "python", "docker", "llms-txt", "pre-1.0" ], "lastRelease": "2026-10-11", "graded": true, "anchor": { "graded": true, "score": 67.9, "grade": "B", "agentReady": false, "rank": 244, "ranked": true, "rankOf": 986, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 84, "payments": 60, "reliability": 57, "schema": 80, "security": 75, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": -3, "negativeNotes": [ "2026-10-08. The v0.21.6 release notes list six security fixes, among them a native sign-in flaw that could send login codes to a non-loopback redirect and a quoted display name in the `From` header that affected the email gateway's sender check. SECURITY.md counts unauthorised access to an external surface as in scope, yet the repository shows no published advisory, so owners on older versions have no advisory to act on. Fixed and described in the notes, -3. https://github.com/NousResearch/hermes-agent/releases/tag/v0.21.6; https://github.com/NousResearch/hermes-agent/security/advisories" ], "verdict": "Card payments always ask first and are refused in unattended sessions, and the messaging gateway denies every sender until an allowlist is set. Shell commands run on the host by default with a model judging risk, and sending mail through the Google Workspace skill is held back only by an instruction to the model.", "bestFor": "A technical owner who wants one always-on agent across chat apps with memory and scheduled jobs, on their own machine or a small server, with any model.", "strengths": [ "Every saved-card fill asks for approval, and cron, webhook and API sessions are refused because nobody can confirm", "The messaging gateway denies all senders until an allowlist or a pairing code approved on the CLI is in place", "The docs say no telemetry, usage data or analytics is collected, and conversations, memory and skills stay in `~/.hermes/`", "SECURITY.md states that in-process checks are not a boundary and names OS-level isolation as the only one", "Ten releases between 19 August and 11 October 2026, the latest v0.21.7 on 11 October" ], "weaknesses": [ "The default terminal backend runs commands on the host, and the default `smart` mode lets an auxiliary model approve commands it rates low-risk", "The Google Workspace skill requests full Gmail, Calendar and Drive scopes, and its confirm-before-sending rule is an instruction in SKILL.md, not enforced in code", "Memory writes are saved without approval by default (`memory.write_approval: false`), including from a background review after each turn", "Release v0.21.6 of 8 October 2026 lists six security fixes and the repository has no published security advisory", "15,102 open issues and more than 5,000 open pull requests on 12 October 2026", "The Nous Portal terms grant Nous a licence to train models on customer data when the Portal is the model provider" ], "agentNotes": [ "Set `approvals.mode: manual` before giving it real accounts. The default `smart` lets an auxiliary model approve commands", "Run the gateway with `terminal.backend: docker` or the project's Docker image when it reads mail, web pages or group chats", "Set `memory.write_approval: true` and `skills.write_approval: true` to review what it saves about the owner", "Leave `approvals.cron_mode` and `approvals.unattended_mode` at `deny` for scheduled and webhook runs", "Set `TELEGRAM_ALLOWED_USERS` or the matching allowlist per channel. Never set `GATEWAY_ALLOW_ALL_USERS=true`" ], "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": 67.9 } ], "editorialScores": { "ergonomics": 80, "maintenance": 84, "payments": 60, "reliability": 57, "schema": 80, "security": 75, "transparency": 73 }, "provenanceScore": 53 }, "connect": { "install": "curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash # then: hermes setup", "headless": { "command": "hermes chat -q \"$TASK\" --format stream-json --max-turns 30" } }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/hermes-agent" }, "area": "frameworks", "provenance": { "legalEntity": "Nous Research, Inc.", "domain": "nousresearch.com", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/NousResearch/hermes-agent/releases", "securityTxt": "none", "checked": "2026-10-12", "notes": [ "The site footer reads Nous Research, Inc., and the Nous Portal terms name it as a Delaware corporation.", "No terms or privacy link is given. The Nous Portal terms and privacy policy (both dated 28 September 2026) govern the optional Portal and Hermes Cloud services, not the software the owner runs under the MIT licence, so the licence stands in.", "hermes-agent.nousresearch.com/.well-known/security.txt answered 404. SECURITY.md in the repository gives security@nousresearch.com and GitHub private reporting.", "No status page applies to software the owner runs. None was looked for on the Portal.", "The domain registration date was not looked up." ], "score": 53 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/hermes-agent.json" }, "facts": [ { "a": "Platform", "b": "Agent harness", "name": "Kind" }, { "a": "SpaceXAI and Cursor (Anysphere, Inc.)", "b": "Nous Research", "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-11", "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": "253k stars", "name": "Popularity" } ], "faq": [ { "answer": "Hermes Agent scores 67.9 (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 Hermes Agent?" }, { "answer": "No open-source release is listed for Grok Bot. Hermes Agent is open source (MIT).", "question": "Are Grok Bot and Hermes Agent open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No incidents deducted, where Hermes Agent loses 3 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, 57 against 40", "Schema \u0026 documentation, 80 against 40", "Agent ergonomics, 80 against 50", "Security \u0026 auth, 75 against 68", "Payments \u0026 pricing, 60 against 25", "Maintenance \u0026 community, 84 against 20" ], "also": [ "No key needed to call it", "Free to start without a card", "Open source" ], "goodFor": "A technical owner who wants one always-on agent across chat apps with memory and scheduled jobs, on their own machine or a small server, with any model.", "slug": "hermes-agent", "watchFor": "The default terminal backend runs commands on the host, and the default `smart` mode lets an auxiliary model approve commands it rates low-risk" } ], "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-hermes-agent.json", "title": "AstrBot vs Hermes Agent", "url": "https://www.anchorterminal.com/compare/astrbot-vs-hermes-agent" }, { "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-hermes-agent.json", "title": "CowAgent vs Hermes Agent", "url": "https://www.anchorterminal.com/compare/cowagent-vs-hermes-agent" }, { "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-hermes-agent.json", "title": "GAIA vs Hermes Agent", "url": "https://www.anchorterminal.com/compare/gaia-vs-hermes-agent" }, { "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-hermes-agent.json", "title": "Gemini Spark vs Hermes Agent", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-hermes-agent" }, { "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-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-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-hermes-agent.json", "title": "Haven vs Hermes Agent", "url": "https://www.anchorterminal.com/compare/haven-vs-hermes-agent" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-instinct.json", "title": "Hermes Agent vs Instinct", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-instinct" }, { "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/hermes-agent-vs-leon.json", "title": "Hermes Agent vs Leon", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-leon" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-lindy.json", "title": "Hermes Agent vs Lindy", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-lindy" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-nanobot.json", "title": "Hermes Agent vs nanobot", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-nanoclaw.json", "title": "Hermes Agent vs NanoClaw", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-openai-dots.json", "title": "Hermes Agent vs Dots", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-openai-dots" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-openclaw.json", "title": "Hermes Agent vs OpenClaw", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-openclaw" }, { "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/hermes-agent-vs-poke.json", "title": "Hermes Agent vs Poke", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-poke" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-qwenpaw.json", "title": "Hermes Agent vs QwenPaw", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-qwenpaw" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-zeroclaw.json", "title": "Hermes Agent vs ZeroClaw", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-zeroclaw" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-zo-computer.json", "title": "Hermes Agent vs Zo Computer", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-zo-computer" } ], "scores": [ { "by": 17, "edge": "hermes-agent", "grok-bot": 40, "hermes-agent": 57, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 40, "edge": "hermes-agent", "grok-bot": 40, "hermes-agent": 80, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 30, "edge": "hermes-agent", "grok-bot": 50, "hermes-agent": 80, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 7, "edge": "hermes-agent", "grok-bot": 68, "hermes-agent": 75, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 35, "edge": "hermes-agent", "grok-bot": 25, "hermes-agent": 60, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 64, "edge": "hermes-agent", "grok-bot": 20, "hermes-agent": 84, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 3, "edge": "grok-bot", "grok-bot": 66, "hermes-agent": 63, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Hermes Agent scores 67.9 (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.", "hermes-agent": "Card payments always ask first and are refused in unattended sessions, and the messaging gateway denies every sender until an allowlist is set. Shell commands run on the host by default with a model judging risk, and sending mail through the Google Workspace skill is held back only by an instruction to the model." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent", "json": "https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent.md", "slim": "https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent.min.md" }, "markdown": "Hermes Agent scores 67.9 (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- Hermes Agent: grade B, 67.9/100, rank #244 of 986. Markdown https://www.anchorterminal.com/tools/hermes-agent.md · JSON https://www.anchorterminal.com/api/v1/tools/hermes-agent.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 Hermes Agent loses 3 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### Hermes Agent (B)\n\nGood for: A technical owner who wants one always-on agent across chat apps with memory and scheduled jobs, on their own machine or a small server, with any model.\n\nAhead on:\n- Reliability, 57 against 40\n- Schema \u0026 documentation, 80 against 40\n- Agent ergonomics, 80 against 50\n- Security \u0026 auth, 75 against 68\n- Payments \u0026 pricing, 60 against 25\n- Maintenance \u0026 community, 84 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 default terminal backend runs commands on the host, and the default `smart` mode lets an auxiliary model approve commands it rates low-risk\n\n\n## Score by category\n\n| Category | Weight | Grok Bot | Hermes Agent | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 57 | Hermes Agent +17 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 80 | Hermes Agent +40 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 80 | Hermes Agent +30 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 75 | Hermes Agent +7 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 60 | Hermes Agent +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 84 | Hermes Agent +64 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 63 | Grok Bot +3 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **45.2 · E** | **67.9 · B** | |\n\n## Facts side by side\n\n| Fact | Grok Bot | Hermes Agent |\n| --- | --- | --- |\n| Kind | Platform | Agent harness |\n| Vendor | SpaceXAI and Cursor (Anysphere, Inc.) | Nous Research |\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-11 |\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 | 253k 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**Hermes Agent.** Card payments always ask first and are refused in unattended sessions, and the messaging gateway denies every sender until an allowlist is set. Shell commands run on the host by default with a model judging risk, and sending mail through the Google Workspace skill is held back only by an instruction to the model.\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### Hermes Agent\n\n1. Set `approvals.mode: manual` before giving it real accounts. The default `smart` lets an auxiliary model approve commands\n2. Run the gateway with `terminal.backend: docker` or the project's Docker image when it reads mail, web pages or group chats\n3. Set `memory.write_approval: true` and `skills.write_approval: true` to review what it saves about the owner\n4. Leave `approvals.cron_mode` and `approvals.unattended_mode` at `deny` for scheduled and webhook runs\n5. Set `TELEGRAM_ALLOWED_USERS` or the matching allowlist per channel. Never set `GATEWAY_ALLOW_ALL_USERS=true`\n\n## Questions\n\n### Which is better for AI agents, Grok Bot or Hermes Agent?\n\nHermes Agent scores 67.9 (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 Hermes Agent open source?\n\nNo open-source release is listed for Grok Bot. Hermes Agent is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent.json, and with the fewest tokens: https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"grok-bot\", \"b\": \"hermes-agent\"}`. From a terminal: `anchor compare grok-bot hermes-agent`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/grok-bot.json and https://www.anchorterminal.com/api/v1/tools/hermes-agent.json\n\n## Other comparisons with Grok Bot or Hermes Agent\n\n- [AstrBot vs Grok Bot](https://www.anchorterminal.com/compare/astrbot-vs-grok-bot.md)\n- [AstrBot vs Hermes Agent](https://www.anchorterminal.com/compare/astrbot-vs-hermes-agent.md)\n- [CowAgent vs Grok Bot](https://www.anchorterminal.com/compare/cowagent-vs-grok-bot.md)\n- [CowAgent vs Hermes Agent](https://www.anchorterminal.com/compare/cowagent-vs-hermes-agent.md)\n- [GAIA vs Grok Bot](https://www.anchorterminal.com/compare/gaia-vs-grok-bot.md)\n- [GAIA vs Hermes Agent](https://www.anchorterminal.com/compare/gaia-vs-hermes-agent.md)\n- [Gemini Spark vs Grok Bot](https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot.md)\n- [Gemini Spark vs Hermes Agent](https://www.anchorterminal.com/compare/gemini-spark-vs-hermes-agent.md)\n- [Grok Bot vs Haven](https://www.anchorterminal.com/compare/grok-bot-vs-haven.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 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 Hermes Agent](https://www.anchorterminal.com/compare/haven-vs-hermes-agent.md)\n- [Hermes Agent vs Instinct](https://www.anchorterminal.com/compare/hermes-agent-vs-instinct.md)\n- [Hermes Agent vs IronClaw](https://www.anchorterminal.com/compare/hermes-agent-vs-ironclaw.md)\n- [Hermes Agent vs Leon](https://www.anchorterminal.com/compare/hermes-agent-vs-leon.md)\n- [Hermes Agent vs Lindy](https://www.anchorterminal.com/compare/hermes-agent-vs-lindy.md)\n- [Hermes Agent vs nanobot](https://www.anchorterminal.com/compare/hermes-agent-vs-nanobot.md)\n- [Hermes Agent vs NanoClaw](https://www.anchorterminal.com/compare/hermes-agent-vs-nanoclaw.md)\n- [Hermes Agent vs Dots](https://www.anchorterminal.com/compare/hermes-agent-vs-openai-dots.md)\n- [Hermes Agent vs OpenClaw](https://www.anchorterminal.com/compare/hermes-agent-vs-openclaw.md)\n- [Hermes Agent vs PicoClaw](https://www.anchorterminal.com/compare/hermes-agent-vs-picoclaw.md)\n- [Hermes Agent vs Poke](https://www.anchorterminal.com/compare/hermes-agent-vs-poke.md)\n- [Hermes Agent vs QwenPaw](https://www.anchorterminal.com/compare/hermes-agent-vs-qwenpaw.md)\n- [Hermes Agent vs ZeroClaw](https://www.anchorterminal.com/compare/hermes-agent-vs-zeroclaw.md)\n- [Hermes Agent vs Zo Computer](https://www.anchorterminal.com/compare/hermes-agent-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 Hermes Agent", "url": "" } ], "description": "Hermes Agent scores 67.9 (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", "Hermes Agent B 67.9", "scores" ], "h1": "Grok Bot vs Hermes Agent", "image": "https://www.anchorterminal.com/assets/og/compare-grok-bot-vs-hermes-agent.png", "path": "/compare/grok-bot-vs-hermes-agent", "published": "2026-10-01", "section": "tools", "title": "Grok Bot vs Hermes Agent for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent" }, "tokens": { "markdown": 2650, "slim": 680 }, "version": 1 }