GitHub's Copilot browser preview brings signed-in sessions into the workflow

Browser use is off by default and runs in an isolated tab group. The November 17 release separates the browser preview from other integrations reaching different availability stages.
GitHub announced public-preview browser use for the Copilot app on November 17, allowing the assistant to work in a Chromium-based browser where the user is already signed in. The company lists filling forms, retrieving information and testing web applications among the intended uses.
The important change is the working context, not simply the ability to open a page. A signed-in session can expose functions and information that an anonymous browser cannot see. That makes the feature's activation and permission controls part of understanding what has actually been released.
A preview that users must enable
GitHub's >release notes (opens in a new tab) say browser use is disabled by default. The app setup requires its Chrome extension and enabling both computer use and browser use in settings. Permission levels can be managed in the extension.
The company says the feature works with browsers including Chrome and Edge and uses an isolated tab group. Its documentation specifies that Chrome must also be installed when using Edge. That describes its browser organization; it should not be expanded into an unsupported claim that every possible account action is harmless or that the assistant needs no supervision. The release notes do not promise either outcome.
Three integrations, different availability labels
The same announcement puts Azure DevOps repository integration into public preview. GitHub describes a workflow that can create a branch, make changes and open a pull request, while following the repository's checks and policies. Cloud sessions are not available for Azure DevOps repositories in this release.
GitHub Enterprise Server support, by contrast, moves from an opt-in preview to general availability in Copilot app version 1.2.0 or later. Cloud sessions are also unavailable for those repositories. Treating the whole release as one general-availability announcement would erase those differences.
Start with the workflow you actually need
For a developer, the practical question is whether browser interaction is necessary for the task. Testing a web application and reading a public page involve different access needs. A preview in an already authenticated browser deserves a deliberate choice of account and permissions, rather than an assumption that enabling a feature grants a blanket instruction to act.
GitHub also lists browser use in its CLI, VS Code and JetBrains environments. That does not make setup instructions interchangeable across every client. The announcement establishes the new availability; users still need the documentation and controls for the particular environment they use. No performance comparison or independently measured reliability result is provided by this release note.


