Cmder: a portable Windows console emulator built on ConEmu and Clink

What Cmder solves for Windows users

Windows ships cmd.exe and PowerShell, but neither gives you a console window with tabs, a readline-style editing model and a prompt that understands Git. Cmder is a software package assembled out of frustration with that gap. It wraps ConEmu for the terminal window, adds clink (with clink-completions) for GNU Readline-style editing and history search, applies a Monokai colour scheme, and adds its own prompt layout. The audience is narrow and specific: people who spend their day in cmd.exe or PowerShell on Windows and want tabbed shells, Ctrl+R history search, and a Git-aware prompt without assembling those pieces themselves.

The design constraint that shapes everything else is portability. The README states that Cmder is designed to be totally self-contained with no external dependencies, which is what makes it usable from a USB stick or cloud storage. It also bundles binaries such as wget, curl and git so that a machine without them still has a working command line. If you already have a terminal you like and only want better completion, the packaging is overhead rather than help.

ConEmu, clink and the launcher: how the pieces fit

Cmder is not a terminal emulator written from scratch. The repository layout shows the split: launcher/ holds the Cmder.exe entry point, vendor/ holds the bundled third-party components, config/ holds the shipped configuration, and bin/ and opt/ are the two user-facing drop points. Cmder.exe parses its own arguments, resolves a root directory, then hands the window to ConEmu and the shell to cmd.exe or PowerShell, with clink injected into the shell process.

The bin/ and opt/ folders behave differently, and the difference matters. According to the README, %cmder_root%\bin is injected into your PATH by default, so executables dropped there become callable from any shell Cmder starts. %cmder_root%\opt is not injected, which the README frames as giving you total control over what gets added. In practice opt/ is where you put a toolchain you want to invoke by explicit path rather than shadow something already on the system. A /max_depth [1-5] argument on init.bat controls whether subdirectories of bin are added recursively, which is worth knowing before you nest folders three levels deep and wonder why nothing resolves.

The consequence of the vendored design is that Cmder's ConEmu and clink versions move when Cmder ships a release, not when upstream does. The most recent release listed is v1.3.25 from 2024-05-31, following v1.3.24 in 2023 and v1.3.21 in 2022. Whatever ConEmu and clink versions that release bundled are the ones you get.

Installing Cmder and opening your first tab

The README gives two installation paths. The simple one is single-user portable: download the latest release, extract the archive, and run Cmder.exe. The README adds a warning worth reading twice: the extraction path should not be C:\Program Files or anywhere else that would require Administrator access to modify configuration files. Extract to a user-writable location instead.

Cmder.exe

Cmder.exe opens a ConEmu window with a Cmder tab running cmd.exe enhanced with Git, a Git-aware prompt, clink and aliases. Press Ctrl+T to open the new tab dialog if you want a second shell, or Shift+Alt+2 for a fast PowerShell tab. Ctrl+R searches your command history, and Shift plus mouse drag selects text from the buffer for copying.

The second path is a shared install with per-user configuration, which is what you want on a machine where the Cmder folder is read-only for normal users. Extract to the shared location, then launch with the /C argument pointing at a user root:

cmder.exe /C %userprofile%\cmder_config

The README states that this creates bin, config\profile.d and opt under that path if they are missing. Both the shared install and the user config location can hold a full set of init and profile.d scripts, so a shared baseline can be overridden per user. To get the Explorer right-click entry, open an Administrator terminal, change into the Cmder directory and run:

.\cmder.exe /REGISTER ALL

After that, right-clicking in or on a directory in File Explorer shows "Cmder Here". If you get Access Denied, the README says the command was not run from an Administrator prompt. /UNREGISTER [ALL, USER] removes the entry again.

Where Cmder is the wrong tool

The clearest limitation is platform. Cmder is a Windows package: the launcher is Cmder.exe, the shells are cmd.exe and PowerShell, and the context-menu integration registers a Windows shell menu shortcut. There is no macOS or Linux build here, and the repository contains no code path for them. If your team is cross-platform, Cmder solves one third of the problem.

The second limitation is the packaging model itself. Because ConEmu and clink are vendored, you cannot update either one on its own schedule without replacing files inside a release that Cmder tested as a unit. If your security process requires tracking upstream versions of terminal components, that is friction you will feel on every release.

The third is release cadence. With v1.3.25 dated 2024-05-31, v1.3.24 in 2023 and v1.3.21 in 2022, the gaps between releases are measured in months to a year. The repository's last push was on 2026-09-14, so the project is not archived, but a user who needs a fix landed upstream in ConEmu or clink this month will not get it through a Cmder release this month.

Finally, the README itself admits the documentation is incomplete: under keyboard shortcuts it notes that some shortcuts are not yet documented though they exist, and asks readers to document them. If you rely on discovering features by reading, expect gaps.

Cmder compared with Windows Terminal and plain ConEmu

The honest comparison is with ConEmu alone and with Windows Terminal, and the difference is packaging rather than terminal technology.

ConEmu is the engine. Cmder is ConEmu plus a major configuration overhaul, a Monokai colour scheme, clink and clink-completions, a custom prompt layout, and a set of bundled binaries. If you install ConEmu yourself, you choose your own clink version and your own prompt, and you maintain that configuration. Cmder makes those choices for you and keeps them in a tree you can copy to another machine. The README links to ConEmu's own page comparing the two, which is the right place to look if you want the maintainers' framing of the differences.

Windows Terminal comes from the opposite direction: it is a first-party terminal that is not tied to cmd.exe, is not portable in the USB-stick sense, and does not bundle git, curl or wget. Cmder's advantage is that the whole environment travels with you, including aliases and binaries, and that it works on a machine where you cannot install anything. Windows Terminal's advantage is that it is maintained on a platform cadence and is not a wrapper around a vendored copy of another emulator. Pick based on whether portability or platform currency matters more to your situation.

Licence, maintenance and upgrade cost

Cmder is MIT licensed. That is permissive: you can use, modify and redistribute it, including in commercial settings, provided the licence notice is preserved. The repository also ships a SECURITY.md, so there is a stated channel for reporting vulnerabilities. This is not legal advice; read the LICENSE file in the repository and the licences of the vendored components under vendor/ before you redistribute a modified build, because Cmder's MIT licence does not automatically relicense ConEmu, clink or the bundled binaries.

Upgrade cost is low but not zero. Because the package is self-contained, upgrading means extracting a new release over or beside the old one and carrying your configuration forward. In the shared-install model, the per-user config lives under the /C path rather than inside the install tree, which is exactly what makes an in-place upgrade of the shared folder safe for user settings. The portable single-user model has no such separation: your aliases, profile.d scripts and anything in bin/ live inside the folder you are replacing, so back that folder up before you extract a new release over it.

Maintenance status should be read from the facts rather than the tone of the README. The repository is not archived, and the last push was on 2026-09-14. The newest tagged release listed is v1.3.25 from 2024-05-31.

Editorial conclusion

Adopt Cmder if you want a self-contained cmd.exe and PowerShell console that carries its aliases, binaries and colour scheme on a USB stick or a synced folder, and if you are willing to keep a packaged ConEmu rather than a current one. Do not adopt it if you need a GPU-accelerated terminal, native macOS or Linux support, or a shell whose vendored components you can update independently of the wrapper. Before committing, verify three things: that your extracted path is outside C:\Program Files so configuration writes do not need Administrator rights, that %cmder_root%\bin is actually on your PATH after launch, and that the /C user config directory is created where you expect it. The last release is v1.3.25 from 2024-05-31; check the release page before assuming a newer build exists.

Frequently asked questions

Official sources

1. cmderdev/cmder on GitHub
2. License: MIT
3. Project website
4. README
5. Releases