Asher

Sorry for the delay, thank you for fixing this and for the thorough testing! This will be published soon, I think in the next few days after the release candidate...

Might need `workspace:write` and maybe `template:read` as well, to start and update workspaces.

> Yes, this is also broken in GitHub Codespaces To confirm, you reproduced this issue in Codespaces? I assume maybe not since this involves remote mounts? I am not exactly...

Interesting, you may want to see if you can reproduce with native VS Code (`code serve-web`), if it reproduces with that we can report it upstream in the VS Code...

Yeah it seems more likely related to the deployment setup here than code-server. That "refused to connect" page is a browser-level error (or network-level, but I just mean it is...

Closing since it does not appear to be a code-server bug, but feel free to continue the discussion.

I am not sure it is actually enforced, it more just means we are unable to provide debugging support since we cannot legally install it. 😢

That said, maybe this is a different issue, with all the `Extension host (Remote) is unresponsive` logs. Will reopen. Are other extensions working?

Are y'all also seeing `Extension host (Remote) is unresponsive` in the logs or something else?

You marked that this is also broken in Codespaces, is that correct? If so we should open the issue with VS Code at https://github.com/microsoft/vscode.