Trigger stage: capture keywords quickly
SnipKey listens for triggers prefixed with # across the system, so it works in any app that accepts text input.
SnipKey is a macOS menu bar text expansion tool. Type #trigger in any app to open a cursor-following completion panel and expand saved text without breaking your flow.
The page follows the real usage flow first, cuts unnecessary decoration, and explains the most important capabilities before anything else.
SnipKey listens for triggers prefixed with # across the system, so it works in any app that accepts text input.
Use arrow keys to move, Tab or Enter to confirm, and Esc to cancel.
Embed {date}, {time}, {clipboard}, and {cursor} directly inside snippet content.
Grouping, search, create, edit, delete, and JSON import/export all live in one native settings window.
The shortest path comes first, so new users understand the flow before digging into details.
Launch the app from the menu bar and start managing your reusable text snippets in Settings.
Create a Key such as account and enter the replacement text or variable-based template you want to insert.
Go back to chat, docs, email, or any other text field, then type #account to see matching candidates.
Confirm with Tab, Enter, or a terminating character, and SnipKey replaces the typed trigger automatically.
This section keeps only the shortest path. The full setup details still live in the repository docs.
make signing-help
make bootstrap-personal-team
make run
# If an Apple Development certificate is already available:
make test
make run
Full signing instructions live in docs/development-signing.md
Listing the important paths directly saves users from hunting through the repo the first time they need them.
~/Library/Application Support/SnipKey/snippets.json
~/Library/Application Support/SnipKey/clipboard-history.json
Jump from here to source code, docs, releases, or issue tracking without hunting through the repository.
Browse source code, build instructions, commit history, and releases.
Open repository →Review the project structure, requirements, testing strategy, and common commands.
Open README →If you want stable permission behavior while debugging locally, this document explains the full workflow.
Open signing guide →Report site issues, product suggestions, or general usage problems.
Open issues →