Agent Wallet MFA page Failed to fetch mimir (Google social) — need official fix

Environment

  • Product: MetaMask Agent Wallet (server wallet), Guard Mode
  • CLI: metamask agent-wallet package 7.3.0 (mm doctor authenticated + initialized)
  • Sign-in / authMethod: social (Google / browser dashboard) — NOT MetaMask Mobile QR
  • Wallet (truncated): 0x0f5a…1297 on BSC (eip155:56)
  • Approval emails arrive from no-reply-developer to the dashboard Gmail
  • Hosts (written to avoid auto-link): developer DOT metamask DOT com /agentic/approval ; agentic-mimir-service DOT api DOT cx DOT metamask DOT io

Symptom
When Guard Mode swap/approve pauses with AWAITING_MFA (authMethod=social), the approval email opens the agentic approval page with approvalId, projectId, mimirSignature, subjectId, operationType.

The page shows only: Failed to fetch (agentic-mimir-service)

  • No Approve / Reject buttons, no amount/intent, no Google login wall, no missing-params error
  • Request expires in about 10 minutes while we cannot approve

Reproduces on:

  1. End-user phone/browser (CN network + multiple VPN nodes) — same Failed to fetch
  2. Cloud assistant browser with the exact full email URL (all query keys intact) — same Failed to fetch
  3. Turning off “route browser via user computer” does not fix the assistant browser case

Console (Chromium): CORS / no Access-Control-Allow-Origin for agentic-mimir-service; net::ERR_FAILED.

Server contrast (same machine, curl not browser):

  • GET root of agentic-mimir-service → HTTP 200 JSON product MetaMask Agentic Mimir API
  • With Origin set to the developer metamask site: still cross-origin-resource-policy same-origin and no access-control-allow-origin
  • OPTIONS preflight: allow-methods/headers but no access-control-allow-origin in headers we receive

Ruled out

  • Incomplete URL / missing projectId; full email URL still fails
  • Wrong wallet: Mobile QR/App notifications bind a different empty address; we stay on Google/email social for 0x0f5a…1297
  • CLI health OK; mm wallet requests list shows AWAITING_MFA then EXPIRED
  • Docs path followed: Agent Wallet “Approve requests” (email link for Google/email)

Ask

  1. Is Failed to fetch on the agentic approval page a known mimir / Cloudflare / geo / CORS issue?
  2. Required allowlist for agentic-mimir-service from restricted networks (CN + VPN)?
  3. Supported workaround for Google/email MFA when the hosted approval page cannot fetch mimir?
  4. Can engineering check recent expired approvalIds that only showed Failed to fetch client-side (example subjectId 52800983-b908-40ea-bd9e-7ee1d6f146b1 on 2026-11-04 about 14:50 UTC)?

Happy to provide HAR/screenshots/CLI NDJSON privately to staff. Please do not ask for seed phrases or private keys (none; server wallet).

(No outbound links in this post — new-user link limit. Staff can ask and I will paste docs URLs in a follow-up reply.)

Update / root cause (Ticket 152591398)

Agent Wallet Guard MFA Approve page still shows Failed to fetch for Google/social login on wallet 0x0f5a5f3159b102467642e942f32ebbc324891297.

Evidence (2026-11-05):

  1. Curl/CLI to agentic-mimir-service.api.cx.metamask.io returns HTTP 200.
  2. Browser Approve page (developer.metamask.com / agentic approval) cannot read mimir responses.
  3. Response headers include cross-origin-resource-policy: same-origin and no Access-Control-Allow-Origin. Chromium console: net::ERR_FAILED / CORS.
  4. authMethod=social (email Approve). Mobile QR login is a separate auth path and creates a different server wallet — it does not migrate this funded address and does not fix email MFA.
  5. Switching Guard→Beast and policy edits also require the same MFA Approve, so those are blocked too.
  6. Fresh stop-loss Approves (AKE / JAGENT) still expire because the Approve UI cannot load.

Please escalate to Agent Wallet / mimir: allow the approval origin to read mimir (CORS + CORP), or provide an official same-address Approve path for Google/social that does not depend on this broken fetch.

Needed outcome: email Approve works again on the existing wallet address above.

Update from MetaMask Support email (Masa / support@metamask.io):

They confirmed Agent Wallet is a separate product and regular Support does not handle it. They redirected us here to Builder Hub for the developer team.

Issue is still open on wallet 0x0f5a5f3159b102467642e942f32ebbc324891297 (Guard, authMethod=social/Google):

  • MFA Approve page Failed to fetch
  • agentic-mimir-service.api.cx.metamask.io returns HTTP 200 via curl/CLI, but browser cannot read it (cross-origin-resource-policy: same-origin, no Access-Control-Allow-Origin, net::ERR_FAILED / CORS)
  • QR / MetaMask App login creates a different empty server wallet and does not migrate this funded address

Please escalate to Agent Wallet / mimir engineering so email Approve works again on this existing address. Happy to provide HAR/console traces if useful.

Thank you.