Microsoft is rolling out a change to its Copilot app on Windows that embeds web browsing directly inside the AI assistant, opening clicked links in a side pane next to the chat rather than launching a separate browser window. The update is available now to Windows Insiders running Copilot version 146.0.3856 or later. It is a small but telling design shift that raises a practical question: does stuffing a browser into an AI chatbot actually help users, or does it just keep them locked inside Microsoft’s ecosystem?
What the Update Actually Does
Until now, clicking any link in a Copilot conversation would bounce users out to their default browser, breaking the flow of whatever task they were working on. The new behavior keeps that content inside the app. When a user clicks a link, the web page opens in a side pane alongside the conversation, so the AI chat and the referenced content sit next to each other on screen. The idea is straightforward: if Copilot cites a source or suggests a link, users can read it without losing their place in the dialogue.
The rollout is limited for now, reaching only Windows Insiders rather than the general public. According to Microsoft’s announcement for testers, the change is starting with Copilot version 146.0.3856 and later, which means the company is treating this as a trial balloon rather than a finished feature. For the average Windows user who has never opted into the Insider program, nothing changes yet. But the direction is clear: Microsoft wants Copilot to handle more of the browsing workflow internally, reducing the reasons a user might switch to a standalone browser tab and giving the company a chance to refine the experience before it lands on millions of machines.
The Browser Engine Hidden Under the Hood
The side pane is not a stripped-down HTML viewer. It runs on Microsoft’s WebView2 framework, which uses the same Chromium-based Edge rendering engine that powers a full desktop browser. WebView2 lets apps embed complete web content, including JavaScript, CSS, and modern page layouts, inside their own interface without opening a separate browser process. That means the pages users see in Copilot’s side pane should look and behave the same way they would in Edge or Chrome, from responsive layouts to interactive widgets, as long as the site itself supports them.
This is not a new technology. WebView2 has been available to Windows developers for several years, and it already underpins embedded web views in apps like Microsoft Teams, Office components, and various third-party tools. Microsoft’s Windows App SDK 1.6 documentation explains how developers can bundle specific WebView2 versions with their apps, giving them control over which browser engine build they target and how often it updates. For Copilot, this means Microsoft can ship browser-grade rendering without asking users to install anything extra or manage another application. The plumbing was already in place; this update simply surfaces it as a user-facing feature, turning what used to be a background component into a visible part of the Copilot workflow.
Convenience Gains and Missing Controls
For casual users who treat Copilot as a research companion, the change removes a genuine friction point. Consider a common scenario: a user asks Copilot to summarize recent news about a topic, and the AI returns a response with several citation links. Previously, clicking any of those links meant opening a new browser tab, reading the article, then switching back to Copilot to continue the conversation. Now that round trip happens in a single window. The chat stays visible on one side while the linked page loads on the other, making it easier to quote, cross-check, or ask follow-up questions based on what appears in the pane. For quick fact-checking or skimming a source, that split-screen approach saves time and mental context-switching.
The tradeoff, though, is that a WebView2 pane is not a full browser. Users accustomed to tabbed browsing, bookmarks, extensions like ad blockers, or developer tools will not find those features in Copilot’s side pane. There is no address bar for navigating to a different site, no way to open multiple tabs within the pane, and no access to the browser extension ecosystem that many people rely on daily. Even simple habits, like quickly copying a URL from the address bar, dragging a tab into a new window, or using a password manager extension, are off the table. For anyone who needs to do more than glance at a single linked page, the embedded view will feel limited. The feature works best as a quick-look tool, not as a replacement for a real browser session, and users who expect browser-level control may find themselves bouncing back to their default browser more often than Microsoft might prefer.
A Pattern Across Microsoft’s Product Strategy
This update fits a broader pattern in how Microsoft is building its AI products. Over the past year, the company has steadily expanded what Copilot can do without requiring users to leave the app. The assistant already handles text generation, image prompts, and conversational search, and it is increasingly woven into Windows itself as a first-stop interface for everyday tasks. Adding in-app web browsing is the next logical step in turning Copilot into a self-contained productivity surface. The goal appears to be reducing the number of separate tools a user needs open at any given time, concentrating attention inside Microsoft’s own interface and making Copilot feel less like a bolt-on chatbot and more like a core part of the operating system.
That concentration of function is worth scrutinizing. Every feature that keeps users inside Copilot is also a feature that keeps them away from competing browsers and search engines. If users can read web content without ever opening Firefox, Chrome, or even a standalone Edge window, their browsing activity flows through Microsoft’s app layer instead. This does not mean the feature is cynical by design, but it does mean the convenience argument and the platform-lock-in argument point in the same direction. Over time, if more workflows (from document editing to web research) are mediated through Copilot panes rather than independent apps, Microsoft gains more leverage over defaults, data flows, and how search results are presented, even as users enjoy the reduced friction of staying in one place.
Who Benefits and Who Should Wait
The practical value of this feature depends heavily on how someone uses Copilot. For light research tasks, quick link previews during a conversation, or verifying a claim the AI made, the side pane is a genuine improvement. It removes a small but real interruption from the workflow by keeping source material and AI commentary side by side. Students checking sources, office workers scanning a linked document, or anyone who uses Copilot as a first stop for information will likely appreciate not being thrown into a separate app every time they click a link. The change also lowers the barrier to actually opening citations, which could nudge more people to read what Copilot is referencing instead of taking its summaries at face value.
Power users, on the other hand, may find the embedded browser more frustrating than helpful. Without extension support, tab management, or the ability to navigate freely beyond the linked page, the side pane cannot serve as a primary browsing tool. Anyone who regularly opens multiple sources, annotates pages, or uses privacy-focused browser extensions will still need to switch to a full browser for serious work. For them, the best approach may be to treat the Copilot pane as a preview window: useful for a first look, but something to be popped out into a dedicated browser as soon as the task becomes complex. As Microsoft collects feedback from Insiders and decides how far to push this design, the company will have to balance its ambition to keep users inside Copilot with the reality that, for many people, the open web still works best when it lives in a real browser rather than an AI assistant’s sidebar.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
