Known limits & feedback

Known limits

Password fields. While a password field has focus, macOS hides every key from every app (Secure Input). A chord fired inside a password field can’t be seen: fire it in the username field and let {tab} move on. The hint says Secure Input is on when this happens. Some apps (Terminal’s “Secure Keyboard Entry”, 1Password) turn Secure Input on globally while open.

Google Docs, Sheets and Slides: pending. Rich paste (md, table) into Google’s editors isn’t verified yet. Plain text chords work there. If you try md/table in a new blank Doc or Sheet, tell us what you see.

Mac App Store build: limits. A future App Store version runs sandboxed:

the config lives inside the app’s container; a custom “Config folder…” isn’t available yet;
file: chords pointing outside the container won’t work until folder access is built;
run: aos actions may be removed if Apple’s review requires it;
no licence keys (Apple handles payment). The alpha you’re testing is the direct download, which has none of these limits.

Also:

Office (Word, Excel, PowerPoint) gets shapes and diagrams as pictures, not editable shapes. Editable shapes are Excalidraw only.
${selection}, ${last} and shape keys are macOS only for now.
Games and some remote-desktop clients read the keyboard below where keychord works.
Each new alpha build may need its Accessibility and Input Monitoring grants removed and re-added (see Updating).
Drive sync (optional): deleting a file on one Mac doesn’t delete it on the others yet.

Send feedback

The quickest way is the WhatsApp tester group. For anything longer, the form below opens your email app with the report filled in.

A good report: what you did, what you expected, what you saw, your macOS version, and the output of keychord doctor --json. Screenshots: one window only, never your whole screen, and nothing private in it.