The settings.json file is accessible within Windows Terminal by pressing CTRL +, or by navigating to the drop-down arrow and selecting Settings. To begin, we will start by opening our settings.json file within your favorite text editor and creating a new profile within the profiles list for our SSH connection.

SSH Server with Public Key Authentication allowed (optional).Valid SSH User Account and Credentials for the SSH server.Then I’ll continue on to show you to how to tie this together with SSH Keypairs. In this tutorial, I’ll be diving into configuring a profile for connecting to SSH servers from the new Windows Terminal. The nice thing about support for different profiles is that we can create and edit them as we wish. If you also have a Windows Subsystem for Linux Distribution installed, that shell will automatically be loaded into one of your Windows Terminal profiles.

These profiles make up the different command line environments on your machine and, by default, include Windows Powershell, Command Prompt and the Azure Cloud Shell. One of the most exciting features to me is the Windows Terminal’s support for profiles. If you do not already have the new Windows Terminal installed, this article from Microsoft will get you up and running. It also lends itself to creativity and finding the best fit for the type of work you find yourself doing at the command line. These components together offer the terminal user an endless array of configurations, making this a valuable tool for development work and system administration. The new Windows terminal was released back in June of 2019 and has brought several exciting and modern features such as support for tabs, availability for in-depth styling, as well as a configurable JSON file to the Windows Command Line environment.

Windows terminal putty