Changed
- Fix for daemon crashes and better logging when daemon restarts
- Added chained step logging for improved debugging
- Fix for chained actions via CLI.
{{actionResult}}now works properly for--exec-actionand--run-auto - More targetted prevention for Superwhisper clipboard polution
- Superwhisper's transient clipboard types can now also speed up action execution (since it is correctly detected)
- Support for more browsers.
- Chromium
- OperaGX
- Thorium
- Wavebox
How to Update
If Installed through Homebrew
brew update
brew upgrade macrowhisper
macrowhisper --restart-service
Why do you need to re-grant accessibility permissions after update?
MacOS stores accessibility permissions tied to the absolute file path, not the application signature. Since Macrowhisper is a single binary application rather than an app bundle, when Homebrew upgrades it, the application gets placed in a version-specific folder. Each brew upgrade causes the binary to be stored at a different path, which macOS treats as a completely different application, effectively resetting the accessibility permissions.
You'll notice multiple versions of Macrowhisper appearing in your System Settings → Privacy & Security → Accessibility panel after updates. You can manually remove these stale entries when upgrading, but unfortunately there's no automatic workaround as long as you install using Homebrew due to this path-based permission system.
Alternative installation option: If you prefer not to re-grant accessibility permissions after each update, you can install Macrowhisper using the script instead of Homebrew (you do need to uninstall using Homebrew first).
If Installed with Script
curl -L https://raw.githubusercontent.com/ognistik/macrowhisper/main/scripts/install.sh | sh
macrowhisper --restart-service