Sometimes you will need to SSH into one location before tunneling into another. This should get you set up right in the correct directory after you’ve connected. If the workspace was recently used, you can use File > Open Recent > $de-workspace otherwise go to File > Open Workspace.

Now open your workspace again with a new connection. code-workspace file somewhere it won’t be picked up by Git

There is, however, a workaround to make this a bit less tedious: Wouldn’t it be nice to have VS Code automatically open to the correct folder once your SSH connection is established? Unfortunately there isn’t a way to set a folder location in the settings yet you’d need to click Open Folder and navigate to the project root every time you connect. Try out Visual Studio Professional or Enterprise editions on Windows, Mac. You’re now connected and can use VS Code’s features like Terminal and Debug Console just like you would locally. The Visual Studio Code Remote - SSH extension allows you to open a remote. Hold down the Command key on your keyboard and press the Space Bar and type 'Visual' in the search field, click on the. Click and drag the Visual Studio Code application to the Applications folder on the left: Finding VS Code after Installation. If your key is on the server, it will state it has your fingerprint and prompt you to continue. If it helps find the Visual Studio Code file, click on the Date Added column to sort by newest.

If your public SSH key isn’t on the remote server, you will be prompted to enter a password. Click the green Open a Remote Window icon on the bottom left corner, select Connect to Host., and pick your desired host, in this case MySite.

Visual studio code ssh mac