Getting started with Windows Terminal for modern command line work
Windows Terminal has quietly become one of the most useful tools on a Windows 11 machine, replacing the ageing console host that served developers for decades. The application is free, open source, and available from the Microsoft Store, bundling Command Prompt, PowerShell, and Linux distributions through WSL into a single tabbed interface. For Australians juggling remote work across Sydney, Melbourne, or regional Queensland, learning to use this terminal properly can save hours each week.
Although the learning curve feels steep at first, things click once you experiment for an afternoon. The app handles multiple shell environments side by side, supports split panes, lets you design custom colour schemes, and includes a drop-down Quake mode. This guide walks through practical steps to install, configure, and enjoy working inside Windows Terminal, with notes tailored to local workflows.
What sets Windows Terminal apart from the legacy console
The traditional conhost.exe window that ships with every Windows release was designed when most interaction happened through a mouse. Modern computing looks very different, especially for users managing cloud workloads or compiling code. Windows Terminal replaces that legacy host with a rendering engine based on DirectWrite and DirectX, which means crisper text, full Unicode support, and proper ligature handling when you select a developer font like Cascadia Code.
The breakthrough is running several shell environments simultaneously without juggling separate windows. You can have PowerShell open in one tab, an Ubuntu WSL instance in another, and an SSH session into a remote server in a third. For Australian sysadmins handling hybrid environments with servers in Sydney, this consolidated approach removes the clutter of dozens of minimised taskbar windows.
The terminal uses GPU-accelerated rendering, which keeps the interface responsive even when a command spits out thousands of lines. Tab switching feels snappier than the older console host, particularly when working over a typical NBN HFC or FTTC connection that introduces the occasional lag spike during peak evening hours.
Installing the terminal and choosing your first shell
Getting Windows Terminal onto a fresh Windows 11 device takes about a minute. Open the Microsoft Store, search for "Windows Terminal," and click Install. Alternatively, winget users can run winget install Microsoft.WindowsTerminal from any existing command line. Once installed, the app pins itself to the taskbar and can be launched with Win+R followed by wt.
The first launch drops you into PowerShell, which remains the default profile for most users. PowerShell 7 brings cross-platform scripting, a massive module ecosystem, and compatibility with tools designed for Linux automation. Many Australian developers also add an Ubuntu or Debian distribution through WSL, which integrates tightly with the file system.
Choosing a default shell is a personal decision, but PowerShell is a sensible starting point because it exposes cmdlets like Get-Process, Get-Service, and Get-Help that map onto everyday administrative tasks. You can change the default later through Settings, which opens as a JSON file you can edit directly.
Profiles, settings, and the JSON configuration file
Settings live in a file named settings.json, opened by clicking the dropdown arrow and selecting Settings. The file splits into global properties at the top, a profiles array that defines every shell entry, and a schemes array for colour palettes. Each profile can override the font, background image, starting directory, and icon, which is useful if you want one tab to look distinctly different from another.
For users connecting to remote servers across multiple time zones, setting a clear colour cue per profile helps avoid the classic mistake of running a destructive command on the wrong machine. A bright red background on production profiles and a softer blue on staging is a common convention. The terminal also supports per-profile padding, acrylic transparency, and custom cursor shapes.
Edits apply immediately when you save the file, and there is no need to restart the application. The settings UI provides a friendlier front-end for newcomers who are not yet comfortable editing JSON by hand. Both approaches write to the same file.
Tabs, panes, and keyboard shortcuts that save time
Productivity in Windows Terminal comes from leaning on the keyboard rather than reaching for the mouse. The default shortcut to open a new tab is Ctrl+Shift+T, while Ctrl+Tab cycles forward through open tabs and Ctrl+Shift+Tab moves backwards. Splitting the current pane horizontally uses Alt+Shift+Plus, and a vertical split uses Alt+Shift+Minus, mirroring the muscle memory many developers already have from tmux or iTerm2.
Quake mode drops the terminal down from the top of the screen with a single keypress, then hides it again when you are done. This is perfect for quick lookups during a Teams call or while drafting an email. Custom key bindings live in the keybindings array of settings.json, where you can remap anything from copy and paste to launching a specific profile with elevated privileges.
Search inside the terminal uses Ctrl+Shift+F and highlights matches across the entire scrollback buffer, not just the visible region. Combined with progressive scrollback, you can quickly locate the output of a command you ran hours earlier without slowing down the application.
Customising fonts, themes, and colour schemes
A pleasant-looking terminal encourages longer sessions, and Windows Terminal exposes plenty of knobs to tune the appearance. The fontFace property accepts any monospaced font installed on your system. Cascadia Code is bundled with the terminal and includes programming ligatures that turn sequences like => and != into single glyphs. Other favourites include JetBrains Mono, Fira Code, and Consolas, all downloadable free of charge.
Colour schemes are defined in the schemes array and reference 16 ANSI colours plus foreground, background, and cursor colours. Built-in schemes like Campbell, Solarized Light, and One Half Dark ship out of the box, but the Windows Terminal gallery on GitHub offers hundreds of community contributions. Picking a scheme with sufficient contrast matters during long sessions, particularly when working late in a Perth office under fluorescent lighting that can wash out subtle colour differences.
Background images and acrylic effects add personality without sacrificing legibility. A subtle desktop wallpaper at low opacity makes the terminal feel less sterile, while full transparency can interfere with text rendering on certain laptop screens.
Running Linux tools through WSL and connecting over SSH
The Windows Subsystem for Linux is the killer feature for many users because it lets you run real Linux binaries on top of the Windows kernel. Installing Ubuntu from the Microsoft Store, or running wsl --install from an elevated PowerShell prompt, gives you a fully featured Linux user space accessible as another profile. Editing files in /mnt/c, running git, and using build tools like make work exactly as they would on a dedicated Linux box.
SSH integration is equally seamless. The terminal inherits the OpenSSH client bundled with Windows 10 and 11, so connecting to a remote host is as simple as ssh user@host. Public key authentication using the built-in ssh-agent streamlines daily logins. For Australian developers connecting to AWS regions in Sydney, this approach avoids the overhead of running PuTTY or a separate MobaXterm installation.
Profiles can be defined that launch straight into an SSH session, complete with a custom icon and colour scheme. A single click can open a new tab connected to your production bastion host, while another tab sits ready for staging. The flexibility to mix local and remote workflows under one interface is what makes Windows Terminal genuinely transformative for daily command line work.
Practical recipes: winget, PowerShell, and Git in one place
The real payoff arrives when you start combining tools inside a single window. winget, the Windows Package Manager, handles application installation and updates from the command line. Running winget upgrade --all from PowerShell keeps installed software current without launching a browser, which is handy when managing a personal device you use to work from a café in Brisbane or a co-working space in Adelaide.
PowerShell scripting becomes more pleasant with the terminal's broad window and rich text rendering. Writing a small function to query ACMA-registered devices, iterate through a CSV, or automate Office 365 tasks feels natural when the shell handles long lines cleanly. Modules like PSReadLine add syntax highlighting and command prediction that speed up daily scripting work.
Git operations tie everything together for developers. Cloning a repository, checking out a branch, and pushing commits all happen within the same window you use for system administration. When your tooling is consolidated, context switching disappears, and the time you save can be spent on more interesting problems. The same applies to anyone who wants to keep their phone in good shape between terminal sessions, and if you need a refresher on hardware upkeep, the guide on cleaning an Android charging port is a useful companion read.
Mastering Windows Terminal is less about memorising commands and more about building a comfortable workspace that fits the way you work. Spend an afternoon tweaking profiles, mapping your favourite key bindings, and adding WSL or SSH entries, and you will find that the command line stops feeling like a relic and starts feeling like the most productive corner of your operating system. When you are ready to wind down after a long scripting session, browse the latest stories and recommendations on https://kepotek.com/games to see what is worth your evening.
