How to Use Slack-Style Emoji Shortcuts Anywhere on Your Mac

If you live in Slack, you’ve trained your fingers to reach for :fire:, :joy:, and :+1: without thinking. Then you switch to Messages or Mail and the muscle memory breaks, you’re back to hunting through the macOS emoji picker (Control-Command-Space) like it’s 2015.

The good news: colon emoji shortcuts aren’t a Slack feature, they’re a typing habit. And you can bring that habit to every text field on your Mac.

Why the emoji picker isn’t enough

The built-in picker is fine for browsing, but it’s slow for the handful of emoji you actually send. It steals focus, it’s mouse-driven, and it doesn’t know that “whiskey” means 🥃. Apple’s Text Replacements can map one alias at a time, but maintaining a giant replacement table by hand is nobody’s idea of fun, and it has no autocomplete, so you have to remember every trigger exactly.

The fix: live colon autocomplete

What you actually want is autocomplete: start typing a colon token, see matching emoji ranked by relevance, and accept the one you want with Tab. That’s exactly what Comoji adds, system-wide.

1. Type a colon and the start of an alias, e.g. :whis.
2. A small popover appears next to your cursor with the best matches.
3. Use the arrow keys to move the selection (recent picks rank higher).
4. Press Tab or Return to insert the emoji and keep typing.

Because Comoji works at the keyboard level, the same shortcuts work in Messages, Mail, Notes, TextEdit, Safari, Chrome, Notion and most other apps, not just one. It ships with the full Unicode emoji set and the gemoji aliases Slack itself uses, so the names already in your head, :tada:, :eyes:, :rocket:, just work.

Setting it up: two permissions

Comoji is a small menu bar app. Download the DMG, drag it to your Applications folder (do this before granting permissions, more on why below), and launch it. On first run it walks you through the two permissions macOS requires for any keyboard utility, both in System Settings › Privacy & Security:

• Input Monitoring, lets Comoji notice when you type a colon token like :fire.
• Accessibility, lets it read the active text field and insert the emoji.

Which Macs it works on

Comoji supports macOS 13 Ventura or later, which means Ventura, Sonoma, Sequoia and the latest macOS 26 Tahoe, on both Apple silicon and Intel Macs. The behavior is identical across versions; the only thing that changes between macOS releases is the exact wording and layout of the Privacy & Security pane.

Troubleshooting: shortcuts aren’t firing

If :fire isn’t turning into 🔥, it’s nearly always a permission that didn’t stick. Work through these:

• Confirm both toggles are on in System Settings › Privacy & Security, under both Input Monitoring and Accessibility. One without the other isn’t enough.
• Re-grant after an update. macOS sometimes drops permissions when you update the OS or the app. The fix: select Comoji in each list, remove it with the − button, then add it back (or just toggle it off and on), and relaunch Comoji.
• Don’t move the app after granting. If you granted permissions and then moved Comoji to a different folder, macOS treats it as a new app. Keep it in /Applications, that’s why we grant after moving it there.
• Check your disable list. In Preferences › Privacy you can turn Comoji off per app or per website. If it works everywhere except one app, it’s probably on that list.
• Password fields stay quiet on purpose. Comoji ignores secure input fields, so shortcuts won’t fire in a password box or password manager. That’s expected, not a bug.

Writing code or timestamps? Change the trigger

The colon is perfect until you’re writing code, JSON or 12:30-style timestamps, where a stray popover is annoying. In Preferences › Shortcuts you can swap the colon for another token-opening key, semicolon, slash, backslash, @, #, ~ or |, and Comoji rewrites every suggestion and example to match. You can also add the specific apps where you don’t want it firing at all to the per-app disable list.

Where it works (and the rare place it doesn’t)

Because Comoji acts at the keyboard level, it works in native apps (Messages, Mail, Notes, TextEdit) and in web text fields too, so the same :emoji: flow works in Slack’s web app, Gmail, Notion, Linear and most sites, across Safari, Chrome, Edge, Arc and Brave. A handful of web editors that fully take over text input (Google Docs is the usual one) can be hit or miss, since they don’t expose a normal text field. For those, the :: browser still inserts reliably, and you can always add a specific app or site to the disable list if you’d rather it stand down there.

It still feels native

A tool like this only works if it disappears. Comoji is conservative by design: it only intercepts Tab/Return while the popover is visible, resets aggressively on clicks and app switches, and never fires on a partial match unless you ask it to. If it isn’t sure you’re typing a shortcut, it does nothing, false negatives over false positives, always.

And it stays private

Reading keystrokes sounds scary, so it’s worth being precise: Comoji processes input locally only to detect colon tokens. It doesn’t log what you type, never uploads message contents, and ignores secure password fields entirely. There’s no account and no cloud, the core app makes no network calls at all.

Bring your Slack reflexes everywhere. Download Comoji, grant the two permissions, and your next :fire: is one Tab away.