GitHub Copilot: Browser Tools for VS Code Now Generally Available
GitHub CopilotGitHub made browser tools for GitHub Copilot agents in VS Code generally available, letting agents drive a real browser, navigate live web apps, and feed what they observe back into chat. Agents can open pages, click, type, capture screenshots, and read console errors, while built-in DevTools remain available for manual inspection. Tabs stay private by default until a developer explicitly shares one with an agent, and enterprise administrators get a dedicated toggle plus existing domain restriction controls.
Key Takeaways
- Browser tools for Copilot agents in VS Code reached general availability, after being shaped by feedback during preview.
- Agents can navigate, click, type, and take screenshots in a real browser, then feed what they see back into the chat.
- User tabs are private by default and only become accessible to an agent after an explicit "Share with Agent" action, which can be revoked anytime.
- Agent-opened pages run in isolated sessions with no access to the user's cookies, storage, or browsing history.
- Camera and microphone access are never granted automatically, requiring per-site approval even inside agent-controlled browser sessions.
- Enterprise administrators get a dedicated
workbench.browser.enableChatToolstoggle plus existing domain restriction controls to govern the feature.
Agents Get a Real Browser
GitHub Copilot's browser tools for VS Code have exited preview and are now generally available. The capability lets Copilot agents drive an actual browser instance rather than relying on static code inspection, giving them the ability to navigate live web applications and bring what they observe back into the chat conversation.
What Agents Can Do
Agents equipped with browser tools can perform the same actions a developer would: opening pages, navigating, clicking, typing, hovering, dragging, and handling dialogs. They can also read page content, capture console errors, and take screenshots, which is particularly useful for debugging front-end issues or validating that a UI change actually rendered correctly. Developers keep full access to DevTools inside the same browser toolbar for manual inspection and debugging.
Privacy by Default
GitHub built the feature around explicit consent. User tabs remain private until a developer clicks "Share with Agent," and that access can be revoked at any time. Pages an agent opens on its own run in isolated sessions with no access to the user's browsing data, cookies, or storage, and parallel agent sessions each keep their own tabs separate from one another. Sensitive permissions such as camera and microphone access are never granted automatically and require per-site approval.
Enterprise Controls
Organizations can manage the feature through a dedicated workbench.browser.enableChatTools toggle, layered on top of existing network domain restriction controls that support wildcards and deny-list precedence.
Why It Matters
Static code analysis can only tell an agent so much about whether a web application actually works. By giving agents a real, sandboxed browser, GitHub Copilot closes the loop between writing front-end code and verifying it behaves correctly in a live environment, a capability that materially reduces the back-and-forth needed to fix UI bugs.