Feedback & bug reports
Rekey is in public beta, and every report makes it better. Feedback and bug reports live in one public place: GitHub Issues. Posting needs a free GitHub account — or just send an email.
Pick the right form
What makes a report useful
Rekey never sends what you type, so a wrong correction is invisible to us until you describe it. The word itself is the most valuable part of the report. Include:
- What you typed, what appeared, and what you expected. For example: typed
ішуon the Ukrainian layout, gotis, butішуshould have stayed. - The app you were typing in: Telegram, Safari, PhpStorm…
- The two keyboard layouts involved, e.g. Ukrainian and ABC.
- Your Rekey version (at the bottom of Rekey’s Settings) and macOS version.
Freezes and missed keystrokes
In Rekey’s Settings, choose Export Diagnostics… — it saves a short anonymous report: versions, settings, permissions and counters. It never contains the text you type, so it is safe to attach to a public issue.
A wrong correction, right now
Press ⌘Z within five seconds of the correction to undo it. Rekey then remembers not to correct that word again. It’s still worth reporting, so the fix reaches everyone.
Before you post
- Update to the latest beta: Settings ▸ Check for Updates…
- Search existing issues. If yours is already there, add your details to it instead of opening a new one.
- Issues are public. Don’t paste passwords, private messages or anything else you wouldn’t want others to read.
Security issues
Rekey uses the Accessibility permission and handles keystrokes system-wide, so security reports matter. Please don’t post them publicly — report them privately on GitHub. The security policy explains what’s in scope.
No GitHub account?
Write to [email protected] with the same details. Your address is used only to reply to you — see the privacy policy.