Skip to content

Browser-only editors

vscode.dev and github.dev have no Node extension host and no filesystem, so the extension does not run there.

PlannedNot built yet. Nothing on this page works in a published release.

Updated 02 Nov 2026Checked against vulnetix-vscode@9ad08fa

vscode.dev and github.dev run the whole editor inside a browser tab. There is no Node process, no way to start a child process, and files come from a virtual filesystem.

The extension has a main (Node) entry point and no browser entry point, so these editors cannot load it at all. Nothing runs: no findings, no status bar item, no commands.

What to do instead

  • On a GitHub repository page, press . to open github.dev, then Continue Working On… to move into a Codespace or a local clone. Both have a filesystem and run the extension.
  • For a browser UI with a real extension host, use code-server, OpenVSCode Server, Gitpod, Coder or Firebase Studio: Remote workspaces and containers.
  • To look up a vulnerability identifier on any web page, use the browser extension.
Edit this pageSources: vulnetix-vscode/package.json, vulnetix-vscode/src/constants.ts
esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.