Troubleshooting

When a shortcut suddenly stops working or behaves in a way you didn’t expect, this is the place to start. Most keyboard trouble comes from one of three things: another app is fighting Uncapped for the same key, something overwrote the remapping that powers the Hyper Key, or Caps Lock is simply doing its new job instead of its old one. Each section below describes a symptom in plain terms and walks through the fix.

Uncapped also keeps an eye out for the first two of these on its own. When it spots trouble it shows a small red warning dot next to the Settings item in the sidebar, and the Settings screen has two sections — Possibly Interfering Apps and Keyboard Remapping Conflicts — that name the likely culprit. The fixes here pair with those two sections.

The Hyper Key stopped working

You press your Hyper Key (Caps Lock by default) and nothing happens — even though Uncapped still shows it as enabled. This almost always means another keyboard tool has quietly taken over your Caps Lock key.

To make the Hyper Key work, Uncapped reassigns Caps Lock deep in the system so the rest of macOS sees it as a spare key (F18) it can build shortcuts on. If you run a second tool that also remaps Caps Lock — another Hyper Key app, for instance — whichever one acted last wins, and Uncapped’s mapping gets overwritten. Everything in Uncapped still looks correct, which is what makes this so confusing.

There are a few variations, but they all have the same feel — the key looks set up but does nothing:

Another app has pointed your Caps Lock (or whichever trigger you chose) at a different key, so Uncapped’s mapping never takes effect.
Uncapped’s own mapping has been overwritten and is now missing.
Another tool wrote a mapping as it quit that silently overrides Uncapped’s, leaving the key dead even though that other app is no longer running.

How to fix it:

Open the Settings screen and look at the Keyboard Remapping Conflicts section. If something else is remapping your key, Uncapped flags it here with a warning.
Find the other keyboard tool and either quit it or turn off its Caps Lock remapping. The Possibly Interfering Apps section just above often names the responsible app.
Click Rescan in that section to re-check. A common culprit is another “Hyper Key” utility — popular ones include Superkey and Raycast.
If the key is still dead after the other tool is gone, toggle the Hyper Key off and back on on the Hyper Key screen (this re-applies Uncapped’s mapping), or simply restart Uncapped.

For the technically curious. Uncapped powers the Hyper Key by mapping Caps Lock → F18 through the system’s HID UserKeyMapping property. It writes this mapping globally with hidutil; some other tools (Superkey, Raycast) write theirs per-device using IOKit, which a global query doesn’t see — so Uncapped reads back both the global mapping and each connected keyboard’s per-device mapping, then compares what’s actually live against what it expects (Caps Lock → F18 while the Hyper Key is on, nothing while it’s off). Anything else mapping the same key — including a “key → itself” mapping some tools leave behind on quit — is reported as a conflict.

If your trouble is specifically that the Hyper Key keeps switching off whenever you quit another keyboard app, Uncapped can re-apply itself automatically — see Hyper Key ▸ Recovery.

A shortcut fires twice or behaves oddly

A shortcut works most of the time, or does something slightly wrong — fires twice, inserts stray characters, or triggers a different action than you set up. When a shortcut is inconsistent rather than completely dead, the usual cause is another app handling the same key press first.

Uncapped isn’t the only kind of app that responds to your keyboard. Launchers, text expanders, and automation tools all act on your keystrokes too, and when two apps both react to the same press, they can step on each other. Common examples are Raycast, Alfred, Keyboard Maestro, and text-expansion utilities.

How to fix it:

Open the Settings screen and check the Possibly Interfering Apps section. Uncapped lists every other app it can see handling the keyboard right now, each with its icon and name.
Quit one of the listed apps — start with whichever one you suspect owns the misbehaving shortcut — and test again.
Click Rescan after quitting an app to confirm it’s no longer in the list.
If you need to keep that app running, change its shortcut (or Uncapped’s) so the two no longer share the same key.

For the technically curious. Uncapped keeps no hard-coded blocklist of apps. It asks macOS for the list of active keyboard event taps — the mechanism apps use to handle input — and resolves the ones handling key events back to the apps that created them, filtering out its own taps and Apple’s built-in services. Because it’s based on actual behavior rather than a list of names, it even catches command-line tools and daemons (such as skhd or yabai) that have no normal app window.

Caps Lock no longer types capitals

You press Caps Lock expecting capital letters and nothing happens. This isn’t a bug — it’s the Hyper Key doing exactly what it’s meant to. When the Hyper Key is on, your Caps Lock key becomes the Hyper Key, so it no longer toggles capitals the way it used to.

If you’d like capitals back, you have three options, all on the Hyper Key screen:

Keep both. Turn on Enable Quick tap and set On tap to Toggle Caps Lock (its default). A quick tap of the key then toggles capitals as normal, while holding it still works as the Hyper Key. See Hyper Key ▸ Quick Tap.
Hold for capitals. Turn on Long press toggles Caps Lock so that holding the key down toggles real Caps Lock, while a quick tap runs your chosen tap action. See Hyper Key ▸ Long Press.
Give Caps Lock back entirely. Change the Trigger key to a different key (such as Right Command) so Caps Lock returns to normal, or turn the Hyper Key off altogether. See Hyper Key ▸ Choosing your trigger key.

Sending diagnostics to support

If none of the fixes above help, Uncapped can put together a diagnostics file that shows what it sees on your Mac. Sending that file along with your message usually gets you an answer much faster than describing the problem from memory.

How to create it:

Open the Settings screen and scroll to the Troubleshooting section.
Turn on Detailed logging.
Use your Mac as normal until the problem happens again. If the trouble starts right after you log in or restart, restart now — detailed logging stays on across restarts.
Go back to the same section and click Export Diagnostics…. Uncapped saves a text file and shows it in Finder.
Attach that file when you contact support, and mention roughly when the problem happened.

Detailed logging turns itself off after 24 hours, so there’s nothing to remember to undo. You can also export without it — the file is still useful, just less detailed.

What’s in the file. It’s plain text, so you can open it and read it before you send it. It contains:

Your macOS version, Mac model and Uncapped version.
Which Uncapped features are switched on and how they’re set up.
Whether Uncapped has the permissions it needs, and whether another app is currently blocking keyboard access.
Other apps that handle the keyboard, and connected mice.
A recent history of what Uncapped did: starting up, switching features on and off, and any errors it ran into.

What’s never in the file. Uncapped does not record what you type, the text of your snippets, anything you’ve copied to the clipboard, or your licence key. With Detailed logging on it does note which shortcuts you pressed — for example a key pressed while holding the Hyper Key — because that’s what’s needed to see why a shortcut misfired. Ordinary typing is only counted, never recorded.

Nothing is uploaded. The file stays on your Mac until you choose to send it.

Settings FAQ