CodeServer Run VS Code on any server over SSH. A precursor of VS Code Remote Development

• VSCode’s SSH agent is bananas - Unlike Tramp, which lives off the land on the remote connection, VSCode mounts a full-scale invasion: it runs a Bash snippet stager that downloads an agent, including a binary installation of Node.

• Github copilot extension - is doing rigrep => this can saturate cpu when opening home folder in remote. => disabling copilot extension solve it

VS Code Remote Development

• work over ssh
• on container
• on WSL (windows)

does not work with fish as default user shell => will cause a Timeout on VSCode client (though ssh work perfectly).

code-server

Run inside chrome and work over ssh.

If you have Chrome installed, it opens the browser in app mode. That means there’s no keybind conflicts, address bar, or indication that you’re coding within a browser. It feels just like native VS Code.

Run over ssh

By default, sshcode will rsync your local VS Code settings and extensions to the remote server every time you connect.

#You can specify a remote directory as the second argument
go/bin/sshcode kyle@dev.kwc.io ~/projects/sourcegraph

Docker server

docker run -it -p 8443:8080 -v "${PWD}:/home/coder/project"  -u "$(id -u):$(id -g)" codercom/code-server --auth=none --disable-telemetry

Autocolor by Host

Using Peacock - it must be installed on both local and remote server (?). - doc

In your global VS Code settings (settings.json), you can set a Peacock color for a specific workspace name:

"peacock.favoriteColors": {
    "prod-server": "#FF0000",
    "dev-server": "#00FF00"
},
"peacock.remoteColor": {
    "SSH: prod-server": "prod-server",
    "SSH: dev-server": "dev-server"
},
"peacock.applyColorOnRemoteConnection": true

It seems that remote color is store remotely in settings.json

  "peacock.remoteColor": "#764FE3"