Skip to content

fix(#310): support vscode-webview:// origin + custom allowed origins#463

Open
giulio-leone wants to merge 2 commits intovercel-labs:mainfrom
giulio-leone:fix/310-vscode-origin
Open

fix(#310): support vscode-webview:// origin + custom allowed origins#463
giulio-leone wants to merge 2 commits intovercel-labs:mainfrom
giulio-leone:fix/310-vscode-origin

Conversation

@giulio-leone
Copy link

Closes #310

Problem

VSCode Webview extensions use vscode-webview:// as their Origin header, which was rejected by the stream server's origin validation.

Solution

  1. Added vscode-webview:// as a default allowed origin in isAllowedOrigin()
  2. Added setAllowedOrigins() for custom origin support
  3. Added AGENT_BROWSER_ALLOWED_ORIGINS env var (comma-separated list)
  4. Added --allow-origins CLI flag passed to daemon

This enables VSCode extensions and other non-browser clients to connect to the stream server.

@vercel
Copy link
Contributor

vercel bot commented Feb 13, 2026

@g97iulio1609 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WebSocket connection rejected from VSCode Webview

1 participant