Windows Terminal Preview v0.9 Release



The v0.9 release of the Windows Terminal has arrived! This is the last version of the Terminal that will include new features before the v1 release. You can download the Windows Terminal from the Microsoft Store or from the GitHub releases page. Let’s dive into what’s new!

Command Line Arguments

The wt execution alias now supports command line arguments! You can now launch Terminal with new tabs and panes split just how you like, with the profiles you like, starting in the directories you like! The possibilities are endless! Here are some examples:

wt -d .
Opens the Terminal with the default profile in the current working directory.

wt -d . ; new-tab -d C:\ pwsh.exe
Opens the Terminal with two tabs. The first is running the default profile starting in the current working directory. The second is using the default profile with pwsh.exe as the "commandline" (instead of the default profile’s "commandline") starting in the C:\ directory.

wt -p "Windows PowerShell" -d . ; split-pane -V wsl.exe
Opens the Terminal with two panes, split vertically. The top pane is running the profile with the name “Windows Terminal” and the bottom pane is running the default profile using wsl.exe as the "commandline" (instead of the default profile’s "commandline").

wt -d C:\Users\cinnamon\GitHub\WindowsTerminal ; split-pane -p "Command Prompt" ; split-pane -p "Ubuntu" -d \\wsl$\Ubuntu\home\cinnak -H
See below. 😊

Image terminal command args

If you’d like to read up on everything you can do with our new command line arguments, check out the full documentation here.

Auto-Detect PowerShell

If you’re a big fan of PowerShell Core, we have great news for you. The Windows Terminal will now detect any version of PowerShell and automatically create a profile for you. The PowerShell version we think looks best (starting from highest version number, to the most GA version, to the best-packaged version) will be named as “PowerShell” and will take the original PowerShell Core slot in the dropdown.

Image terminal powershell core

Confirm Close All Tabs

Are you someone who always wants to close all of your tabs without being asked every time? If you said yes, this new feature is for you! A new global setting has been created that allows you to always hide the “Close All Tabs” confirmation dialog. You can set "confirmCloseAllTabs" to false at the top of your profiles.json file and you’ll never see that popup again! Thanks to @rstat1 for the contribution of this new setting. 😊

Other Improvements

⭐ Accessibility: You can now navigate word-by-word using Narrator or NVDA!

⭐ You can now drag and drop a file into the Terminal and the file path will be printed!

⭐ Ctrl+Ins and Shift+Ins are bound by default to copy and paste respectively!

⭐ You can now hold Shift and click to expand your selection!

⭐ VS Code keys used for key bindings are now supported (i.e. "pgdn" and "pagedown" are both valid)!

Bug Fixes

πŸ› Accessibility: Terminal won’t crash when Narrator is running!

πŸ› Terminal won’t crash when you provide an invalid background image or icon path!

πŸ› Our popup dialogs all now have rounded buttons!

πŸ› The search box now works properly in high contrast!

πŸ› Some ligatures will render more correctly!

Top Contributors

We always love working with our community and we’d like to give out our monthly contribution awards. Check out the winners!

Contributors Who Opened the Most Non-Duplicate Issues

πŸ† j4james

πŸ† JekRock

πŸ† jsoref

πŸ† vadimkantorov

Contributors Who Created the Most Merged Pull Requests

πŸ† j4james

πŸ† german-one

πŸ† Harmon758

πŸ† vtabota

πŸ† mkitzan

πŸ† rholliday

πŸ† iamakulov

Contributors Who Provided the Most Comments on Pull Requests

πŸ† jsoref

πŸ† j4james

πŸ† german-one

Let’s Chat

If you ever have any questions or feedback, feel free to reach out to Kayla (@cinnamon_msft) on Twitter or file an issue on GitHub. We hope you like this feature-complete release of the Terminal before v1 and we’ll be back with another update soon!


Comments are closed. Login to edit/delete your existing comments

  • Avatar
    Arun K

    Does windows terminal have emoji support just yet? When I type an emoji into power shell I get ?? and not the emoji like in the preview video. I tried different fonts too (Segoe emoji), dΓ©jΓ  sans etc. No luck.

  • Avatar
    JoΓ£o Antonio Santana

    The Windows Terminal will now detect any version of PowerShell and automatically create a profile for you.

    This includes Developer PowerShell (yes, i know it wasn’t a version strictly speaking)?

  • Avatar
    Julian Knight

    Hmm, well split pane is a start but who thought it a good idea not to bother to implement some way of doing from – you know “Windows” after which the OS is named?! In fact, you can’t even do it from PowerShell! Neither can you split panes from an open WSL or other Linux shell. πŸ™

    Nor can you resize the split? And this is v0.9?

    Sorry all but that kind of misses the mark. I have to open a terminal (cmd.exe only), then issue the command which opens a new terminal Window. Then I can’t resize the split.

    Seems like a long way to v1. But “This is the last release that will have new features before the v1 release” – ??? So you are really going to release it as a v1 in this state?! Please don’t, it is embarrassing.

    Don’t get me wrong, I’m loving the fact that Windows Terminal is finally getting some decent attention after so many years of neglect but the current delivery isn’t terribly “Windows-like”.

  • Derek Price
    Derek Price

    Can’t figure out how to launch Windows Terminal from a PowerShell prompt and have it work. From one of the examples above, if I type in:

    ❯ wt -p “Windows PowerShell” -d . ; split-pane -V wsl.exe
    split-pane: The term ‘split-pane’ is not recognized as the name of a cmdlet, function, script file, or operable program.
    Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

    You get an error since PowerShell recognizes the semicolon as a statement terminator. I tried using & with the same result. Also, your PowerShell window is locked until you exit wt.

    What am I missing here?


  • Avatar
    Jon Miller

    I’m trying to use the nano.exe that comes with Git for Windows. Some of the commands such as Ctrl+Home, Ctrl+End, Shift+Home, and Shift+End aren’t working. It’s not working in Windows Terminal or the PowerShell/cmd console window. It does work in a WSL Ubuntu window. I’m assuming this is a problem with the nano.exe that comes with Git for Windows? Or, would it be a problem with the console?

  • Avatar
    P L

    Looks good! But when I launch WT from the address bar of File Explorer, it takes me to my home directory, not the directory that I’m in.
    If I invoke cmd or powershell they take me to the current folder directory.

  • Avatar

    This is a good feature. By customizing the opening like ‘wt -p “Ubuntu” -d \\wsl$\Ubuntu\home\user’, I don’t need to change my windows home folder (/mnt/c/Users/user) to Linux one (/home/user) everytime I open my Ubuntu profile any more, which has been bugging me for weeks. What’s strange is that this trick (using -d flag to specify the starting directory) does not seem to work with Powershell Profile though: whatever directory I try, it just starts in the %USERPROFILE% folder.