• feat: add --no-wait flag to skip exit prompt (#1872)
• feat: add string mappings for keypad parenthesis keys (#1871)
• feat: add tap-hold-tap-keys action (#1866)
• feat(linux): add VID/PID to --list output (#1857)
• fix: omit mouse activity from process-unmapped-keys (#1880)
• fix: avoid leaks in custom actions (#1853)
• fix: make td-eager first custom action press work (#1852)
• fix: clippy warnings

Download the appropriate kanata-windows-variant.zip file for your machine CPU. Extract and move the desired binary variant to its intended location. Optionally, download kanata.kbd. With the two files in the same directory, you can double-click the extracted .exe file to start kanata. Kanata does not start a background process, so the window needs to stay open after startup. See this discussion for tips to run kanata in the background.

You need to run via cmd or powershell to use a different configuration file:

kanata_windows_binaryvariant.exe --cfg <cfg_file>

Binary variants

Explanation of items in the binary variant:

• x64 vs. arm64:
  • Select x64 if your machine's CPU is Intel or AMD. If ARM, use arm64.
• tty vs gui:
  • tty runs in a terminal, gui runs as a system tray application
• cmd_allowed vs. not
  • cmd_allowed allows the cmd actions; otherwise, they are compiled out of the application
• winIOv2 vs. wintercept
  • winIOv2 uses the LLHOOK and SendInput Windows mechanisms to intercept and send events.
  • wintercept uses the Interception driver. Beware of its known issue that disables keyboards and mice until system reboot: Link to issue.
    • you will need to install the driver using the release or from the copy in this repo.
    • the benefit of using this driver is that it is a lower-level mechanism than Windows hooks, and will work in more applications.

Download the kanata-linux-x64.zip file.

Extract and move the desired binary variant to its intended location. Run the binary in a terminal and point it to a valid configuration file. Kanata does not start a background process, so the window needs to stay open after startup. See this discussion for how to set up kanata with systemd.

Example:

chmod +x kanata   # may be downloaded without executable permissions
sudo ./kanata_linux_x64 --cfg <cfg_file>`

To avoid requiring sudo, follow the instructions here.

Binary variants

Explanation of items in the binary variant:

• cmd_allowed vs. not
  • cmd_allowed allows the cmd actions; otherwise, they are compiled out of the application

The supported Karabiner driver version in this release is v6.2.0.

WARNING: macOS does not support mouse as input. The mbck and mfwd mouse button actions are also not operational.

Binary variants

Explanation of items in the binary variant:

• x64 vs. arm64:
  • Select x64 if your machine's CPU is Intel. If ARM, use arm64.
• cmd_allowed vs. not
  • cmd_allowed allows the cmd actions; otherwise, they are compiled out of the application

Instructions for macOS 11 and newer

You must use the Karabiner driver version v6.2.0.

Please read through this issue comment:

https://github.com/jtroo/kanata/issues/1264#issuecomment-2763085239

Also have a read through this discussion:

https://github.com/jtroo/kanata/discussions/1537

At some point it may be beneficial to provide concise and accurate instructions within this documentation. The maintainer (jtroo) does not own macOS devices to validate; please contribute the instructions to the file docs/release-template.md if you are able.

Install Karabiner driver for macOS 10 and older:

• Install the Karabiner kernel extension.

After installing the appropriate driver for your OS (both macOS <=10 and >=11)

Download the appropriate kanata-macos-variant.zip for your machine CPU.

Extract and move the desired binary variant to its intended location. Run the binary in a terminal and point it to a valid configuration file. Kanata does not start a background process, so the window needs to stay open after startup.

Example:

chmod +x kanata_macos_arm64   # may be downloaded without executable permissions
sudo ./kanata_macos_arm64 --cfg <cfg_file>`

Add permissions

If Kanata is not behaving correctly, you may need to add permissions. Please see this issue: link to macOS permissions issue.

03668fd658463151077a4c73c848429a8581ba907272d052eaab1c4560f590ae  kanata-linux-binaries-x64-v1.10.1-prerelease-1.zip
cc6cb4b07c188bfc7093932dd6031cd9690c262f1b8b74afe888e77b5e235089  kanata-macos-binaries-arm64-v1.10.1-prerelease-1.zip
963ebff9665cd14545e85e507bc4f9a8f8afad2294859041063548409a8814e6  kanata-macos-binaries-x64-v1.10.1-prerelease-1.zip
8ec5f54e7df5a10077e9b32ac54572d99b6e16545ab4c2d8894da5e97b163208  kanata-windows-binaries-arm64-v1.10.1-prerelease-1.zip
3e28379018a45262f480fa4d6f91ffcf0d4a3a5739cdb18d2e79ee833b3c8eb0  kanata-windows-binaries-x64-v1.10.1-prerelease-1.zip
16f01dc778edcda62a91c394ee4f8bf8ca1a0a8df5bc4400a42a696fecd9d07e  kanata.kbd