Just type. Heblish handles the language switching.

Whether you started a word in the wrong layout or simply didn't bother to switch, Heblish notices what language you meant, fixes the word in place, and moves the input source there — so your next word lands right too.

Download for macOS Requires macOS 13 or later · Apple Silicon & Intel · ~2 MB

akuo

שלום

tr.

ארץ

I,צ

I'm

How it works

1. It watches words, not keystrokes

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?

2. It tries the other layout

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.

3. It rewrites and switches

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.

Hotkeys

`⌥⇧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.

Privacy

Heblish never sends your text anywhere — the autocorrect engine is entirely local and makes no network calls. The one part that does use the network is the update checker: it checks whether a newer Heblish exists, both on a periodic background schedule and when you pick "Check for Updates…" yourself. Either way it fetches only a signed version feed — nothing about you or what you type. You can verify it, or block it at the firewall.

The autocorrect engine reads keystrokes entirely locally and links only Apple frameworks (AppKit, Carbon, ApplicationServices). Your typed text is never transmitted.
The only networked component is the update checker (the open-source Sparkle framework). It checks for a newer version on a periodic background schedule and whenever you choose "Check for Updates…" from the menu — either way it fetches only the signed update feed and sends none of your text or any personal data.
The dictionaries it uses are /usr/share/dict/words and macOS's bundled NSSpellChecker — both fully local.
Your buffered word lives in RAM and is wiped whenever you finish a word, switch apps, lock the screen, or quit.
Heblish never buffers when a password field, sudo prompt, or Touch ID dialog is active. macOS's IsSecureEventInputEnabled() short-circuits it.
The only file Heblish writes is your ignore list, at ~/Library/Application Support/Heblish/ignore_list.txt, with mode 0600. You can read or delete it any time.
You can put Heblish behind any firewall (Little Snitch, LuLu, macOS's built-in) and block all outgoing traffic. Autocorrect works identically — you just won't be able to check for updates.

What it handles well

Hebrew typed on English: akuo → שלום, vch, → הבית
English typed on Hebrew: יקךךם → hello
Words starting with ת: ,usv → תודה
Words ending with ץ / ף: tr. → ארץ, xu; → סוף
Mixed scripts when shift produces a Latin literal on Hebrew layout: I,צ → I'm, Hקךךם → Hello
Cascading mistakes: if you type several words in the wrong layout, Heblish fixes each one independently.

What it deliberately leaves alone

Real English contractions like I'm, don't, can't.
Proper nouns like Adi, Tom, Friday.
Acronyms like PT, USA, OK — even when followed by punctuation.
Two-letter words (I, am, is, to) where the layout ambiguity is too strong to call.
Any word you've put on the ignore list, either by undoing a fix or by adding manually.
Anything typed into a password field.

FAQ

Why does Heblish need Accessibility permission?

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.

Why isn't Heblish on the Mac App Store?

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.

Does Heblish work with non-standard Hebrew layouts?

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.

Can I edit the ignore list directly?

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.

How does Heblish update?

Heblish checks for a newer version automatically in the background, and also whenever you pick "Check for Updates…" from the menu. Either way it fetches a signed update feed (EdDSA-verified) and, if a newer version exists, offers to install it — nothing is downloaded or installed without your say-so. The check fetches only the version feed; it never sends your text. Updates download from GitHub Releases, and it uses Sparkle, the standard open-source update framework. Prefer fully manual? Block Heblish at the firewall and check whenever you like.

Can I trust an unfamiliar app to read my keystrokes?

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, and it never transmits your text — its only network activity is checking for its own updates. The source code can be reviewed. If you want a hard guarantee, block it at the firewall — autocorrect needs nothing from the network.

Is Heblish free?

Yes. If you find it useful and want to support development, that's always appreciated — but there's no payment required.

Changelog

1.3.1 July 10, 2026

Multi-word correction: short ambiguous openers are fixed retroactively once the rest of the sentence makes the intended language clear.
Smarter layout switching: correcting a single borrowed word mid-sentence no longer flips your keyboard layout out from under you.
Sentences opening with a shift-typed "I" ("I have…") now correct properly on the Hebrew layout, even when the garbled word collides with a real Hebrew word.
Short-word corrections must land on a common English word, eliminating a class of rare-dictionary-word misfires.
Reliability: fast typists' words typed immediately after a correction are no longer missed.

1.2 July 1, 2026

Fixed handling of the comma key on the Hebrew layout.

1.1 June 30, 2026

Fixed issues with the geresh / apostrophe key.

1.0 June 24, 2026

Initial public release.
Auto-correct of layout-mistyped Hebrew and English words on word-boundary.
Manual fix, undo, and ignore-selection hotkeys (⌥⇧Z / ⌥⇧X / ⌥⇧I).
Persistent ignore list with full edit and clear controls.
Mixed-script handling for shifted Latin literals on Hebrew layout.
Proper-noun and acronym suppression.
Asymmetric recent-context heuristics tuned against a 50-sentence corpus.
Signed and notarized by Apple; opens with no "unidentified developer" warning.
Automatic and manual update checks via Sparkle (EdDSA-signed).