GitHub Copilot Expands Agent Coding to Azure DevOps and Browser Automation

GitHub's standalone Copilot app now clones Azure DevOps repos, drives PRs to merge with agents, and adds browser automation plus general availability for GHES.

·
·
·
Read4 min
TypeNews
SubtopicCode Agents
  • GitHub Copilot app adds Azure DevOps integration in public preview, clone to merge in one client.
  • Agent merge fixes CI failures and completes PRs once Azure DevOps checks and policies pass.
  • Inline Fix button on review comments dispatches an agent to apply the change.
  • Browser use preview drives Chrome or Edge via the Copilot extension, reusing your logged-in session in an isolated tab group.
  • GitHub Enterprise Server support is now generally available in Copilot app 1.2.0 or later.
  • Cloud sessions are not available for Azure DevOps or GHES repositories, agents run locally.

GitHub expanded the standalone GitHub Copilot app at Microsoft Ignite, adding Azure DevOps repository support, browser automation, and generally available GitHub Enterprise Server support. The release brings agent-driven coding and pull-request workflows to teams whose repositories sit outside GitHub.com.

Where each feature stands

Capability Availability Execution Key requirement
Azure DevOps Public preview Local machine Enable the experimental integration
Browser use Public preview Isolated Chromium tab group Install the extension and enable two settings
GitHub Enterprise Server Generally available Local machine Copilot app version 1.2.0 or later

Azure DevOps joins the agent loop

Azure DevOps support covers the full pull-request workflow. An agent can clone a repository, create a branch, modify code, and open a pull request from the Copilot app. The sidebar tracks pull-request status, and inline review comments include a Fix button that sends the requested change to an agent.

Agent merge can continue working after the pull request opens. When CI fails, the agent can revise the branch and rerun checks, then complete the merge after the configured checks and branch policies permit it. Teams retain their existing Azure DevOps approval and policy controls.

Setup currently requires an experimental flag. Open Settings > Experimental, enable Azure DevOps integration, then select Accounts > Add account and sign in with the Microsoft account connected to Azure DevOps.

Cloud sessions are unavailable for Azure DevOps repositories, so the local machine provides the execution environment for every agent task. That limitation matters for long-running jobs and differs from the hosted sessions available for GitHub.com repositories.

Chrome becomes an agent surface

Browser use lets Copilot fill forms, extract information from webpages, and test or debug web applications through an existing signed-in browser session. Reusing that session reduces repeated authentication and two-factor prompts during automated tasks.

The public preview supports Chromium-based browsers, including Google Chrome and Microsoft Edge, through the GitHub Copilot extension. Agent-controlled pages run in an isolated tab group, separating them from unrelated tabs. Browser use can also work alongside computer use, allowing one task to move between browser actions and broader desktop automation.

Activation requires two explicit steps because browser use is disabled by default. Install the extension, then open Settings > Computer Use and enable both Enable Computer Use and Enable Browser Use. GitHub also exposes browser use through Copilot CLI, Visual Studio Code, and JetBrains IDEs.

GHES sheds the preview label

GitHub Enterprise Server support is generally available after an opt-in preview. Organizations need GitHub Copilot app version 1.2.0 or later and can add a server account from the Accounts pane.

GHES repositories share the Azure DevOps execution constraint: Cloud sessions are unavailable, and agent work runs locally. Self-hosted teams can still use the Copilot app without moving source code to GitHub.com.

The workflows this opens

The expanded client reduces handoffs across several common enterprise development setups:

  • Azure DevOps teams can run an agent-driven coding, review, CI repair, and merge workflow from one client.
  • GHES customers can use agent features while retaining self-hosted repositories.
  • Authenticated browser sessions can support form completion, data extraction, and end-to-end testing without a fresh headless browser profile.
  • Developers working across GHES and Azure DevOps can manage both repository types through the same application.

Limits to check before rollout

Local-only execution for Azure DevOps and GHES makes agent jobs dependent on developer hardware. Flaky tests and misconfigured policies can also trigger repeated repair attempts when agent merge responds to CI failures, increasing runtime and compute use.

Browser automation carries a separate permission risk. The isolated tab group limits the agent’s tab scope, while the active site session can still authorize consequential actions. Organizations can restrict site access through the extension settings and apply the same review controls used for other authenticated automation.

GitHub provides detailed instructions in the Azure setup guide and browser use guide. The features are rolling out in the latest Copilot app build, with Azure DevOps and browser use remaining in public preview.

Trending
  • No trending articles

Comments

avatar

Next Reads