chrisant996 /clink

Bash's powerful command line editing in cmd.exe

★ 5,600⑂ 212👁 42⑃ 47● 763▤ 288
C++GPL-3.0Created 2020-09-12chrisant996.github.io/clink/
Download: v1.9.36v1.9.36 ↓1.9.362026-11-09
+1
Daily
5,600
stars
212
forks
42
watchers
47
prs
763
issues
288
releases

README

Overview

Clink combines the native Windows shell cmd.exe with the powerful command line editing features of the GNU Readline library, which provides rich completion, history, and line-editing capabilities. Readline is best known for its use in the Unix shell Bash, the standard shell for many Linux distributions.

For details, refer to the Clink documentation.

 [!NOTE]
 Starting Clink injects it into a cmd.exe process, where it intercepts a handful of Windows API functions so that it can replace the prompt and input line editing with its own Readline-powered enhancements.

 Download

Downloads are available from the releases page.

See the issues page for known issues or to file new issues.

 Feature Highlights

- Auto-Suggestions; Clink offers suggestions as you type based on history, files, and completions.
- Completions; Clink can complete words when you press Tab or Ctrl-Space (interactive completion list).
- Persistent History; Clink stores persistent history between sessions.
- Scriptable Prompt; You can customize the prompt dynamically with Lua scripts -- like in other shells -- but never before possible in cmd.exe!
- Colored Input Line; Your input is colored by context sensitive completion scripts.
- Command Line Editing Improvements; Clink supercharges the command line with new input editing commands and configurable key bindings.
- Auto-answering of the "Terminate batch job?" prompt.
- and much more!

 Installation

You can install Clink by running the setup EXE file from the releases page.

Or by using winget and running winget install --id chrisant996.Clink -e.

Or by using scoop and running scoop install clink.

Or by downloading the ZIP file from releases page, and extracting the files to a directory of your choosing.

 Usage

Once installed, there are several ways to start Clink.

1. If Clink is configured for autorun, just start cmd.exe and Clink is automatically injected and ready to use.

     The setup EXE has an option "Autorun when cmd.exe starts".  If you didn't use the setup EXE, or if you want to enable or disable autorun later, you can run clink autorun install or clink autorun uninstall to change the autorun configuration.  Run clink autorun --help for more info.

2. To manually start, run the Clink shortcut from the Start menu (or the clink.bat located in the install directory).
3. To establish Clink to an existing cmd.exe process, use clink inject.

     If the Clink install directory isn't in the PATH, then use install_dir\clink in place of clink to run Clink commands.  Once Clink is injected into a cmd.exe process, then it automatically sets an alias so that you can simply use clink.

You can use Clink right away without configuring anything:

- Searchable command history will be saved between sessions.
- Tab and Ctrl-Space will do match completion two different ways.
- Press Alt-h to see a list of the current key bindings.
- Press Alt-Shift-/ followed by another key to see what command is bound to the key.

See Get

Top issues

Discussions

Latest release

v1.9.36 v1.9.36 2026-11-09
- Fixed console.settitle to preserve an Administrator prefix, if present.
- Fixed an edge case that could cache failed ahead/behind counts (regression introduced in v1.9.35).
- Fixed 915; 500 ms startup delay in conhost on Windows 10 (regression introduced in v1.9.35).
- Reduced logging noise in the clink.log file:
  - Suppress log entries about resetting mismatched stdout/stderr handles; it's normal and frequent, and doesn't need log entries.
  - Only log history statistics when trimming to fit history.max_lines or when compacting history to remove lines marked for deletion.
- Log begin

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON