GitHub Copilot App: Browser Use Lets Copilot Work in Your Signed-In Browser
Browser use is now in public preview in the GitHub Copilot app. Copilot can fill out forms, pull information from webpages, and test or debug the web app a developer is building, in their signed-in Chromium browser. It runs in an isolated tab group through the GitHub Copilot extension for Chrome, and is also available in Copilot CLI, VS Code and JetBrains IDEs.
Key Takeaways
- Copilot can act in a signed-in browser, which opens up pages that sit behind a login.
- It can fill forms, extract page information and test or debug the web app being built.
- Work happens in an isolated tab group, limiting what Copilot can touch.
- It is off by default, requiring the Chrome extension and two toggles in Computer Use settings.
- It works in Chromium browsers such as Chrome and Edge, and alongside computer use.
- Browser use also reaches Copilot CLI, VS Code and JetBrains IDEs, not only the app.
Sources & Mentions
1 external resource covering this update
Copilot Can Now Use Your Browser
GitHub introduced browser use in public preview. It lets Copilot act inside the developer's own signed-in browser, so it can work with pages that need a login.
What Copilot Can Do
Copilot can fill out forms, pull information from webpages, and test or debug the web application being built. It works in Chromium-based browsers such as Chrome and Edge through the GitHub Copilot extension for Chrome. It also works alongside computer use.
Isolation and Controls
Copilot works in an isolated tab group rather than across all of a user's tabs. Permission levels are managed in the extension's settings. The feature is off by default.
Setup
Install the extension, then turn on Enable Computer Use and Enable Browser Use under Settings, then Computer Use. Browser use is also available in Copilot CLI, VS Code and JetBrains IDEs.