The new Windows Terminal and the original Windows console host, all in the same place!
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ian O'Neill c8f00df170
Fix code-format and test invocation through PowerShell
2 hours ago
.config Auto-format our XAML files and enforce in CI (#9589) 3 months ago
.github Persist inbox conhost; delegate control activities to it via a pipe (#10415) 5 days ago
.nuget Auto-format our XAML files and enforce in CI (#9589) 3 months ago
.vscode Add a language switcher using PrimaryLanguageOverride (#10309) 2 weeks ago
build Force the execution policy on the til::feature powershell script (#10411) 1 week ago
dep Rev wil to latest version (#10435) 6 days ago
doc doc: fix typo in (#10424) 7 days ago
oss Update {fmt} to 7.1.3 (#9580) 3 months ago
res Update Cascadia Code to 2106.17 (#10455) 3 days ago
samples [Defapp] Use real HPCON for PTY management; Have Monarch always listen for connections (#10170) 4 weeks ago
scratch/ScratchIslandApp Add a Scratch.sln for prototyping (#10067) 2 weeks ago
src Update Cascadia Code to 2106.17 (#10455) 3 days ago
tools Fix code-format and test invocation through PowerShell 2 hours ago
.clang-format Update clang-format to 10.0 (#7389) 10 months ago
.editorconfig add .editorconfig file (#585) 2 years ago
.gitattributes Initial release of the Windows Terminal source code 2 years ago
.gitignore Scale box drawing glyphs to fit cells for visual bliss (#5743) 1 year ago
.gitmodules Lowercase GH org name in .gitmodules (#629) 2 years ago
.vsconfig Upgrade Windows SDK to 19041 (#10118) 1 month ago doc: update (#4816) 1 year ago doc: Added links to folders and headers mentioned (#10111) 1 month ago
LICENSE Initial release of the Windows Terminal source code 2 years ago Implement PGO in pipelines for AMD64 architecture; supply training test scenarios (#10071) 1 month ago
NuGet.Config Cleanup NuGet.Config file. (#8829) 5 months ago
OpenConsole.sln Implement PGO in pipelines for AMD64 architecture; supply training test scenarios (#10071) 1 month ago doc: Add logos to README (#9925) 2 months ago doc: fix a small issue for #hacktoberfest (#3057) 2 years ago Prepare for the primary branch name to change to main (#7985) 8 months ago
Scratch.sln Add a Scratch.sln for prototyping (#10067) 2 weeks ago
XamlStyler.json Auto-format our XAML files and enforce in CI (#9589) 3 months ago
common.openconsole.props Initial release of the Windows Terminal source code 2 years ago
consolegit2gitfilters.json Update Cascadia Code to 2106.17 (#10455) 3 days ago
custom.props version: bump to 1.10 on main 4 weeks ago
dirs Initial release of the Windows Terminal source code 2 years ago


Welcome to the Windows Terminal, Console and Command-Line repo

This repository contains the source code for:

Related repositories include:

Installing and running Windows Terminal

🔴 Note: Windows Terminal requires Windows 10 1903 (build 18362) or later

Install the Windows Terminal from the Microsoft Store. This allows you to always be on the latest version when we release new builds with automatic upgrades.

This is our preferred method.

Other install methods

Via GitHub

For users who are unable to install Windows Terminal from the Microsoft Store, released builds can be manually downloaded from this repository's Releases page.

Download the Microsoft.WindowsTerminal_<versionNumber>.msixbundle file from the Assets section. To install the app, you can simply double-click on the .msixbundle file, and the app installer should automatically run. If that fails for any reason, you can try the following command at a PowerShell prompt:

# NOTE: If you are using PowerShell 7+, please run
# Import-Module Appx -UseWindowsPowerShell
# before using Add-AppxPackage.

Add-AppxPackage Microsoft.WindowsTerminal_<versionNumber>.msixbundle

🔴 Note: If you install Terminal manually:

  • Terminal will not auto-update when new builds are released so you will need to regularly install the latest Terminal release to receive all the latest fixes and improvements!

Via Windows Package Manager CLI (aka winget)

winget users can download and install the latest Terminal release by installing the Microsoft.WindowsTerminal package:

winget install --id=Microsoft.WindowsTerminal -e

Via Chocolatey (unofficial)

Chocolatey users can download and install the latest Terminal release by installing the microsoft-windows-terminal package:

choco install microsoft-windows-terminal

To upgrade Windows Terminal using Chocolatey, run the following:

choco upgrade microsoft-windows-terminal

If you have any issues when installing/upgrading the package please go to the Windows Terminal package page and follow the Chocolatey triage process

Via Scoop (unofficial)

Scoop users can download and install the latest Terminal release by installing the windows-terminal package:

scoop bucket add extras
scoop install windows-terminal

To update Windows Terminal using Scoop, run the following:

scoop update windows-terminal

If you have any issues when installing/updating the package, please search for or report the same on the issues page of Scoop Extras bucket repository.

Windows Terminal 2.0 Roadmap

The plan for delivering Windows Terminal 2.0 is described here and will be updated as the project proceeds.

Project Build Status

Project Build Status
Terminal Terminal Build Status
ColorTool Colortool Build Status

Terminal & Console Overview

Please take a few minutes to review the overview below before diving into the code:

Windows Terminal

Windows Terminal is a new, modern, feature-rich, productive terminal application for command-line users. It includes many of the features most frequently requested by the Windows command-line community including support for tabs, rich text, globalization, configurability, theming & styling, and more.

The Terminal will also need to meet our goals and measures to ensure it remains fast and efficient, and doesn't consume vast amounts of memory or power.

The Windows Console Host

The Windows Console host, conhost.exe, is Windows' original command-line user experience. It also hosts Windows' command-line infrastructure and the Windows Console API server, input engine, rendering engine, user preferences, etc. The console host code in this repository is the actual source from which the conhost.exe in Windows itself is built.

Since taking ownership of the Windows command-line in 2014, the team added several new features to the Console, including background transparency, line-based selection, support for ANSI / Virtual Terminal sequences, 24-bit color, a Pseudoconsole ("ConPTY"), and more.

However, because Windows Console's primary goal is to maintain backward compatibility, we have been unable to add many of the features the community (and the team) have been wanting for the last several years including tabs, unicode text, and emoji.

These limitations led us to create the new Windows Terminal.

You can read more about the evolution of the command-line in general, and the Windows command-line specifically in this accompanying series of blog posts on the Command-Line team's blog.

Shared Components

While overhauling Windows Console, we modernized its codebase considerably, cleanly separating logical entities into modules and classes, introduced some key extensibility points, replaced several old, home-grown collections and containers with safer, more efficient STL containers, and made the code simpler and safer by using Microsoft's Windows Implementation Libraries - WIL.

This overhaul resulted in several of Console's key components being available for re-use in any terminal implementation on Windows. These components include a new DirectWrite-based text layout and rendering engine, a text buffer capable of storing both UTF-16 and UTF-8, a VT parser/emitter, and more.

Creating the new Windows Terminal

When we started planning the new Windows Terminal application, we explored and evaluated several approaches and technology stacks. We ultimately decided that our goals would be best met by continuing our investment in our C++ codebase, which would allow us to reuse several of the aforementioned modernized components in both the existing Console and the new Terminal. Further, we realized that this would allow us to build much of the Terminal's core itself as a reusable UI control that others can incorporate into their own applications.

The result of this work is contained within this repo and delivered as the Windows Terminal application you can download from the Microsoft Store, or directly from this repo's releases.


For more information about Windows Terminal, you may find some of these resources useful and interesting:


I built and ran the new Terminal, but it looks just like the old console

Cause: You're launching the incorrect solution in Visual Studio.

Solution: Make sure you're building & deploying the CascadiaPackage project in Visual Studio.

⚠ Note: OpenConsole.exe is just a locally-built conhost.exe, the classic Windows Console that hosts Windows' command-line infrastructure. OpenConsole is used by Windows Terminal to connect to and communicate with command-line applications (via ConPty).


All project documentation is located at If you would like to contribute to the documentation, please submit a pull request on the Windows Terminal Documentation repo.


We are excited to work alongside you, our amazing community, to build and enhance Windows Terminal!

BEFORE you start work on a feature/fix, please read & follow our Contributor's Guide to help avoid any wasted or duplicate effort.

Communicating with the Team

The easiest way to communicate with the team is via GitHub issues.

Please file new issues, feature requests and suggestions, but DO search for similar open/closed pre-existing issues before creating a new issue.

If you would like to ask a question that you feel doesn't warrant an issue (yet), please reach out to us via Twitter:

Developer Guidance


Building the Code

This repository uses git submodules for some of its dependencies. To make sure submodules are restored or updated, be sure to run the following prior to building:

git submodule update --init --recursive

OpenConsole.sln may be built from within Visual Studio or from the command-line using a set of convenience scripts & tools in the /tools directory:

Building in PowerShell

Import-Module .\tools\OpenConsole.psm1

Building in Cmd


Running & Debugging

To debug the Windows Terminal in VS, right click on CascadiaPackage (in the Solution Explorer) and go to properties. In the Debug menu, change "Application process" and "Background task process" to "Native Only".

You should then be able to build & debug the Terminal project by hitting F5.

👉 You will not be able to launch the Terminal directly by running the WindowsTerminal.exe. For more details on why, see #926, #4043

Coding Guidance

Please review these brief docs below about our coding practices.

👉 If you find something missing from these docs, feel free to contribute to any of our documentation files anywhere in the repository (or write some new ones!)

This is a work in progress as we learn what we'll need to provide people in order to be effective contributors to our project.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.