Asher

`abs-proxy-base-path` is for code-server's internal proxy for proxying web apps (accessible via `/absproxy/$portnumber`), but it does not have anything to do with NGINX proxying to code-server, if that makes sense....

Wait I am dumb, missed the `proxy_pass`. Try `proxy_pass http://$upstream/;`.

Closing for inactivity, but feel free to continue the discussion if you come back to this.

Weird, I am not sure what we could have changed that would cause this. I tried reproducing with Chromium 127.0.6533.119 on Linux but v4.95.3 fits within the window for me....

Just to be sure, I tried the same version of Chrome on a Windows machine, loading it at a few different window sizes, but it always fits in the window...

I think the problem is that you launched code-server with `?workspace=/root/code-server`. A "workspace" in VS Code parlance is a file that contains a list of folders. So, it tries to...

If it reproduces in Codespaces we should report it upstream (https://github.com/microsoft/vscode). I am not sure we change anything in VS Code that could cause this. 🤔

Closing for now since it appears to be an upstream issue.

In the integrated terminal, VS Code usually provides its own `code-server` binary. Is that the one being ran, or is it the one we ship? What does `which code-server` show?...

Ahhhh I see, yup if you use it outside of the integrated terminal and there is no `VSCODE_IPC_HOOK_CLI` variable set, then it will instead use our own socket which defaults...