> Supported apps and known limitations

> Works reliably

• Slack (native macOS app)

  Message composer, thread replies, and search. Corrections land after a space or punctuation just as in a plain text field.

• Telegram (native macOS app)

  Chat input and captions. Emoji shortcodes and mentions are unaffected because only the finished word is inspected.

• Safari

  Standard HTML inputs and textareas — search boxes, forms, comment fields. No extra setting is needed.

> Requires the Chrome helper

Chromium reports text differently from native controls, so Chrome support is a separate switch in TextSwitcher Settings. Turn it on, then restart Chrome once. With it enabled these have been verified:

• Google Chrome — inputs and textareas

  Search fields, login-style forms (never password fields), and comment boxes behave like native fields.

• ChatGPT

  The prompt composer is a rich-text editor; TextSwitcher reconstructs the current word from keystrokes when Chromium does not expose normal text events.

• Lovable

  The chat/prompt field is corrected the same way, which is how mistyped Russian prompts get repaired before you send them.

• Asana comments

  Rich-text comment fields were specifically fixed in 1.2.0; a space reliably completes the word and triggers correction.

> Not supported or limited

• Secure fields (passwords, passphrases, 2FA codes)

  Skipped by design. macOS marks these fields as secure and TextSwitcher never reads or edits them, even with Accessibility granted.

• Browsers other than Chrome and Safari

  Firefox, Arc, Edge, Brave and other Chromium forks are untested. Some Chromium forks may partly work with the Chrome helper on, but nothing is guaranteed.

• Apps that draw their own text engine

  Terminal-style emulators in canvas mode, virtual machines, remote desktop sessions, and games render text themselves and expose no editable field to correct.

• Text selected or edited out of order

  If a selection is active, or the caret is moved back into an earlier word, correction is skipped rather than risking an edit in the wrong place.

• Third-party input methods and dictation

  Non-standard input sources and voice dictation bypass the keystroke path the app relies on.

> Common reasons it may not work in a supported app

1. Accessibility was granted to an old copy. Replacing the app in /Applications leaves a stale entry — remove it and re-add the current build.
2. The app was launched before permission. Quit and reopen TextSwitcher after granting Accessibility.
3. Chrome was not restarted after enabling the Chrome helper.
4. The word was never finished. Nothing is corrected until you type a space, punctuation, or Return.
5. Only one layout is installed. Both English and Russian input sources must exist in System Settings → Keyboard.

Step-by-step fixes live on the troubleshooting page. If an app in the “works reliably” list fails for you, email support@antari.io with the app name and macOS version so it can be reproduced.