Get an audit

Head to head · Assistant proactive · October 2026 research run

Grok Bot vs IronClaw

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.

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 IronClawNEAR AI · Agent harness B66.7/100#288 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.

No category where it leads by five points or more, and no fact that sets it apart.

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

IronClaw B

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

Ahead on

  • Reliability, 67 against 40
  • Schema & documentation, 74 against 40
  • Agent ergonomics, 69 against 50
  • Payments & pricing, 60 against 25
  • Maintenance & community, 74 against 20
  • Transparency & trust, 75 against 66

Also in its favour

  • Open source

Watch 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

Score by category

CategoryWeight this runGrok BotIronClawEdge
Reliability16%204067IronClaw +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24074IronClaw +34
Agent ergonomics13%16.25069IronClaw +19
Security & auth14%17.56866Grok Bot +2
Payments & pricing10%12.52560IronClaw +35
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.82074IronClaw +54
Transparency & trust7%8.86675IronClaw +9
Negative events≤150-2
TotalE 45.2/100B 66.7/100

Facts side by side

FactGrok BotIronClaw
KindPlatformAgent harness
VendorSpaceXAI and Cursor (Anysphere, Inc.)NEAR AI
Hosted endpointno (local only)no (local only)
TransportsHTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietaryMIT OR Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-09-29
Terms last updated2026-09-03no document linked
Privacy policy last updated2026-09-29no date given
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
Popularitynone13k 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.

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.

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

IronClaw

  1. Open Settings and turn off global auto-approve, or set send and delete tools to ask each time, before connecting mail or chat accounts
  2. Install with the release installer and run ironclaw onboard. 1.x does not migrate 0.29 data, so use a fresh home directory
  3. Call POST /api/v1/responses with the bearer token from ~/.ironclaw/reborn/webui-token. Keep under 30 requests in 60 seconds
  4. Resolve approval and OAuth gates in the web interface. The Responses API fails the turn instead of surfacing them
  5. Connect MCP servers over HTTP only. The stdio transport is rejected

Questions

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

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

Are Grok Bot and IronClaw open source?

No open-source release is listed for Grok Bot. IronClaw is open source (MIT OR Apache-2.0).

Other comparisons with Grok Bot or IronClaw

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