Most daily computer frustration is a mode error. You typed a paragraph in the wrong alphabet, Caps was on, or a shortcut did the destructive thing because the window underneath was not the one you thought. ModeGuard is a layer that makes the machine state visible, undoes the mistakes that come from getting it wrong, and holds back the ones you cannot undo.
ModeGuard started as one request, rebind a key to switch keyboard language, and grew into the layer that should have been there all along.
A low-level keyboard hook, so a bound shortcut is genuinely captured rather than fired a moment too late. The layout toggle is instant because it runs inside the engine.
Caps, the active keyboard layout and the modifiers you are holding are shown where you can see them, before you write three paragraphs in the wrong alphabet.
Typed a line in the wrong layout? ModeGuard rewrites it in the right one instead of making you delete it and start again.
The shortcuts that delete, overwrite or close without saving can be held for a confirmation, set per application rather than globally.
If a binding collides with something your browser or editor already owns, ModeGuard tells you instead of quietly winning the fight and confusing you later.
Graphite, Midnight, Phosphor, Daylight and Linen. All driven by design tokens, so a theme is data rather than a fork of the interface.
ModeGuard is in build. The engine works and the portable build runs, and we would rather say that plainly than dress it up as shipped.
The portable build is running and we are looking for a small group of people who lose real time to mode errors every day. Tell us what your keyboard keeps doing to you and we will send it over.
