I’m happy to announce the public release of BarCuts!
Over the last few days, I’ve sanded down a few more rough edges, squashed the last (known) bugs, overhauled the app’s web page, and so we’re good to go! 
The BarCuts web page got a solid glam-up, too, and I produced a new 5-minute introduction video. I’m pretty pleased with it:
If you’ve been part of the beta (thank you!), please know that your settings and added workflow actions will not transfer over to the release version.
So, get the latest version from the website and have a look. I’m happy with how it has turned out so far, and naturally, I’m not done – I have a good number of ideas on how to hammer Shortcuts into shape, so to speak. 
And for the record, here are the latest changes that were implemented after beta 2025.0.4.
New
- Settings can now be accessed from the menu.
- The initial setup now asks you for permission to execute Shortcuts workflows. (See section on Fixes, below.)
Changes
The Tagger app selection is now more complete, and the list is now quicker to pop up. Before, it was only showing a list of installed apps which were marked as having windows. (Basically, any app contains a marker for macOS, telling it whether it’s a window-based or window-less app.) Since BarCuts’ job is reacting to you switching apps, it was logical to filter out the window-less ones. But it turns out there are some apps which are marked as window-less, yet then when they’re running, they flip that switch. For example, the very nice camera app Camo Studio starts as a menu bar app, and only when you tell it to, it’ll open a window. So, now the Tagger’s app selection will check at runtime for those apps. When you come across one of “those” apps, open one of its windows, and chances are that the Tagger will find the app.
Also, it will no longer ask you to specify an application when that parameter is empty, and the workflow is run. When the parameter is blank, the workflow is basically tagged as an always-available one.
Fixes
After getting reports of workflows silently failing (i.e., they wouldn’t run) on macOS 15.4β, I had a couple of interesting days. I discovered that other devs, too, had run into problems with the macOS-native CLI tool that BarCuts was using (/usr/bin/shortcuts). Therefore, I rewrote the workflow execution to not use that tool anymore, and implemented a different solution.