Who we are / context
Ember (building VibeKit/Ember Vaults) is preparing a demo where a user upgrades an EOA to a smart account and authorizes a constrained “agent signer” (our automation) to execute specific, policy-bound actions. We’ve been using MetaMask Delegation Toolkit and built this on the backend without issue. When doing QA for the frontend, we ran into issues.
Goal (what we need to accomplish)
- User can upgrade EOA → smart account (EIP-7702 flow) prompted by dapp.
- User can approve a constrained delegation to a signer (agent) with caveats
- User can revoke or rotate that delegated signer cleanly.
- (Nice-to-have) clarity on chaining / re-delegation semantics and safe patterns.
Current blockers / what we observe
- Client-side delegation signing appears disabled in MetaMask client, so a dapp cannot complete a delegation approval UX.
- EIP-7702 authorization/upgrade prompts from a dapp also appear client-disabled.
We’d like confirmation and recommended workarounds/roadmap.
Questions
- Are 7702 upgrade prompts disabled for the MetaMask client?
- Is delegation signing intentionally disabled in the MetaMask client atm?
- If so, can it be enabled (flag, build, allowlist) for partner demos? Any short-term workaround you recommend?