Skip to content
The new Windows Terminal and the original Windows console host, all in the same place!
C++ C# C PowerShell Batchfile Assembly Other
Branch: master
Clone or download

Latest commit

miniksa Update wil. Fixes GDI handle leak (#6229)
## Summary of the Pull Request
When resizing the window title, a GDI object would be leaked. This has to do with our island message handler using `wil` to track these objects and `wil` having a bug.

## References

## PR Checklist
* [x] Closes #5949 
* [x] I work here.
* [x] Tested manually
* [x] Doc not required.
* [x] Am core contributor.

## Validation Steps Performed
* [x] Added the GDI Objects column to Task Manager, set the Terminal to use the `titleWidth` size tabs, then changed the title a bunch with PowerShell. Confirmed repro before (increasing GDI count). Confirmed it's gone after (no change to object count).
Latest commit 48b3262 Jun 1, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update wil. Fixes GDI handle leak (#6229) Jun 1, 2020
.nuget Update razzle to use vswhere (#13) (#606) May 10, 2019
build build: merge the signing steps and wildcard them (#5817) May 8, 2020
dep Update wil. Fixes GDI handle leak (#6229) Jun 1, 2020
doc Allow the default profile to be specified by name (#5706) Jun 1, 2020
oss build: move oss required to build conhost out of dep/ (#5451) Apr 21, 2020
res Update Cascadia Code to 2005.15 (#5930) May 15, 2020
samples sample: Fix static "cmd.exe" in miniterm (#2461) Aug 19, 2019
src Update wil. Fixes GDI handle leak (#6229) Jun 1, 2020
tools Fix SGR indexed colors to distinguish Indexed256 color (and more) (#5834 May 27, 2020
.clang-format add clang-format conf to the project, format the c++ code (#1141) Jun 11, 2019
.editorconfig Merged PR 3315789: Migrate GitHub changes up until cfc72ce May 28, 2019
.gitattributes Initial release of the Windows Terminal source code May 2, 2019
.gitignore Scale box drawing glyphs to fit cells for visual bliss (#5743) May 8, 2020
.gitmodules Lowercase GH org name in .gitmodules (#629) May 9, 2019
.vsconfig Switch away from OS version detection for DirectWrite things (#2065) Jul 24, 2019 doc: update (#4816) Mar 5, 2020 doc: correct Help Wanted link in (#5967) May 18, 2020
LICENSE Initial release of the Windows Terminal source code May 2, 2019 On second thought, embed the third-party notices in the package (#5673) Apr 30, 2020
NuGet.Config Host our own NuGet feed for packages that we need that aren't elsewhe… Jul 12, 2019
OpenConsole.sln Add a context menu entry to "Open Windows Terminal here" (#6100) May 28, 2020 Add `winget` instructions to (#6169) May 27, 2020 doc: fix a small issue for #hacktoberfest (#3057) Oct 4, 2019
common.openconsole.props Initial release of the Windows Terminal source code May 2, 2019
consolegit2gitfilters.json Merged PR 4405977: tell git2git to ignore some cascadia things Mar 9, 2020
custom.props version: bump to 1.1 on master May 5, 2020
dirs Initial release of the Windows Terminal source code May 2, 2019

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

Microsoft Store [Recommended]

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 Terminal from the Microsoft Store, Terminal builds can be manually downloaded from this repository's Releases page.

Note: If you install Terminal manually:

  • Be sure to install the Desktop Bridge VC++ v14 Redistributable Package otherwise Terminal may not install and/or run and may crash at startup
  • 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

Project Build Status

Project Build Status
Terminal 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.

You can’t perform that action at this time.