Browser Tools for GitHub Copilot in VS Code Are Generally Available

What's new

• Real browser control: Agents can open pages, navigate, click, type, hover, drag, handle dialogs, and capture screenshots — all without leaving VS Code
• Console and DevTools access: Read page content, capture JavaScript console errors, run scripted end-to-end testing workflows
• On by default with GA — no opt-in required for developers
• Privacy and isolation: Developer's own tabs stay private until explicitly shared; agent-opened tabs run in isolated sessions with no access to existing cookies or history
• Enterprise controls: On/off toggle and network domain allow/deny lists via workbench.browser.enableChatTools setting

Why it matters

Previously, Copilot could only help with code — it couldn't see the running application. Now agents can close the feedback loop by testing live web apps, catching runtime errors, validating UI changes visually, and reading documentation on demand. This is a significant step toward autonomous full-stack development workflows.

How to try it

• Update VS Code to the latest version and ensure the GitHub Copilot extension is current
• Ask Copilot: 'Open my app at localhost:3000 and check the console for errors'
• To disable: set workbench.browser.enableChatTools: false in VS Code settings