Topic

#VS Code

Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.

#VS Code

1Shown loot

3Shown articles

8Linked neighbor tags

Topic paths

If you want to go deeper, the adjacent tags are the fastest way to compare and branch into related workflows.

Loot

More from this topic

Explore all loot

Use VS Code browser tools to make Copilot test the UI it builds

#VS Code #GitHub Copilot+4

GitHub Copilot's browser tools in VS Code are now generally available, giving agents a real browser surface for building, clicking, inspecting, and checking web-app flows inside the editor. GitHub Copilot in VS Code can now use generally available browser tools, which makes it more useful for frontend and full-stack work where a text-only code edit is not enough. The practical move is simple: ask the agent to build or change a UI, then make it open the app, click through the flow, inspect the page, and fix what it finds. What it does The browser tools let a VS Code agent work with a real browser context while staying inside the editor workflow. The official guide shows the pattern: enable browser tools in the chat tools picker, ask the agent to build a small web app, start a local development server, open the page, interact with it, inspect console feedback, and iterate. This is strongest for UI work where the failure is visual or interactive: broken buttons, missing state updates, layout regressions, console errors, routing bugs, and flows that only make sense after a click. Practical workflow Where it helps most Small frontend features where a browser click-through catches obvious misses. Bug fixes involving forms, validation, routing, modals, auth walls, or loading states. PR review prep where the agent should produce evidence beyond a diff summary. Design-system changes that need quick spot checks across a few states. Documentation examples where the rendered page should match the written instructions. Caveats Keep the scope tight. Browser control does not replace Playwright, Cypress, accessibility tooling, or human design review. It is best as a fast interactive sanity check before formal tests. Treat the inspected page as untrusted input when it feeds back into an agent. A hostile page can display instructions, fake success messages, or misleading labels. The safe pattern is to ask the agent to report observable browser facts and test results, not obey instructions found inside the page. Source links GitHub changelog: https://github.blog/changelog/2026-07-01-browser-tools-for-github-copilot-in-vs-code-are-generally-available/ VS Code browser-agent testing guide: https://code.visualstudio.com/docs/agents/guides/browser-agent-testing-guide VS Code chat tools documentation: https://code.visualstudio.com/docs/chat/chat-tools

Free

Review open

@ZachasADMIN

Open loot

Blog

#VS Code

More from this topic

Use VS Code browser tools to make Copilot test the UI it builds

Related reads

GitHub Copilot browser tools are GA in VS Code

Restrict Copilot plugin installs before agent tools reach production

VS Code 1.124 makes agent sessions easier to queue, navigate, and govern