keyhac-key-table-configuration

Add a binding by assigning an action to a key expression in a key table, such as kt["Ctrl-K"] = some_action, then reload the config. The Skill reads the file first, makes a minimal edit, reloads it, and confirms placement with describe_keymap.

Use a key table with an app= condition matching the application name, which is stable across window titles. For conditions based on a kind of control like a text field, use focus_path_pattern= read from the live focus path via describe_keymap.

Common causes are a later key table overriding the same key, a condition that never matches, or a config that failed to load leaving the old one running. Platform issues like Cmd- on Windows or Fn-arrow keys on macOS also produce silently dead bindings.

Yes, one config.py runs on both platforms, but modifier names differ: Cmd- and Fn- never fire on Windows, and Win- never fires on macOS. Cross-platform configs should branch on keymap.platform or use the LEADER and MOD constants.

Only partially. It can confirm via describe_keymap that the binding loaded, sits in the intended table, and is not overridden, but it cannot press keys. The user must press the key to confirm the action does what they expect.

Use an action when the goal goes beyond a keystroke, such as driving another application's UI, reading a table, or filling a form. Actions are Python classes in ~/.keyhac/extensions/ that you bind to a key once written.