PuppyIP Resource Center
Developer Tools & Networking 5 min read Published 2026-11-18

Copilot App Browser Use Preview: Setup and Troubleshooting

GitHub Copilot app can use a browser extension to interact with websites, test web apps and retrieve page information. The feature is public preview and off by default. Prepare Node.js 22 or later and the official extension, then enable both Computer Use and Browser Use. Edge also requires Chrome to be installed.

GitHub Copilot app browser use Browser extension Chrome Microsoft Edge

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The November 17 announcement introduces the browser-use preview in Copilot app. This guide covers app settings; other clients have their own setup.
  • The app plugin needs Node.js 22 or later with node on PATH. Chrome and Edge use the GitHub Copilot extension from the Chrome Web Store; Edge also requires Chrome.
  • Enable Browser Use depends on Enable Computer Use. The enterprise managed setting features.browserUse=false prevents users from enabling it.
  • On macOS 27, an installed extension may appear as Not installed. GitHub recommends starting a session and sending a message to connect it. Access to signed-in websites can also expose visible sensitive content as context.

What can it do, and which requirements remain unspecified?

GitHub introduced the browser-use preview in its November 17, 2026 Copilot app update. Browser use lets an agent visit websites, retrieve information, fill forms and test web applications. It remains public preview, so behavior and entry points may change.

The concept documentation also lists Copilot CLI, Visual Studio Code and JetBrains IDEs. This guide covers the Copilot app workflow. Its switches are not universal instructions for other clients, and browser interaction is a separate task from controlling other desktop applications.

The reviewed sources do not provide a complete plan, country, minimum app/OS version or separate feature-price table. Preview does not establish access for every account or free model calls. Check your client, subscription and organization settings.

Prepare Node.js, the browser and the official extension

The app guide requires Node.js 22 or later, with node available on PATH so the app environment can find that command. Browser use needs Node.js to run its plugin; installing the browser extension alone does not meet this requirement.

In Google Chrome or Microsoft Edge, install the GitHub Copilot extension from the Chrome Web Store. The concept documentation explicitly requires Google Chrome to be installed when using Edge too. Chromium-based does not by itself establish support for another browser.

This guide describes the public instructions without installing an extension or changing settings for you. The extension settings let you manage permissions and experimental features. Confirm that the chosen test website is appropriate for the task.

Enable both app switches, then define the task

Open the app settings and select Computer Use in the sidebar. Enable Computer Use first if it is off, then turn on Enable Browser Use. Browser use is off by default and requires computer use to be enabled.

Once enabled, the app can use browser use automatically for browser-related tasks. You can also request it explicitly with /browser-use. Specify the website, desired outcome and constraints so the result is easier to check.

A hypothetical test task could ask it to open your test application, check the empty-field validation on its sign-in form, avoid submitting real credentials or changing data, and report what it observes. Use a page you are authorized to test and review the actual agent activity and result.

How do enterprise policy and signed-in websites affect access?

Administrators can control whether users may enable the feature through features.browserUse in managed settings. Setting it to false prevents activation. Setting it to true, or omitting the key, lets users control it; neither automatically enables the feature nor replaces extension installation and app setup.

Browser use can interact with websites where you are already signed in. Visible account details, business information or other people’s data may become context for Copilot. Limit the site and task, and use only content you are comfortable providing to Copilot.

Page content and timing can cause the agent to choose the wrong control or enter text in the wrong place. Define the allowed actions and verify results before tasks that submit, share or change other people’s data. Do not assume confirmation before every click or treat website access as business authorization.

Does Not installed on macOS 27 mean you must reinstall?

The app guide documents a macOS 27 display issue: the GitHub Copilot browser-extension card under Prerequisites in Computer Use settings can show Not installed even when the extension is installed. Browser use can still work in that situation.

For this specific case, GitHub recommends starting a session and sending a message. The extension connects within a few seconds and the card updates. Distinguish an installed extension that has not connected from a missing installation before relying on the card label alone.

This note does not make macOS 27 the minimum OS requirement or establish a universal fix for extension connection errors. For a different situation, check Node.js/PATH, the extension, both switches and organization policy, and retain the actual error.

How do you verify that the task actually finished?

Compare the real page result with the requested task. Check the target page, expected validation message and any field the agent was allowed to change. A completion message or a click alone does not establish those results.

Dynamic pages, interface changes and loading timing can prevent completion. Start with a limited task on a test page without sensitive content before expanding the scope. After an unintended action, inspect changes already made; do not assume a later stop automatically undoes them.

Handle enterprise disabling and missing local dependencies at their own layers. Changing a proxy exit cannot install Node.js, grant website access or override enterprise policy. Investigate networking further only when you have a concrete connection symptom.

Sources

Frequently Asked Questions

Can I use Safari, Firefox or a mobile browser?

The current concept documentation lists only Chrome and Edge for the extension, with Chrome also installed when using Edge. This guide has no evidence of equivalent support in those other browsers or mobile clients.

Does /computer on also enable the browser extension?

These are not equivalent. The app guide requires the official browser extension, Node.js 22 or later on PATH, and Enable Browser Use in Computer Use settings. Enabling Computer Use is one prerequisite.

Does disabling the extension or a switch revoke access for a running task?

The reviewed browser-use guides do not specify how disabling the extension or a switch revokes access for an ongoing session. Check actual activity and page changes for an in-progress task; a switch state alone does not establish that actions have stopped or earlier changes have been undone.