Copilot in Microsoft Edge is the AI assistant built into Microsoft's browser, and its agent feature, now called Browse with Copilot, can click, type and navigate websites inside the user's own Edge window to finish multi-step tasks. The feature has changed names three times in a year. Microsoft launched Copilot Mode as an experimental, opt-in mode for Windows and Mac on Jul 28, 2025, released Copilot Actions as a free US preview on Oct 23, 2025, and on May 13, 2026 retired Copilot Mode and renamed Copilot Actions to Browse with Copilot.
Today Browse with Copilot is limited to Microsoft 365 Premium subscribers in the US on Edge desktop, plus a business preview for Microsoft 365 Copilot tenants outside the EEA that only browses domains an admin allows. Microsoft hasn't published usage numbers. Typical tasks are restaurant reservations, unsubscribing from newsletters, comparing products across tabs and shopping up to checkout, which puts it on restaurant, ecommerce, travel and SaaS sites, and because it reuses the user's cookies, those sessions arrive already signed in.
How Copilot in Edge shows up on your site
Microsoft says every Browse with Copilot action runs locally in the user's Edge, in the current window, in a tab marked with a cursor icon. It reuses the profile's cookies, so the user is signed in to your site already, but it can't read autofill, saved passwords or wallet data and asks the person to enter personal or payment details. Microsoft documents no user agent token, request signature or IP list for these actions, so the request your server sees is a normal Edge request from the user's home or office network.
| Check | What Copilot in Edge does |
|---|---|
| User agent | Normal Edge, with no Copilot token |
| Web Bot Auth signature | None documented |
| IP ranges | None, traffic uses the user's own IP |
| robots.txt | Not documented |
Why Copilot in Edge is hard to detect
The browser is real, signed in and on the account holder's own network, so cookie, IP and device checks all point at a trusted returning customer. The Edg/ token in the user agent tells you the visitor uses Edge, which millions of people do without any agent involved, and Microsoft documents nothing that separates the agent's clicks from the person's.
That leaves behavior. In studies of other Chromium agents, researchers at UC Davis separated agents from people by looking for missing mouse movement, fields filled instantly and paste events in place of typing. Their FP-Agent study did not test Edge, so those traits are a reasonable starting point rather than a proven fingerprint for Copilot. The repeated renaming adds a practical problem too, because the same traffic is described in different places as Copilot Mode, Copilot Actions or Browse with Copilot.
How Verisoul detects Copilot in Edge
Verisoul does not name Copilot in Edge yet, because Microsoft gives it no declared identity or signature we can verify. When Copilot takes over, Verisoul reads the automated clicks, typing and page flow in the session, and those raise the bot score while the agent field stays empty. The device and network look like the customer's own, since they are, which is why the score depends on behavior here.
"agent": nullbot_scoreruns from 0 to 1 and rises as the session looks automated, so 0.97 means the input and page flow look like softwareagentisnullbecause Copilot in Edge does not declare or sign an identity, so Verisoul does not attach a name- The device is the user's own Edge and the IP is their own network, so neither raises the score on its own
If Microsoft adds a declared identity, Copilot in Edge will get its own entry in Agent Atlas. The AI agent detection docs explain how bot score and the agent field fit together.
- 01User asks Copilot to book a table
- 02Copilot acts in their signed-in Edge tab
- 03It pauses before the booking is confirmed
- 04Your site sees Edge on a home IP
How to detect Copilot in Edge step by step
- Add the Verisoul SDK to login, booking, checkout and account pages, following the AI agent detection docs
- Flag sessions on known accounts where
bot_scoreis high andagentis null, which is where Copilot sessions land - Route payouts and account detail changes in those sessions to review
- Leave browsing and booking flows open and check the review queue weekly to tune the threshold
Should you block Copilot in Edge?
Most teams shouldn't. Browse with Copilot runs in the real account holder's signed-in Edge, and Microsoft makes it pause for the person before buying, booking, sending email or deleting calendar events. Blocking it mostly turns away paying customers who asked Microsoft's assistant to save them a few clicks.
Review is still worth it on payouts and account changes, where an automated session on a trusted account can do real damage if something has gone wrong. Companies that want to limit where their own employees' Copilot can browse can do that with Edge's BrowsingWithCopilotAllowList and BrowsingWithCopilotBlockList policies, though those are admin controls for the browser side, not tools a website can use.