How to Configure Text Replacements in Charm
Charm does not have its own text replacements feature. Instead, it works seamlessly alongside macOS's built-in Text Replacements system, found in System Settings > Keyboard > Text Replacements. Set up abbreviations there to expand into full phrases. Charm then handles error correction and word prediction on top of the expanded text. Together, they cover both proactive phrase expansion and reactive error fixing.
How macOS Text Replacements work with Charm
The two systems handle different jobs and layer on top of each other cleanly.
macOS Text Replacements are proactive. You define a short abbreviation - such as ;;sig - and every time you type it in a native macOS app, the system immediately replaces it with the full text you assigned (your email signature, a long URL, a standard reply). The expansion happens before you finish the word. It is triggered by you, on purpose.
Charm is reactive. It monitors text as you type and corrects spelling, grammar, and awkward phrasing in real time. It does not know or care about your abbreviations - it simply corrects whatever text is in the field. Once macOS expands your abbreviation into a full phrase, Charm reads the expanded result and corrects any errors within it.
In standard native apps - Mail, Notes, Pages, Messages - the two systems coexist without any special configuration. macOS fires first, expands the abbreviation, and Charm then applies its corrections to the result. You get both phrase expansion and error correction from a single keystroke sequence.
Setting up Text Replacements for use with Charm
Adding text replacements takes about two minutes. Here is the setup path:
- Open System Settings on your Mac.
- Go to Keyboard, then select Text Replacements.
- Click the + button at the bottom left to add a new entry.
- In the Replace column, type your abbreviation. In the With column, type the full phrase.
- Press Return to save. The replacement is active immediately across all supported apps.
Best practice for abbreviation naming: use a distinctive prefix like ;; for every abbreviation. Examples:
;;sig- your email sign-off;;addr- your mailing address;;ty- "Thank you for getting in touch, I will respond within one business day.";;meet- your calendar booking link;;ph- your phone number
The ;; prefix matters for two reasons. First, it makes abbreviations visually distinct and easy to remember. Second, double semicolons do not appear in normal prose, so Charm will not attempt to correct the abbreviation before macOS has a chance to expand it. More on this in the conflict section below.
A well-configured set of 30 to 50 text replacements saves an average of 20 minutes per day for heavy email users. The initial setup investment pays back quickly.
Where Text Replacements don't work - and how Charm Oracle helps
macOS Text Replacements rely on Apple's text input system, which only operates inside native macOS apps. They do not work in Electron apps - this includes VS Code, Slack, Discord, Notion, and many other popular tools. Electron apps run their own rendering engine and bypass Apple's text handling entirely. This is an Apple-level limitation, not a Charm limitation.
If you type ;;sig in Slack's desktop app, nothing will happen. macOS never sees the keystroke in a way that triggers the replacement.
This is where Charm Oracle fills part of the gap. Oracle is Charm's word prediction feature. It learns the phrases you type most often across every app - including Electron apps - and suggests completions as you type. While Oracle does not do literal abbreviation expansion, it surfaces your frequent phrases as you begin typing them, providing a similar speed benefit through prediction rather than replacement.
If you need true abbreviation expansion in Electron apps, the best solution is a third-party tool like Typinator, which hooks into keyboard input at the system level and works across all apps including Electron. Typinator and Charm can run alongside each other without conflicts.
Avoiding conflicts between Text Replacements and Charm
In practice, conflicts are rare - but they can occur if an abbreviation looks like a plausible typo. For example, if you set sig as an abbreviation (without any prefix), Charm may attempt to correct it to "big", "sir", or another nearby word before macOS gets the chance to expand it.
The ;; prefix convention solves this completely. Charm's correction engine sees ;;sig as an unusual character sequence that does not resemble any English word. It will not attempt to correct it. macOS then fires its replacement as expected.
A few things to check when testing your setup:
- Type the abbreviation in Apple Notes or Mail first - native apps are the most reliable test bed.
- If a replacement does not fire, check that Text Replacements is enabled in System Settings and that the specific app supports it. Some third-party native apps disable the feature.
- If Charm appears to be altering the expanded phrase in an unexpected way, use Charm's per-app settings to adjust correction sensitivity for that application.
;; as a prefix for all your abbreviations. It keeps Text Replacements and Charm cleanly separated, and the double semicolon is fast to type with muscle memory.
Frequently asked questions
Does Charm have its own text replacements?
No. Charm does not include a text replacements feature. It works alongside macOS's built-in Text Replacements system in System Settings > Keyboard > Text Replacements. Charm handles error correction and word prediction; macOS handles abbreviation expansion. The two layer on top of each other in any native macOS app.
How do I use text replacements with Charm?
Go to System Settings > Keyboard > Text Replacements and add your abbreviations there using the ;; prefix. Once you type an abbreviation in a native app, macOS expands it. Charm then corrects any errors in the expanded text. No additional configuration is needed - they work together automatically.
Do text replacements work in VS Code with Charm?
macOS Text Replacements do not work in Electron apps like VS Code or Slack - this is a system-level limitation, not related to Charm. Charm still runs in those apps for spelling and grammar correction. For phrase prediction in Electron apps, Charm Oracle learns your common phrases and suggests them as you type. For full abbreviation expansion in Electron apps, use a tool like Typinator alongside Charm.
How do I stop Charm from correcting my text replacement abbreviations?
Use the ;; prefix for all your abbreviations (for example, ;;sig instead of sig). The double semicolon is not a word pattern Charm recognises as a typo, so it passes through uncorrected. macOS then expands it as normal. This prefix convention also makes abbreviations faster to remember and less likely to fire accidentally mid-word.
Charm handles correction. You handle expansion.
Pair Charm with macOS Text Replacements for a complete writing setup. $9.99, yours forever.