Oh, that's the PWA install prompt. PWAs are progressive web apps. If you install that, then code-server runs as a separate window. It still runs on Chrome, but it appears to have its own standalone app.

Another PWA example is most ChromeOS apps that are pre-installed. They open as shortcuts on the Browser, but some apps like GitHub can open in separate windows while running on Chrome, that is, when they are actually "installed"(creating a shortcut and opening a separate window for that tab)

Basically this makes it look as though you installed code-server as an app, like VS Code. But still, it runs on Chrome. Youcan try it, but if you don't like that, you can use it on the browser as you would.

it'd be great ifchrome.sockets.tcpServer was used to bind local ports for forwarding them to the instance that runs code-server. this way, the user would be able to use - for example -http://localhost:3000/ instead ofhttps://code-server.example.com/proxy/3000/ to live view the app they're developing.