Docs · Troubleshooting
When something is not firing.
Most issues come down to a key conflict, a field that blocks input, or a macro that ran ahead of the page. Here is how to spot and fix each one.
A shortcut is not firing
First check for a conflict: the same key may already be mapped to another action, or the website itself may capture that key before HotKeyNavigator sees it. Conflict detection flags clashes when you map a key — if a site is greedy with a combination, pick a different one. Some browser-reserved combinations (like Ctrl+T) can never be intercepted by an extension.
My shortcut clashes with the website
A few web apps bind their own shortcuts to plain letter keys. If yours stops working only on one site, the page is likely claiming the key. Remap the action to a combination the site does not use, or scope it to a profile so it only loads where there is no conflict.
Text expansion is not triggering
Expansion only runs while your cursor is in an editable field — a text box, textarea, or rich editor. It will not fire in a read-only area or while focus is on a button. A small number of editors block programmatic input for security; if a specific field refuses to expand, that field is the cause, not the extension.
A macro replays too fast or skips steps
Real pages do not load instantly. If a macro clicks before an element exists, add a wait-for step or increase the per-step delay so it pauses until the page is ready. Use the built-in test-run to watch each step land before you bind the macro to a key.
My JavaScript function throws an error
Functions run in the context of the page, so open the browser DevTools console to see the error exactly as the page reports it. A few sites set a strict Content Security Policy that limits what injected scripts can do — if your code works everywhere except one domain, the site CSP is the likely limit.
My setup did not appear on another computer
Configuration is stored locally on each device by default. Cloud sync — which carries your shortcuts, templates, functions, and profiles to every machine and survives a reinstall — is a Pro feature. On the free plan, set up each device independently or upgrade to sync automatically.
My settings disappeared after reinstalling
Uninstalling an extension clears its local storage, so a fresh install starts empty. With Pro cloud sync, signing back in restores everything. Without it, re-import a backup if you exported one — which is why sync exists.
The extension stopped responding after a browser update
Manifest V3 extensions run on a background service worker that the browser can suspend. After a browser or extension update, reload the open tab so the content script re-attaches. If it still misbehaves, toggle the extension off and on from the browser extensions page.