Blog
Why Capslock works the way it does, how it is built, and what changed in each version.
How Capslock works: F18, an event tap, and a mapping it gives back
Caps Lock is a poor modifier as macOS delivers it. Capslock remaps it to F18, reads it from an active event tap, and changes only the part of the system key mapping it owns.
Capslock goes native
Capslock started as a Karabiner-Elements configuration. It is now a native Mac app that keeps the same layout and adds an editor, app rules, lessons, and a way to always get Caps Lock back.
Capslock 0.4.0
A clearer first run, lessons that follow your configuration, Profile behaviour for unmapped keys, verified recovery feedback, and plain statements of what stays local.
Capslock 0.3.0
Safer keyboard recovery, stricter configuration handling, more reliable pointer controls, and editor and diagnostics fixes. Internal build.
Capslock 0.2.0
The complete Classic layout becomes the default, the editor puts all sixteen planes and the whole keyboard on one screen, and the Caps key gets explicit semantics. Internal build.
Capslock 0.1.0
The first native build: Capslock Classic built in, two Hyper modes, a native editor with per-app overrides, Hold-to-Reveal, the Playground, and diagnostics. Internal build.