Handy Tool 2.1.3

A diagnostic release for Shortcut Keeper.

Shortcut Keeper says why it did not keep a shortcut (Windows)

When you press a kept shortcut in a Remote Desktop session and Shortcut Keeper lets it through instead of running Handy, the log now names the shortcut and the reason:

• the hook not ready yet (just entered the session),
• the key or a modifier already down when the hook went in,
• a Windows key held,
• the keyboard focus outside the session window, or a full queue.

Only a kept shortcut's whole key combination, pressed with the physical keys, is ever noted. Ordinary typing, AltGr characters (ó, ł, @…) and keys sent by software (password managers, macro tools) never are.

A shortcut that reached the remote with no such line got past Handy's hook entirely, because the Remote Desktop client's own hook was in front. This tells the two apart the next time a shortcut such as Ctrl+Alt+P lands in the remote session — where, in Codex or Claude Code, it recalls your previous prompt — instead of starting a recording.

Tip: a Transcribe & Submit shortcut without a letter (for example Ctrl+Shift+F2) does no harm if it ever reaches the remote.

Install

Windows x64 — Handy.Tool_2.1.3_x64-setup.exe below. The installer is not code-signed with Authenticode, so SmartScreen will warn: More info → Run anyway. Existing installs update in place: click the version in the sidebar → Update now, or let the nightly silent update do it. (winget still offers 2.0.3; Handy updates itself from there.)

Linux — rpm, deb or AppImage. These are built but have not been tested on real hardware.

macOS — the disk images are built, but the app does not work on macOS yet.