The future is here. MetaMask Agent Wallet, which reached general availability on August 6, 2026, gives an AI agent its own self-custodial wallet, lets that agent trade on your behalf, and keeps every action inside limits you set before the agent starts working.

That distinction between an agent acting and an agent having full access matters more than it might sound like at first. It’s also the same question we ran into when covering agentic wallets more broadly, how much autonomy a piece of software should actually get, and what happens when every provider draws that line differently.

Key Takeaways

  • MetaMask Agent Wallet moved from a roughly 200-person early access group in June to general availability on August 6, 2026, a two-month gap that let the team test the security model before opening it to everyone.
  • The wallet is self-custodial: users hold their own keys and can export their Secret Recovery Phrase at any time, the agent never takes custody.
  • Two operating settings, Guard Mode and Beast Mode, control how much an agent can do before a human has to approve a transaction manually.
  • Eligible transactions get up to $10,000 a month in Transaction Protection, but only if they already passed MetaMask’s simulation and threat-scanning checks and still resulted in a loss.
  • Agents connect through a command-line interface rather than a browser extension, which tells you who this is actually built for right now.

What Is MetaMask Agent Wallet

MetaMask Agent Wallet is a self-custodial wallet built specifically for AI agents. It connects to agent frameworks like Claude Code, Codex, and Cursor through a command-line interface, letting an agent monitor markets and execute trades while staying inside spend limits, allowlisted protocols, and risk settings the user defines in advance.

Nothing about that setup hands an agent your existing MetaMask wallet. It gets its own, created specifically for this purpose, and every transaction it attempts still has to clear the same security pipeline MetaMask uses for regular wallets, transaction simulation, threat scanning, MEV protection, before it lands on-chain.

Consensys, the company behind MetaMask, built the product for traders and developers already comfortable working in a terminal rather than clicking through a browser popup, which is a narrower audience than MetaMask’s usual base.

Roughly 200 people got access during the early access phase that opened June 8, 2026. General availability followed two months later, on August 6.

How an AI Agent Gets Its Own Wallet

MetaMask Agent Wallet gets a separate, self-custodial wallet created specifically for it, with its own keys and its own Secret Recovery Phrase, one you can export at any time.

That separation is the actual security design. If an agent’s wallet gets compromised or misused, whatever’s exposed is limited to what you funded that specific wallet with, not your full portfolio sitting somewhere else in MetaMask.

The agent connects through a command-line interface rather than a browser extension. Once connected, an agent can prepare transactions, batch swaps using ERC-7821, and execute trades across HyperLiquid and supported EVM chains including Robinhood and Monad. It can also do this without holding a chain’s native token for gas. MetaMask settles the network fee directly in whatever token the agent is moving, removing a step that trips up a lot of automated trading setups.

Guard Mode and Beast Mode

MetaMask Agent Wallet ships with two operating settings, Guard Mode and Beast Mode, and the difference between them is how often a human gets pulled in before a transaction executes.

Guard Mode is the default version. Spend limits and allowlisted protocols stay enforced strictly, and anything outside that policy pauses and waits for two-factor approval through MetaMask Mobile or an email link.

Beast Mode loosens that up for users who don’t want to keep approving routine actions. Even in Beast Mode, the security checks don’t turn off. A transaction that looks malicious still gets stopped and sent back to you, no matter which mode you’re running.

It comes down to how much you want to be asked before something happens. Guard Mode checks in more often. Beast Mode figures you already made those calls when you set the rules.

What Protects a Transaction Before It Executes

Every supported transaction in MetaMask Agent Wallet passes through the same security pipeline before it lands on-chain, and each layer catches something different.

Transaction simulation runs first, showing what a transaction is expected to do, balance changes, approvals, gas routing, before anything gets signed. Threat scanning comes next, powered by Blockaid and tested across millions of MetaMask transactions, flagging malicious activity before it reaches the user. MEV protection handles a separate problem entirely, keeping a transaction from leaking value to bots watching the mempool for opportunities to front-run it.

These layers are a part of the same security model the wallet already applies to manual transactions. What’s different here is that an agent, not a person, is the one initiating actions, so the checks matter more, not less.

For transactions that clear all three checks and still result in a loss, MetaMask offers Transaction Protection coverage up to $10,000 per month. That coverage has real conditions attached: the transaction has to have already passed simulation, threat scanning, and MEV protection. It’s not a blanket insurance policy against bad trades, it covers the specific case where the security pipeline did its job and something went wrong anyway.

$10,000 a month. That’s the ceiling on Transaction Protection, and it only applies to transactions that already passed every security check MetaMask runs. A trade an agent made outside your policy, or one flagged and pushed through anyway, isn’t what this covers.

Two months between early access and general availability is a short window for a product that hands execution authority to AI agents. It suggests MetaMask spent that time watching how real users actually used it, not just hitting a launch date.

Whether this exact model, self-custodial plus rules-based execution, becomes how most agentic wallets get built is still an open question. But MetaMask just gave the rest of the industry a real, working example to react to.

So, congrats on the launch! MetaMask is doing the heavy lifting right now reshaping and improving crypto space for users.

At Evercode Lab, we build white label crypto wallets for businesses that want that kind of functionality without starting from scratch, custody model, security pipeline, and permission architecture included from day one. If you’re exploring what a feature like this could look like in your own wallet product, we’re happy to talk through what that would actually take to build.

FAQ

When did MetaMask Agent Wallet launch?

General availability began August 6, 2026, following an early access phase that opened to roughly 200 traders and developers on June 8.

Is MetaMask Agent Wallet self-custodial?

Yes. Users hold their own keys and can export their Secret Recovery Phrase at any time. The agent operates its own separate wallet, it never takes custody of the user’s main funds.

What’s the difference between Guard Mode and Beast Mode?

Guard Mode is the default and pauses for two-factor approval whenever a transaction falls outside the user’s spend limits or allowlisted protocols. Beast Mode reduces how often that approval step interrupts the agent, though flagged or malicious transactions still get blocked either way.

Which AI tools does MetaMask Agent Wallet support?

Claude Code, Codex, Cursor, OpenClaw, Hermes, and OpenCode, connecting through a command-line interface rather than a browser extension.