Get an audit

Head to head · Assistant proactive · October 2026 research run

Grok Bot vs NanoClaw

NanoClaw scores 68.3 (B) on agent readiness against Grok Bot's 45.2 (E), and leads in 6 of 7 scored categories. Both do assistant proactive.

Best AI personal assistants that act for one person · All 190 assistants comparisons

Grok BotSpaceXAI and Cursor (Anysphere, Inc.) · Platform E45.2/100#893 of 986 NanoClawNanoCo, Inc. · Agent harness B68.3/100#229 of 986

Which one, for what

Grok Bot E

Best 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.

Also in its favour

  • No incidents deducted, where NanoClaw loses 5 points for them

Watch 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

NanoClaw B

Best for A technical owner who wants an assistant on their own machine, reachable from chat apps, with container isolation and scheduled tasks, and who is willing to keep a fork.

Ahead on

  • Reliability, 78 against 40
  • Schema & documentation, 82 against 40
  • Agent ergonomics, 70 against 50
  • Security & auth, 74 against 68
  • Payments & pricing, 60 against 25
  • Maintenance & community, 78 against 20

Also in its favour

  • No key needed to call it
  • Free to start without a card
  • Open source

Watch for

The Claude provider runs with permissionMode: 'bypassPermissions', so shell, file and web tools run inside the container with no prompt

Score by category

CategoryWeight this runGrok BotNanoClawEdge
Reliability16%204078NanoClaw +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24082NanoClaw +42
Agent ergonomics13%16.25070NanoClaw +20
Security & auth14%17.56874NanoClaw +6
Payments & pricing10%12.52560NanoClaw +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82078NanoClaw +58
Transparency & trust7%8.86665Grok Bot +1
Negative events≤150-5
TotalE 45.2/100B 68.3/100

Facts side by side

FactGrok BotNanoClaw
KindPlatformAgent harness
VendorSpaceXAI and Cursor (Anysphere, Inc.)NanoCo, Inc.
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyNone
PricingPaidFree
x402nono
LicenceProprietaryMIT
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-09
Terms last updated2026-09-03no document linked
Privacy policy last updated2026-09-29no document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularitynone31k stars

Verdicts

Grok Bot

Connector tokens stay on Cursor's backend and each user gets a separate microVM, with approvals, drafts and a review model before risky actions. All of a user's Bots share one computer and its sign-ins, the review model skips memory writes, and the status page shows seven major Grok Bot incidents since 3 September 2026.

NanoClaw

Each session runs in an unprivileged Docker container and API keys stay in a credential gateway on the host, so a manipulated agent cannot read them. Inside the container the agent runs with permission prompts off, network egress is open by default, and it can message any chat it is wired to without approval.

Before you call either

Grok Bot

  1. 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
  2. Add narrow Ask first rules for sending, publishing, purchasing and deleting. Ask first wins over Allow automatically when both match
  3. 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
  4. Run Test run with safe inputs. A test run performs real work and can call connected tools
  5. 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

NanoClaw

  1. Install with git clone and bash nanoclaw.sh. There is no registry package, and setup needs Docker, Node 22 or later and a Claude or Codex credential
  2. Set NANOCLAW_EGRESS_LOCKDOWN=true before giving an agent credentials or an audience of strangers. The default leaves egress open
  3. Put chats with different audiences in separate agent groups. Every session of a group shares one read-write workspace and memory tree
  4. Turn on per-request approval for a secret in the gateway when its use should wait for a person. It is off unless configured
  5. On OneCLI installs, move the gateway to 1.42.0 by the upgrade guide before updating to 2026.10.0. The updater stops until that is done

Questions

Which is better for AI agents, Grok Bot or NanoClaw?

NanoClaw scores 68.3 (B) on agent readiness against Grok Bot's 45.2 (E), and leads in 6 of 7 scored categories.

Are Grok Bot and NanoClaw open source?

No open-source release is listed for Grok Bot. NanoClaw is open source (MIT).

Other comparisons with Grok Bot or NanoClaw

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report