GitHub Copilot app adds Azure DevOps and browser use
GitHub's Copilot app now reaches Azure DevOps repositories and the browser you are signed in to, and GitHub Enterprise Server support is out of preview.
GitHub Copilot app Azure DevOps support is now in public preview, alongside browser use and general availability for GitHub Enterprise Server, per a changelog entry dated November 17, 2026. GitHub frames the three changes around one idea: Copilot works best where the developer already is, and each item connects the app to an account or a surface a person already has open. Full details are in the GitHub Copilot app announcement.
Azure DevOps repositories, in public preview
The app can clone an Azure DevOps repository, and an agent can create a branch, make code changes and open a pull request without leaving the app. Pull request status is tracked in the sidebar. Clicking Fix on a review comment asks an agent to address it, and an optional agent merge setting lets an agent fix CI failures and complete the pull request once the Azure DevOps checks and policies pass.
To turn it on, open Settings > Experimental and enable Azure DevOps integration, then go to Accounts > Add account and sign in with the Microsoft account used for Azure DevOps. GitHub states plainly that cloud sessions are not available for Azure DevOps repositories.
Browser use, off by default
Browser use is in public preview and works in Chromium-based browsers, including Google Chrome and Microsoft Edge, through the GitHub Copilot extension for Chrome. It runs in an isolated tab group and works alongside computer use. It is off by default: install the extension, open Settings > Computer Use, and turn on both Enable Computer Use and Enable Browser Use. Permission levels are managed in the extension's settings. The same capability is also available in Copilot CLI, VS Code and JetBrains IDEs.
The stated uses are concrete. You can ask Copilot to fill out forms, pull information from webpages, or test and debug the web app you are building, in the browser session you are already signed in to. That last one is the clearest example: an agent checking your own app in a real signed-in tab rather than a fresh, logged-out one.
Enterprise Server reaches general availability
GitHub Enterprise Server support, previously an opt-in preview, is now generally available. Adding a GHES account lets you work with remote repositories, issues and pull requests inside the app. It requires GitHub Copilot app version 1.2.0 or later. Sign in with a GitHub.com or GHE.com account, open Settings > Accounts > Add account and choose GitHub Enterprise Server. As with Azure DevOps, cloud sessions are not available for GHES.
Limits and open questions
The changelog does not say which plans, seat types or licence tiers receive Azure DevOps integration or browser use, and it gives no pricing. It also does not explain why cloud sessions are excluded for Azure DevOps and GHES. This suggests that agent work on those two sources stays tied to the machine running the app, which likely means long-running background work remains a GitHub.com repository feature for now. How much of a page a browser-use agent can read, and what the permission levels default to beyond the global off switch, is not described in the source.
What this means for building apps with AI
For anyone building a web app, the interesting shift is that coding agents are being wired into the places where the code and the running product actually live, including a logged-in browser. If you are building with an AI app builder instead of an agent in a repo, Draftship takes a different route: you describe the app in plain language and it writes, builds and hosts it, with a built-in database, user sign-in and hosting. Paid plans add source code access, custom domains and GitHub push, which you can read about in GitHub and Vercel. Draftship is not affiliated with GitHub, and nothing here suggests it supports Azure DevOps or the features announced.
Primary sources
- GitHub Copilot app, Microsoft Ignite releases · GitHub Changelog, Nov 17, 2026
This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.