Back to catalog
Windows Terminal
MITOpen-source terminal emulator for Windows that replaces MobaXterm for SSH and CLI tasks with GPU rendering, tabs, and WSL integration.
Open-source alternative to — compare it against:
Overview
Microsoft developed Windows Terminal to modernize the command-line experience without breaking backward compatibility for legacy console utilities. By decoupling the terminal frontend from the low-level console subsystem through ConPTY, the project created a native host for PowerShell, Command Prompt, and Linux environments. Today, it serves as the default terminal canvas on modern Windows systems, combining GPU text rendering with tabbed window management.
Why Windows Terminal instead of MobaXterm
MobaXterm bundles an X11 server, an SFTP browser, and session management, but caps sessions in its free tier and relies on an internal Cygwin layer. Windows Terminal takes a modular operational approach: it functions strictly as a terminal emulator, leaving network connectivity to Windows OpenSSH and Linux environments to the Windows Subsystem for Linux (WSL). For engineers managing infrastructure through SSH keys and CLI tools, Windows Terminal eliminates third-party licensing concerns and runtime clutter.
Configuration also follows modern DevOps practices. Where MobaXterm stores connections in proprietary session files, Windows Terminal uses a JSON file that engineers can track in dotfile repositories. Command-line flags allow automated launch scripts to configure split panes for logs and monitoring with one command. Windows Terminal lacks all-in-one tooling, however: remote file editing requires command-line SFTP or rsync, and remote graphical software depends on WSLg or external display servers rather than a bundled X11 daemon.
What it does well
- Profile isolation: DevOps engineers can maintain distinct profiles for PowerShell, Command Prompt, Azure Cloud Shell, and multiple WSL Linux distributions, each with custom environment variables and starting directories.
- Declarative configuration: Terminal preferences and key bindings reside in settings.json, enabling teams to version-control configurations across machines.
- GPU text rendering: DirectWrite acceleration handles high-throughput logs and compilation output without UI stalls or dropped ANSI sequences.
- Dynamic panes: Engineers can split active windows into horizontal or vertical panes and summon a command palette to switch tasks without leaving the keyboard.
- Tear-off tabs: Tabs can be detached into independent windows or merged across multi-monitor setups during debugging.
