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:
- End-user phone/browser (CN network + multiple VPN nodes) — same Failed to fetch
- Cloud assistant browser with the exact full email URL (all query keys intact) — same Failed to fetch
- 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
- Is Failed to fetch on the agentic approval page a known mimir / Cloudflare / geo / CORS issue?
- Required allowlist for agentic-mimir-service from restricted networks (CN + VPN)?
- Supported workaround for Google/email MFA when the hosted approval page cannot fetch mimir?
- 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.)