Support

How can we
help you?

Keyholdr is built and maintained by a solo developer. If you're running into an issue or have a question, reach out directly — responses usually arrive within a day or two.

Common questions

• The hotkey isn't working — make sure Keyholdr is running (look for the key icon in your menu bar). On macOS Sequoia, you may need to re-grant Accessibility permissions in System Settings → Privacy & Security → Accessibility.
• Touch ID keeps asking for permission — on first use, macOS shows a Keychain access prompt. Choose "Always Allow" and it won't ask again.
• Getting the CLI on your PATH — open a new terminal window after installing. Still not picking up? Add export PATH="$HOME/.local/bin:$PATH" to your shell profile.
• Using the terminal with the Mac App Store version — the App Store build is sandboxed, which limits the command-line tool inside it. For keyholdr in the terminal (including the full-screen UI), install the Homebrew or direct-download build alongside it. Open the Terminal app (search for it with Spotlight: press ⌘Space, type "Terminal", hit Return), paste this in, and press Return:
  Copy

  brew install --cask olixignacious/tap/keyholdr

  Then open a new Terminal window and type keyholdr. (You can copy this command from inside the Keyholdr app too: click the ⋯ button next to the search bar, then "Terminal Setup…".) Don't have Homebrew? Download the app from the latest release instead.
• The terminal asks for my login password, once per key — every key is its own Keychain item, so macOS asks the first time keyholdr reads each one. Choose Always Allow on each dialog and it won't ask for that key again.
• Some keys can't be read in the terminal — secrets saved by the Mac App Store version live in a protected part of the Keychain that the direct-download keyholdr can't see (and the other way round). The terminal UI names the keys it couldn't read and still copies the rest; read those from the app you saved them in, or re-add them.
• Are my notes encrypted? — no. Scratch notes are plain text in a local file, not in the Keychain and not behind Touch ID, and they aren't part of vault export. Keep API keys in Keys and use Notes for everything else.
• ⌘N opens a new file instead of a note in the terminal UI — terminal apps such as VS Code keep ⌘ shortcuts for themselves. Press Ctrl+N instead, or type the note's text and press ⏎ when nothing matches. See the CLI reference for a VS Code keybinding that forwards ⌘N.
• Restoring keys after reinstall — your secrets are stored in macOS Keychain, so they survive reinstalls as long as you stay on the same Mac and account. Use File → Export Vault before switching Macs.

Contact

For bug reports, feature requests, or anything else — email is the fastest way to reach me.