It's all very utilitarian which is to be expected - after all the focus first and foremost is on building a better Console Host and it's an early preview. The core terminal functionality is rock solid,īut the Windows UI shell and command interface are not very feature rich around the edges yet.

The terminal works great, but it's still in the early stages of development. Open source on GitHub and under active development.Any shell application uses ConHost and the Terminal UI provides the hosting UI for these shell instances. The Terminal acts as a host to those shells that are loaded inside of it. Keep in mind that Windows Terminal is a Terminal UI, plus the Console Host, and it's not a replacement for the Powershell, CMD or Bash shells or any other shell. For me, the main reason is that it ships with a new ConHost.exe, that is considerably faster than the ConHost shipped with Windows which results in much faster terminal painting and scrolling. There are lots of reasons to like this new Terminal and I don't want to get into all of them here.

I've been using Windows Terminal for a while now since it was announced and made available in the Windows Store a few months back. Opening an Admin Windows Terminal from Visual Studio Leaving this post in place for archival purposes only.Ī related and more recent post that talks about launching from other applications can be found here:

This post is mostly obsolete, as Windows Terminal now supports a -d parameter for specifying a startup folder: wt.exe -d 'c: emp'.

Wsl windows terminal starting directory