Take Command v36 vs. Windows Terminal: Two Different Visions of the Command Line

For decades, Windows users have wrestled with the limitations of the default command-line environment. Today, two tools offer different approaches to solving that problem: JP Software’s Take Command v36 and Microsoft’s Windows Terminal.

At first glance, they seem comparable—both offer tabbed interfaces, modern visuals, and improvements over the classic console. But under the hood, they serve fundamentally different purposes. This article explores those differences.

The Core Distinction: Toolkit vs. Terminal

Before diving into features, it’s critical to understand the architectural difference:

• Windows Terminal is a terminal emulator. It is not a shell; instead it hosts shells like TCC, CMD, PowerShell, or WSL.
• Take Command 36 is a complete command-line environment—a terminal, command processor / shell, scripting platform, and IDE. It replaces both the terminal and the command processor / shell with a fully integrated solution. And Take Command also supports TCC, CMD, PowerShell, and WSL.

User Interface: Tabs vs. Workspace

Both tools support tabbed consoles—but the similarity ends there.

Windows Terminal

• Tabbed interface for multiple sessions
• Split panes

Take Command 36

• Tabbed windows plus vertical/horizontal tab groups and splitters
• Detachable and reconfigurable tab layouts
• Optional integrated Explorer-style file manager for drag-and-drop operations
• Toolbars, status bars, and configurable UI components

In short: Windows Terminal modernizes the Windows console; but Take Command transforms it into a full workspace.

Command Power: Hosting vs. Enhancing

Windows Terminal

Windows Terminal doesn’t add commands—it simply hosts existing shells.

If you want more power, you rely on:

• PowerShell scripting
• External tools
• WSL environments

Take Command v36

Take Command includes TCC, a command processor compatible with the default Windows shell CMD, but massively enhanced to include:

• Extensive command line editing features
• Full Unicode support, including UTF-16 and UTF-8
• 220+ additional internal commands
• 800+ built-in variables and functions
• User-defined aliases and functions
• Integrated Internet support, including HTTP(S) and FTP(S) for file commands (copy, del, dir, move, etc.)
• Advanced batch scripting (DO loops, SWITCH, event monitoring, exception handling)
• Regex support for filename selection, and extended wildcards
• Many automation commands, variables, and functions
• Plugins for commands, variables, functions, and command line editing. Plugins can be written in C/C++, or any .NET language
• Integrated support for multiple scripting languages, including Python, Lua, REXX, and Tcl/Tk

TCC remains compatible with CMD while dramatically expanding its capabilities.

Take Command doesn’t just host commands—it reinvents them.

Productivity Features: Minimal vs. Comprehensive

Windows Terminal

• GPU rendering and performance improvements
• Customizable themes and fonts

These are quality-of-life enhancements—not workflow transformations.

Take Command v36

Take Command focuses heavily on productivity:

• Performance improvements (faster output than Windows Terminal)
• Customizable themes and fonts
• Full Unicode support (UTF-16 and UTF8)
• Integrated batch debugger and IDE
• Syntax coloring and advanced command-line editing
• Macro recording and playback
• Built-in file viewer, search/replace, and regex tools
• Event monitoring and automation triggers

It effectively merges:

• Terminal
• File manager
• Scripting engine
• Development environment

Customization: Appearance vs. Behavior

Windows Terminal

• Themes, fonts, colors
• JSON-based configuration
• Profiles for different shells

Take Command 36

• Themes, fonts, colors
• Deep customization of:
  • Commands
  • Aliases
  • Variables
  • UI layout
  • Toolbars and workflows
• Plugin support and extensibility

Use Cases: Who Should Use What?

Choose Windows Terminal if:

• You primarily use PowerShell, CMD, or WSL

Choose Take Command 36 if:

• You rely on batch scripting or automation
• You want a unified GUI + CLI workflow
• You need advanced command extensions and debugging tools
• You value productivity features over simplicity

Final Thoughts

Comparing Take Command 36 to Windows Terminal is less about “which is better” and more about what problem you’re solving.

• Windows Terminal modernizes the Windows command-line experience.
• Take Command 36 redefines it.

If your needs stop at running shells more comfortably, Windows Terminal is an excellent choice. But if you’re looking for a power-user environment that integrates scripting, debugging, file management, and automation into a single interface, Take Command stands in a category of its own.

That distinction—terminal vs. toolkit—is the real takeaway.