Agent Wallet CLI 7.3.0: policy HTTP 500 and trading-mode HTTP 404 with successful exit

Hello MetaMask Agent Wallet team. I need help diagnosing an existing server wallet without creating a new wallet or overwriting its current policy.

Environment: @metamask/agent-wallet 7.3.0, macOS. Observed October 28, 2026.

Local authentication and initialization checks succeeded, and wallet identity matched the expected existing wallet. However:

  • mm wallet policy get --json: underlying policy GET returned HTTP 500; CLI exited 0 with empty policy output.
  • mm wallet trading-mode get --json: underlying mode GET returned HTTP 404; CLI exited 0 with mode:null.

HTTP status was captured using a diagnostic wrapper that reported only endpoint category and response status, without logging headers, credentials, URLs, or response bodies. Installed source catches policy-fetch exceptions and returns an empty string; the mode reader can return null after an exception. We therefore treat the policy and mode as UNKNOWN, not confirmed absent.

Trading is paused. No policy/mode changes or transactions were performed during these checks.

Is this a known version/API compatibility issue? What supported diagnostic or fix can restore reads for the existing wallet while preserving its policy? If account-specific details are needed, please provide an official private support channel.

This report intentionally excludes tokens, wallet addresses, project identifiers, and raw logs.

Update: I also tested my original CLI login token in a separate local session directory, without replacing the current login. The local login helper reported success based on the CLI login result, but the subsequent auth status --json returned authenticated: false. Wallet address, policy, and trading-mode checks then exited with code 1. This attempt did not restore access; the cause has not been established.

My immediate priority is recovering access to the existing server wallet so I can withdraw my USDT and excess native BNB on BNB Chain to my own wallet. Please provide a supported recovery or withdrawal procedure, or an official private escalation channel. Trading remains paused; no funds were moved and no policy was changed during these tests.

No tokens, wallet addresses, project identifiers, or raw logs are included here.

Further diagnostic update: a freshly issued CLI token now returns authenticated: true. In a separate local test session, after copying the existing wallet selection and local walletMode/tradingMode metadata (without changing any server policy), wallet address --json succeeds and matches the existing wallet.

The underlying read requests still return HTTP 500 for policy and HTTP 404 for trading mode. Both CLI wrappers exit 0 despite those HTTP failures. A fresh authenticated login therefore has not resolved these errors; the permission state remains unknown.

Please advise on restoring access to this existing wallet or a supported withdrawal procedure for USDT and native BNB on BNB Chain, preferably through an official private support channel. Trading remains paused; no new wallet was created, no server policy was changed, and no transfers were submitted during these tests. No tokens, wallet addresses, or project identifiers are included.

Hi, I’m Hieu from the Agent Wallet team. Are you still seeing this?

Your policy stays on the server. Logging out only clears this CLI session. It does not change the policy or move funds.

Please run mm logout, then mm login. Login syncs your server wallet and trading mode locally. If login says the project is not set up, run mm init and choose server-wallet. Do not choose BYOK.

Then run these and send the output with the address and project id removed:

mm wallet address --json
mm wallet policy get --json -v
mm wallet trading-mode get --json -v

If the policy is still empty or the trading mode is still null, stop there. Please don’t create a new wallet or run mm wallet policy set.