I treated Windows Terminal like a lab notebook for three months. Every shiny setting got a trial period. If it didn’t earn its keep in real work—debugging scripts, hopping between PowerShell and CMD, babysitting long builds—it got turned off. This is the keep/kill list that survived.
Starting defaults that quietly waste attention
Out of the box, Windows Terminal looks polished. That polish includes a few defaults that fight muscle memory:
- Acrylic / Mica backgrounds. Pretty until you overlay a second monitor with pale slides. Opacity made me squint at pale gray error text. I disabled acrylic and set a solid dark theme.
-
“Close on exit” quirks per profile. Leaving some shells open after a crash is useful for reading the traceback. Others (especially one-shot
cmd /claunches) should die cleanly. I set this per profile, not globally. - Excessive bell style. Audible bells during noisy CI logs are hostility. Visual bell only.
None of these are wrong. They’re just not free.
What I kept—and why
Separate profiles that match how I think
I keep three intentional profiles:
- PowerShell 7 — daily driver for objects, modules, remoting experiments.
- Windows PowerShell 5.1 — the reality on locked corporate images.
- CMD — dead-simple file ops and “what does the legacy script actually do?”
The win isn’t aesthetics. It’s context switching with intent. When I open 5.1, I remember: no ternary sugar, older encoding defaults, different module paths. That mental bookmark prevents half my “why doesn’t this work here?” moments.
Cascadia Code + clear font size floor
Ligatures stay on. Font size never drops below 12 on my main display. Tiny fonts feel productive until an Access Denied scrolls by in a wall of identical paths.
Keybindings that mirror editor habits
I bound split panes to chords I already use in VS Code. Duplicate muscle memory beats “clever” Terminal-only shortcuts I’ll forget in a month.
Startup directory discipline
Each profile opens in a known folder: repos root for pwsh, a sandbox for CMD experiments. Random “wherever the shortcut’s cwd was” is how you accidentally del the wrong tree.
What I disabled after the honeymoon
- Automatic profile detection noise. Handy once. Annoying when every tool install sprouts a new dropdown entry. I pruned hard.
-
Intense color schemes with low contrast on errors. Red-on-maroon looks “hacker.” It also hides
ERRORLEVELmessages. - Always-on multi-line prompt fireworks. Oh My Posh-style prompts can be worth it—but only after the base shell is boring and reliable. I ran ninety days mostly plain, then reconsidered prompt tooling with a clearer cost model.
- Unrestricted paste warnings off. I left paste warnings on. One bad multiline paste into a remote session is enough education forever.
The meta-lesson
Windows Terminal configuration is a productivity tool and a distraction engine. The useful test isn’t “is this cool?” It’s “does this reduce mistakes when I’m tired?”
After ninety days, my Terminal is quieter, more contrasty, and profile-explicit. I ship fewer “wrong shell, wrong encoding, wrong directory” mistakes. That’s the entire ROI.
A week-by-week trim log (condensed)
Weeks 1–2: Installed themes, enabled acrylic, added every auto-detected profile, bound five new shortcuts I immediately forgot.
Weeks 3–4: Turned acrylic off after a pairing session on a bright display. Deleted unused profiles (Azure leftovers, duplicate PowerShell entries). Standardized on Cascadia Code everywhere.
Weeks 5–8: Split panes became daily. I stopped using them as a novelty and started using them as “build left / logs right.” That stuck.
Weeks 9–12: Prompt experimentation returned carefully. I allowed a minimal status segment on the personal machine only. Teaching demos stayed plain.
The pattern: novelty → friction → prune → keep only mistake-reducers.
Settings I’d hand a teammate on day one
- Solid background, high-contrast scheme, font ≥ 12.
- Profiles named by edition and intent, not by installer defaults.
- Paste warnings on; bells visual-only; startup directories explicit.
- One page of keybindings that mirror the editor—nothing more until those are muscle memory.
If your Terminal config requires a tour to explain, it’s already too loud for ops work.
If you teach or onboard people on Windows CLIs, boring-reliable beats beautiful-fragile. Interactive practice beats screenshot tours—something I keep rediscovering while building drills for CMD Master, where the prompt itself is the lesson.
What did you turn off in Windows Terminal after the novelty wore off?
