Kavanati›Articles

Kavanati for developers: the keyboard follows the app

Last updated: 13 October 2026 · 5 min read

A developer in Israel does not have a "wrong language" problem so much as a window-switching problem: the terminal wants English, the IDE wants English with Hebrew commit messages, Teams and WhatsApp want Hebrew, the browser wants both. The keyboard language stays wherever you left it in the last window. Kavanati fixes the result as you type (עןא דאשאוד becomes git status, akuo becomes שלום) and, per app, can keep the keyboard where it belongs: terminals are English-only out of the box, everything else is Auto.

The actual pain

It is not that you cannot spell. It is that you pressed Enter on ךד -ךש in the terminal because the last window was a Hebrew chat, then typed a Hebrew reply in Slack that came out as akuo nv eurv because the last window was the terminal. Windows keeps the input language per window; macOS can keep it per document. Either way, you are the one carrying the state between windows, and you get it wrong a few dozen times a day, usually at the worst moment: the first word of a command, a commit message, a search box.

Where you areWhat you wantedWhat came out
Terminalgit statusעןא דאשאוד
Terminalls -laךד -ךש
Teams / Slackשלום מה קורהakuo nv eurv
VS Code searchhandleLoginישמגךקךםעןמ
Commit messageתיקון באג בהתחברות,heui ctd cv,jcru,

What Kavanati does about it

1. Terminals are English-only, by default

A real terminal never needs Hebrew. Kavanati ships with cmd, PowerShell, Windows Terminal, conhost, mintty and bash (Windows) and Terminal, iTerm2, Warp, Alacritty, kitty, WezTerm and Hyper (Mac) set to English-only: anything typed on the Hebrew layout is retyped as English immediately and the layout switches, no detection needed. Password prompts are skipped on purpose; a password typed in the wrong layout stays wrong rather than being echoed anywhere.

2. IDEs and editors stay in Auto

VS Code, Visual Studio, Rider, IntelliJ, PyCharm, Xcode, Sublime, Cursor: these are Auto (both directions), because they host Hebrew too: commit messages, comments, the Copilot chat panel, a README in Hebrew. In Auto, Kavanati only converts a word that is clearly wrong-layout typing and leaves every real word alone; identifiers like handleLogin are not Hebrew-looking and are never touched. If you never type Hebrew in your editor, set it to English-only yourself: type in the app, open the tray menu → Per-app rules… → This app → English-only.

3. Chat and mail: fix the first word, switch the layout

In Teams, Slack, WhatsApp Desktop, Outlook and the browser, the first word after a window switch is the one that comes out wrong. Kavanati fixes it when you finish the word, switches the keyboard to the language you are evidently writing, and the rest of the sentence comes out right. The detection runs on the Hebrew ↔ English pair specifically, with word lists in both languages, so a real English word in a Hebrew sentence (or the other way round) is not "fixed".

4. Force English on focus (Pro, Windows)

One step further: when you focus an English-only app (a terminal, or an editor you set that way), Kavanati switches the keyboard to English before you type. It is the setting that makes the keyboard actually follow the app instead of correcting after the fact. Settings → Force English on focus.

5. Undo, protect, learn

What it does not do

It does not read your screen, send anything off the machine or install a keyboard layout. It hooks keystrokes locally (Windows: a low-level keyboard hook; Mac: an event tap, which needs Accessibility and Input Monitoring permissions), and its only network calls are the update check and the license check. It fixes Hebrew ↔ English only. It is not open source; the security page describes what you can verify yourself (traffic, hashes, permissions). It will not work inside a remote desktop session's remote side unless installed there, and VMs count as separate computers.

Install it like a developer

Frequently asked questions

Does Kavanati change what I type in my IDE?
Only a word that cannot be anything but wrong-layout typing, and it never touches real English or Hebrew words. By default IDEs and editors are in Auto mode (both directions), because commit messages, comments and chat panels carry Hebrew. If you never type Hebrew in an editor, set it to English-only in the per-app menu and any Hebrew-layout gibberish becomes English at once.
What happens in the terminal?
Terminals are English-only out of the box: cmd, PowerShell, Windows Terminal, conhost, mintty and bash on Windows; Terminal, iTerm2, Warp, Alacritty, kitty, WezTerm and Hyper on Mac. A command typed on the Hebrew layout is retyped in English and the layout switches. Password prompts are skipped.
Can it break a command by 'fixing' it?
It will not touch a real word, and Ctrl+Z right after a fix reverts it in one press. Undo the same word twice with the fix key and it is protected for good; the Protected words window lets you manage the list. Words you type three times join your personal dictionary and are never fixed again.
Is it free for developers?
The 7-day trial is unlimited; after that the free plan gives 15 automatic fixes a day and an unlimited one-key manual fix. Pro (₪149 once, for up to 3 of your computers) removes the daily limit and adds the personal dictionary and Force English on focus.

Related articles

← All articles