Heblish
Heblish quietly catches the moment you typed a Hebrew word on the English keyboard, or vice versa, and fixes it in place — switching the input source so your next word lands in the right layout.
Each time you finish a word — by hitting space, return, or punctuation — Heblish asks one question: does this word make sense in the language the keyboard is set to?
If the answer is no, Heblish maps the word to the other layout's keys and checks: is that a real word? Hebrew is checked against macOS's built-in spell checker; English uses the system word list and the spell checker together.
If only the other-layout word is real, Heblish erases what you typed, switches the input source, and types the correct word. Your next word lands in the right language. If it ever guesses wrong, ⌥⇧X within two seconds undoes the fix and adds the word to an ignore list so it never auto-fixes that word again.
| ⌥⇧Z | Manually fix the current word before you've hit space. |
|---|---|
| ⌥⇧X | Undo the last auto-fix (within 2 seconds and only if you haven't typed anything else). Adds the word to the ignore list. |
| ⌥⇧I | Take whatever text is highlighted in the foreground app and add each word to the ignore list. |
Heblish does not make a single network call. Ever. You can verify it yourself.
URLSession, no Network.framework, nothing./usr/share/dict/words and macOS's bundled NSSpellChecker — both fully local.IsSecureEventInputEnabled() short-circuits it.~/Library/Application Support/Heblish/ignore_list.txt, with mode 0600. You can read or delete it any time.akuo → שלום, vch, → הביתיקךךם → hello,usv → תודהtr. → ארץ, xu; → סוףI,צ → I'm, Hקךךם → HelloI'm, don't, can't.Adi, Tom, Friday.PT, USA, OK — even when followed by punctuation.I, am, is, to) where the layout ambiguity is too strong to call.Accessibility is the macOS permission that lets an app observe keystrokes system-wide. That's what Heblish does — it reads each key you press to decide whether a word might be in the wrong layout. The same permission is what Karabiner, Alfred, Rectangle, BetterTouchTool, and similar apps use. The observation happens entirely locally; nothing leaves your Mac.
Mac App Store apps must run in App Sandbox, which doesn't allow the kind of system-wide keystroke observation Heblish needs. Apps like Karabiner-Elements, Hammerspoon, BetterTouchTool, and Alfred all distribute directly for the same reason. Heblish is signed and notarized by Apple, so macOS opens it without the "unidentified developer" warning — it just isn't in the App Store's catalog.
Heblish currently assumes the standard Israeli "Hebrew" input source (not "Hebrew – QWERTY" or "Hebrew – PC"). If you use a different layout, the key-to-letter mapping will be off. Let me know — adding additional layouts is straightforward.
Yes. Open the file at ~/Library/Application
Support/Heblish/ignore_list.txt in any text editor (one word per
line), save, and click Reload in the Heblish menu.
Yes — it uses Sparkle, the open-source auto-update framework. Updates are signed with EdDSA and downloaded from this domain. You'll see a gentle prompt when a new version is available; you can install it, skip it, or disable update checks entirely in the menu.
That is the right question to ask of any app that requests
Accessibility permission. The short answer for Heblish: it's signed
and notarized by Apple, makes no network calls (verifiable with
nm on the binary), and the source code can be reviewed.
If you want a hard guarantee, block it at the firewall — it doesn't
need the network for anything.
Yes. If you find it useful and want to support development, that's always appreciated — but there's no payment required.