Windows Terminal is Microsoft's open-source command-line host for running PowerShell, Command Prompt, and Linux shells through WSL in customizable tabs and panes, giving Windows users one workspace for command-line tasks.
Windows Terminal brings several command-line environments into one desktop application, so developers and administrators can work with their preferred shells without managing separate console windows. It hosts PowerShell, Command Prompt, and installed WSL distributions while leaving each shell responsible for interpreting commands and running programs. A developer can keep a project shell, a package-management session, and a server connection available during the same task. Administrators can move between Windows utilities and Linux tools without changing their usual command syntax. The application provides the surrounding interface rather than replacing existing shells, making it useful for people who depend on established scripts and command-line workflows.
Windows Terminal runs on supported Windows 10 and Windows 11 systems, with packaged releases available through Microsoft Store, WinGet, and GitHub. The supplied installer is an MSIX bundle, and some installations may require additional dependency packages. Direct GitHub installations should not be assumed to receive automatic updates; users can obtain newer releases through their chosen distribution channel. For browser-based documentation and downloads, microsoft-edge provides a related Windows browsing option without changing how the terminal executes commands. Version 1.24 includes an extensions settings page and supports relative paths for several customization resources, while automatic SSH host detection is not included in that release.
Keeping related command-line work in one organized workspace reduces the time spent locating windows and rebuilding working context. Windows Terminal lets a user retain separate sessions for a running development server, file operations, and system checks while moving between them as needed. This separation makes it easier to inspect output without interrupting another command or losing the directory associated with a different task. Familiar shells and existing scripts remain usable, so adopting the host does not require replacing an established toolchain. Customizable keyboard actions can reduce repeated mouse navigation, and saved settings help maintain consistent behavior across regular work sessions. Clear text rendering and adjustable appearance also make long command output more comfortable to inspect. For administrators, the ability to keep Windows and Linux environments accessible from the same application supports mixed-system maintenance without forcing every task into a single shell. The result is a more controlled command-line workspace rather than a new language or scripting platform.
Windows Terminal opens different shells in separate tabs and lets users rearrange or detach tabs into other windows. You can keep a long-running process available while starting another command in a fresh session. Custom tab titles and colors help identify related tasks, making a busy workspace easier to navigate without closing active processes.
Split panes display multiple command-line sessions within a single tab, with vertical or horizontal layouts and keyboard controls for moving focus and resizing sections. One pane can show a build log while another remains available for troubleshooting. Read-only mode can also prevent accidental input to a pane that should remain undisturbed.
Windows Terminal automatically detects supported installed shells, including WSL distributions and additional PowerShell versions, and creates corresponding profiles. Users can also define profiles for executables, scripts, or SSH commands, choosing a starting directory and other settings. This reduces repeated setup when switching between local tools and remote systems while keeping each environment's configuration separate.
Appearance settings allow individual profiles to use different color schemes, fonts, cursor styles, and background images. Users can configure these options through the graphical settings interface or edit settings.json for more detailed control. Shared defaults can keep profiles consistent, while individual overrides make particular environments easier to distinguish when several sessions are open.
Windows Terminal provides a searchable command palette for finding and running application actions without navigating several menus. It can open through Ctrl+Shift+P, and users can assign custom shortcuts to frequently used commands. Version 1.24 also supports searching the palette in English and the display language, helping users locate actions when interface translations differ.
Unicode and UTF-8 support allow the terminal to display multilingual characters and symbols used by modern command-line programs. Its GPU-accelerated renderer supports configurable fonts and text presentation, while applications can use supported terminal escape sequences for richer output. These capabilities are particularly useful when inspecting international text, source files, or tools that rely on accurate character rendering.
Windows Terminal supports the wt command for launching windows, tabs, and panes with specified profiles, directories, and commands. A shortcut or script can start a prepared workspace instead of requiring every session to be opened manually. This is useful for repeatable development routines, although the commands themselves still run inside the selected shell.
Scrollback search helps locate earlier output within a terminal session, including text that has moved beyond the visible window. Users can also select and copy text or export tab content for later examination. This makes it easier to review command results, preserve useful diagnostic information, and share relevant output without reproducing an entire troubleshooting session.
Yes. Microsoft distributes the application under the MIT license, which permits use, modification, and redistribution under its terms. It is available without a purchase or subscription. The terminal is a host for command-line applications, so any separate tools or services you connect to may have their own licensing requirements.
Use Microsoft Store, run winget install --id Microsoft.WindowsTerminal -e, or download the official MSIX bundle from GitHub. The packaged installer may retrieve dependencies during setup. For a Store-free installation, Microsoft also offers unpackaged ZIP distributions. Choose a package appropriate for your system and follow the official instructions for that distribution.
No. It hosts existing command-line shells rather than replacing their command interpreters. PowerShell, Command Prompt, and WSL distributions continue to provide their own commands, scripts, and environments. You can select a default profile and install additional shells independently, so changing the terminal interface does not require abandoning existing workflows.
Yes. Installed WSL distributions can appear automatically as profiles, and you can create a profile that launches an SSH command for a remote host. The SSH client and any Linux distribution must be available separately. Version 1.24 does not provide automatic SSH host detection, so remote profiles need manual configuration.
Update behavior depends on the distribution. Microsoft Store and supported packaged installations can receive Store-managed updates, while unpackaged and portable ZIP installations require manual updates. A direct GitHub installation should not be assumed to update automatically. Check the installed package type and use the appropriate update method rather than relying on a universal updater.
Comments