Need a hand? Most answers are below. If you’re still stuck, email hello@swiftlab.co.uk and a real person will help.
Installing Nimble
- Download the latest build and open the
.dmg. - Drag Nimble into your Applications folder.
- Launch it. Because Nimble is signed with an Apple Developer ID and notarized by Apple, it opens without Gatekeeper warnings.
Nimble requires macOS 14 Sonoma or later and runs on Apple silicon and Intel Macs.
Activating your license
After you buy, Lemon Squeezy emails you a license key. Each license includes 2 activations.
- Open Nimble. The Activate screen appears on first launch.
- Paste your license key.
- Click Activate. Every feature unlocks immediately.
Your key and a per-install identifier are stored securely in the macOS Keychain.
Lost your key, or managing your license
You can view and re-send your license key, and see your activations, from the Lemon Squeezy customer portal:
Moving Nimble to a new Mac
Your license includes 2 simultaneous activations. To free one up, open Nimble → Settings → Deactivate License Key on the old Mac, then activate on the new one. You can also manage activations from the order portal above.
Activation troubleshooting
- “License key does not exist.” Double-check for a stray space when pasting. Re-copy the key from your Lemon Squeezy email.
- “This license could not be activated.” You may have reached your activation limit, deactivate on a Mac you no longer use, or contact us to reset it.
- Offline? Nimble validates licenses online but keeps working if validation can’t reach the network, so a brief outage won’t lock you out.
Setting up Quick Commit
Quick Commit lets a global hotkey commit the repository of whatever app is in front of you. Because it reads the frontmost app, macOS asks for Accessibility permission the first time. Grant it under System Settings → Privacy & Security → Accessibility, then toggle Quick Commit on in Nimble’s settings.
Git authentication
Nimble uses your existing Git setup. For SSH remotes, make sure your key is
added to your agent (ssh-add); for HTTPS remotes, your credential helper or a
personal access token is used. Credentials are stored in the macOS Keychain,
never in plaintext.
Still need help?
Email hello@swiftlab.co.uk. Include your Nimble version (from Nimble → About) and a short description, and we’ll get back to you.