Feature Request: Expose a Versioned UI State API in Microsoft Edge for AI Agent Integration

I'm submitting this to the Tech Community to amplify a formal Feature Change Request (FCR) already on record with the Microsoft Edge product team via the official Feedback Portal — where it has already moved to "We're Reviewing This" status within 48 hours of submission (September 16, 2026).

The core problem: Microsoft Edge does not expose its live UI state to AI agents — including Microsoft's own Copilot. This forces agents to generate step-by-step instructions based on stale training data, guessed UI layouts, and cached assumptions. The result is real, visible, recurring failure: instructions referencing moved menus, renamed paths, occluded click targets, and frozen containers that agents cannot detect.

Three concrete Feature Change Requests are on the table:

FCR-001 — Versioned UI State API

Edge should expose a versioned, permissioned browser-side API (e.g., a Manifest v3 edgeUIState permission + browser.edgeUI.getSnapshot() method) that allows approved agents to query live UI layout metadata — control labels, element positions, sidebar geometry, overlay presence, and container status. Versioned so agents can declare compatibility ranges and degrade gracefully across Edge update cycles.

FCR-002 — Container & Overlay Awareness

Edge should surface a lightweight heartbeat signal (~500ms) to credentialed agent sessions covering: container responsive/frozen state, sidebar bounding rectangle in viewport-relative coordinates, and full or partial overlay presence. This directly resolves Copilot sidebar occlusion failures and Application Guard container freeze blindness.

FCR-003 — Official UI-Check Protocol Specification

Microsoft should publish and maintain a formal specification defining when and how Edge-integrated AI agents are required to perform a live UI check before generating user-facing instructions — including required fallback behavior and disclaimer language when live UI data is unavailable. Published alongside WebView2 and extension API references, with a named owner and versioned changelog.

Why this matters right now:

These failures occur in standard Edge configurations and are disproportionately likely during AI-assisted task flows — precisely because those flows involve the Copilot sidebar being open. Single-agent failure is a user frustration. Systemic agent failure across every Edge user running Copilot is a platform trust problem.

Feedback Portal submission (status: We're Reviewing This):

https://feedbackportal.microsoft.com/feedback/idea/e3dfa689-02b2-f111-aad1-000d3a02f23c

If this resonates with your workflow or development experience — please upvote, comment, and share. The more traction this gets in the community, the stronger the signal to the product team that this is a priority worth accelerating.

— CA_MGooGG | Chicago, IL | September 18, 2026