[FEATURE] VS Code integrated browser support

Status Fixed / completed
Maintainer reply ✓ Yes — bcherny
Activity 6 comments · opened Jun 3, 2026 · closed Aug 17, 2026
💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When using Github Copilot or Cursor, I am able to view web pages/web apps, and pass control to the agent, as well as pass references to DOM elements, console logs, and other traffic logs. The Claude extension for VS Code lacks similar functionality.

Proposed Solution

Extend the extension to support the integrated browser or similar.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

When working on a webapp with passkey auth and websockets, it can be trivial to ask Github Copilot why something isn't appearing with the expected value within the app. It's just a click and a sentence away, and GHCP is able to get screenshots and parse the DOM and even inject code to intercept WebSocket traffic, finding issues nearly instantly. With Claude in VS Code, that experience just isn't possible.

Additional Context

_No response_

View original on GitHub ↗

6 Comments

NikolMarg · 2 months ago

This would be a game-changer, it is the reason I preferred Copilot by far. Please consider adding it 🙏

JLC2319 · 1 month ago

This really needs to be implemented. It really limits Claude's ability to understand what users are trying to communicate, especially as it relates to UI changes.

bcherny collaborator · 14 days ago

The VS Code extension can already drive a browser for this kind of debugging. Install the Claude in Chrome extension, then type @browser in the prompt box followed by what you want, e.g. @browser go to localhost:3000 and check the console for errors. Claude can take screenshots, read the DOM, read console messages and network requests, fill forms, and interact with pages you're logged into. It runs in your Chrome/Edge window rather than a VS Code integrated browser pane. Docs: https://code.claude.com/docs/en/vs-code#automate-browser-tasks-with-chrome and https://code.claude.com/docs/en/chrome

🤖 Generated with Claude Code

RyanEwen · 14 days ago

That sounds, okay, but not nearly as good as GitHub Copilot combined with the integrated browser.

I have had moderate success with a third party mcp server that helps Claude drive the integrated browser.

But even better is that I've figured out how to use the copilot chat and Claude harness together with my Claude Max sub. Much better experience!

mogelbrod · 13 days ago
But even better is that I've figured out how to use the copilot chat and Claude harness together with my Claude Max sub. Much better experience!

@RyanEwen how did you accomplish this? I'd also be interested in it!

RyanEwen · 13 days ago
> But even better is that I've figured out how to use the copilot chat and Claude harness together with my Claude Max sub. Much better experience! @RyanEwen how did you accomplish this? I'd also be interested in it!

I asked Claude for help and was surprised to get a working solution:

  • Enable this setting in VS Code:

"chat.agentHost.allowSignedOutWhenUsable": true

  • Run claude setup-token in a terminal, to get a long-lived token and put it into ~/.claude/settings.json

Eg: { "env": { "CLAUDE_CODE_OAUTH_TOKEN": "sk-ant-oat01-..." } }

  • Fully close and reopen VS Code. You should be able to switch the Github Copilot chat from Local to Claude without it being greyed-out / asking to Upgrade.

Unfortunately it has some issues with Remote dev (eg WSL and Dev Containers) but I've opened a bunch of pull requests with info and fixes that will hopefully help get it sorted sooner than later.