TL;DR
- On October 14 MetaMask posted that its Agent Wallet is now live on Grok Bot.
- It's a separate wallet for your Bot, not your main one. MetaMask's docs say the default "server wallet" gives your agent "a dedicated wallet without access to your main one."
- Setup is a CLI plus a skill: install
mm, add MetaMask's agent skills, paste one setup prompt. - Guard Mode (recommended) adds allowlists, outflow limits, and your approval when a trade falls outside your rules. Beast Mode has fewer limits.
- MetaMask's quickstart doesn't name Grok Bot in its list of supported agents. I'm going off MetaMask's X post for the Grok Bot part. Start with an amount you can afford to lose.
What happened
Wednesday afternoon, MetaMask posted this:
Short post. It was in my bookmarks the same day, because it's the first time I've seen a big wallet company point straight at Grok Bot.
What the Agent Wallet is
MetaMask's product page calls it "a self-custodial AI trading wallet that lets your AI agent execute all kinds of DeFi trades—swaps, perpetuals, prediction markets, staking, and liquidity provision." It says every supported transaction goes through "transaction simulation, Transaction Shield threat scanning (powered by Blockaid), and MEV protection," and that "malicious transactions are auto-rejected."
Two notes from that same page, since the fine print matters with money:
- It lists simulation as "dry-run simulation (soon)" in one spot, so I wouldn't count on that piece yet.
- Threat scanning "only applies to Blockaid-supported chains," and MetaMask lists those chains on the page.
The key idea is the separate wallet. Your Bot doesn't get your main MetaMask. It gets its own wallet that you fund on purpose.
How setup works
The quickstart is short. You need Node.js 22.18 or later and "an AI agent that supports skills." Then:
1. Install the CLI. npm install -g @metamask/agent-wallet@latest. The mm CLI is "how your agent signs in, checks balances, and sends transactions." 2. Add the skills. npx skills add MetaMask/agent-skills, then pick metamask-agent-wallet. MetaMask says skills teach your agent "which mm commands to run and when to ask for your confirmation before moving funds." 3. Paste the setup prompt: "Set up MetaMask Agent Wallet: help me pick a sign-in method, wallet mode, and trading mode, then show my address." 4. Sign in. Google, email, or a QR code with MetaMask Mobile. 5. Pick a wallet mode. Server wallet (most people) or bring your own wallet. 6. Pick a trading mode. Guard or Beast. 7. Fund it from another wallet or exchange.
This fits how Grok Bot works. Each Bot has a cloud computer with "a browser, filesystem, and terminal" (Grok Bot docs), so it can run the install itself. You can just hand it the quickstart link and the prompt.
One gotcha MetaMask calls out: "Pick one sign-in method and keep using it." Google, email and QR "each one loads a different wallet address, even if you use the same email." Pick one and write it down.
Guard Mode vs Beast Mode
From the quickstart:
- Guard Mode (Recommended): "Allowlists, outflow limits, and your approval when a transaction falls outside your policy."
- Beast Mode: "Power users who want fewer limits. Malicious transactions still need your approval."
MetaMask also says "your agent should ask you rather than choose for you." If your Bot picks a mode without asking, stop and redo that step.
When a trade needs your OK, Google or email users get an email with an approve or reject link. QR users get a request in MetaMask Mobile's notifications menu (quickstart).
I'd start in Guard Mode. No contest.
What I couldn't verify
Being straight about it:
- MetaMask's quickstart names Claude Code, Codex, Cursor, OpenClaw and Hermes Agent "or similar." It doesn't name Grok Bot. The Grok Bot claim comes from MetaMask's X post.
- I didn't find a Grok Bot docs page about the Agent Wallet, and I didn't find it listed in the x.ai Marketplace.
- I haven't funded one myself. Nothing here is a report on how well it trades.
None of that means it doesn't work. It means check before you trust it.
Two layers of approvals
The part I like is that you get two sets of brakes.
MetaMask's Guard Mode is one. Grok Bot's own approvals are the other. The Grok Bot security docs list "purchases and financial transfers" as something to put behind an explicit boundary, and they say to "keep sending, publishing, purchasing, deletion, and production changes behind approval."
Grok Bot's Auto-review also lets you add an "Ask first" rule, and the docs say "if both kinds of rule match, Ask first wins." An "Ask first before any wallet transaction" rule is a cheap seatbelt.
Two more lines from those docs worth knowing before you do this:
- Your Bots share one computer, and "files, browser sessions, and command line credentials on that computer are available across your Bot roster." If the
mmCLI is signed in, assume every Bot you run can reach it. The docs say plainly: "Do not use separate Bots as a security boundary." - For passwords, codes and payment confirmations, "the Bot should hand you control of the computer." Don't paste a seed phrase into chat. If you go the bring-your-own-wallet route, think hard about it first.
How I'd start
1. Fund it with lunch money. Small enough that a bad trade is a lesson, not a loss. 2. Guard Mode, tight limits. Low outflow limit, short allowlist. 3. Add a Grok Bot boundary in the request, like this:
> Set up MetaMask Agent Wallet using the quickstart at docs.metamask.io/agent-wallet/quickstart. Use a server wallet and Guard Mode. Ask me before choosing anything. After setup, you can check balances and show me quotes, but don't send any transaction without my OK.
4. Watch a week of quotes before letting it trade. Read-only first, the same way I'd start any new Bot. 5. Sign out when you're done with it. The docs say to "sign out of a service when it should no longer be available."
Bottom line
A Bot with its own wallet and hard limits is a real step up from pasting keys into scripts. MetaMask did the sensible thing by making it a separate wallet with an approval path. Keep the amount small, keep Guard Mode on, and keep your own hand on the approve button.