Except, sometimes, pasting passwords over SSH plain won't work. The 'new' Windows Terminal is everything i want. I'll add a tabTitle and a commandline.I swear i'm going insane and it shouldn't be that hard. It will have no icon and it'll launch cmd.exe as the default shell because I didn't set any other command line! It I add it at the top (as the first) item in the profiles array it'll also appear first in the menu and have the hotkey Ctrl+Shift+1. This will make a new menu item in Windows Terminal with the same name. To start, and to learn, let's add the simplest possible profile! I'm just adding the as an array item in the larger profiles and giving it a name. I'll add a profile to the 'profiles' array. This will make it easier to create and discover new settings. That's important because the Windows Terminal settings profile.json includes a JSON Schema and you'll want your settings to have autocomplete/intellisense. Note that there are a ton of great and useful settings so explore the Settings Schema, and when you're editing the settings make sure that Visual Studio Code is set as your default handler for. Adding a New Profile to Windows TerminalĬlick the down arrow in the Windows Terminal top tab bar. Perhaps those remote machine can have their own cool menu item? Let's see what that would look like and how we'd do it.

However, I'd like to be able to have a profile that ssh's into Linux machines that I use regularly. I have a number of things in my Terminal dropdown. Windows Terminal will regenerate it when it next starts. If you tried terminal a few versions ago and haven't gone back in, it's also time to let the Windows Terminal generate you a nice fresh new profiles.json (settings file). You may also have customize your settings. By now I hope you've installed Windows Terminal.

Windows terminal putty