Description

MetaMask CLI / developer-dashboard flows need users to approve sensitive operations (login, wallet mode changes, transaction requests) on mobile. This PR wires https://link.metamask.io/agentic-cli universal links into a modal WebView that completes the hosted dashboard MFA flow while keeping auth tokens and navigation inside an allowlisted origin policy.

Flow

1. Deeplink — ACTIONS.AGENTIC_CLI is registered in universal-link handling (whitelisted, no interstitial). handleAgenticCliApproval parses query params (projectId, approvalId, optional approvalPagePath, mimirSignature, operationType, subjectId), validates paths under /agentic/…, and navigates to Routes.AGENTIC_CLI_APPROVAL.CONFIRM after a short settle delay (same pattern as other pending deeplinks).
2. Auth — AgenticCliApprovalService selects the dashboard host from build type (test / dev / prod Web3Auth or developer.metamask.io), exchanges the wallet Hydra bearer via mm-qr-login/token, and loads the page with approval query params plus #auth_token=… in the URL fragment (not sent on the HTTP request).
3. WebView — Allowlisted origins only (dashboard hosts, Web3Auth auth, Stripe embeds, MetaMask auth APIs). Disallowed top-frame URLs open in the OS browser; subframes are blocked without external open. The screen listens for mm-cli-mfa postMessages (approved / rejected / close / error), matches approvalId to route params, and shows localized load/submit errors with retry.

Notable details

• Dashboard host is always chosen on-device; deeplink may only override approvalPagePath (default /agentic/login).
• mimirSignature is read from the raw query string so literal + in base64-style signatures are not converted to spaces; percent-encoded values are still decoded.
• getBuildType() is exported for host selection; unit tests cover service, screen, and deeplink handler.

Changelog

CHANGELOG entry: Added mobile WebView approval for MetaMask CLI requests opened via agentic-cli universal links.

Related issues

Fixes:

Manual testing steps

Feature: Agentic CLI approval deeplink

  Scenario: user approves a CLI request from a universal link
    Given the user is onboarded, vault unlocked, and signed in (Hydra bearer available)
    And a dev/UAT/prod build matching the target dashboard host

    When the app is opened via a link such as:
      https://link.metamask.io/agentic-cli?projectId=<id>&approvalId=<id>&mimirSignature=<sig>
      (optional: approvalPagePath=/agentic/approval, operationType, subjectId)
    Then the Agentic CLI approval modal opens
    And the WebView loads the hosted login/approval page with auth in the fragment
    And approving on the hosted page closes the modal (postMessage `approved` + matching approvalId)

  Scenario: user rejects or closes the hosted flow
    Given the approval modal is open
    When the hosted page posts `rejected` or `close`
    Then the modal closes without treating it as a load failure

  Scenario: disallowed navigation is blocked or opened externally
    Given the approval WebView is loaded
    When a top-frame navigation targets a non-allowlisted origin
    Then it opens in the system browser instead of the WebView

Suggested deeplink (adjust host/build):

https://link.metamask.io/agentic-cli?projectId=<projectId>&approvalId=<approvalId>&mimirSignature=<signature>

Screenshots/Recordings

Before

N/A — feature not present on main.

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.