I’m repeatedly running into a very frustrating issue where BetterTouchTool keyboard shortcuts stop working on macOS Tahoe because Secure Input becomes active.
BTT currently shows:
Secure Input enabled by: Finder (PID: 670). Shortcut functionality is limited.
But this is not limited to Finder. I have also seen the same warning with Chrome and ChatGPT. The app shown as the Secure Input source changes from time to time.
Environment:
macOS: Tahoe / macOS 26
BetterTouchTool version: 6.640 (2026071312)
Mac model: [your Mac model]
Issue:
BTT keyboard shortcuts suddenly stop responding. When I check the BTT menu, it says shortcut functionality is limited because Secure Input is active. This has happened multiple times with different apps shown as the source, including Finder, Chrome, and ChatGPT.
I keep BTT updated, but the issue still occurs.
I have tried:
Updating BTT
Restarting BTT
Restarting macOS
Rechecking Accessibility permissions
Rechecking Input Monitoring permissions
Quitting the app shown as the Secure Input source
The problem still comes back.
This makes BTT shortcuts unreliable during daily use.
I understand that Secure Input is a macOS feature and may not be directly controlled by BTT, but I would like to know if there is any recommended workaround, diagnostic option, or setting that can help with this on macOS Tahoe.
Is this a known Tahoe issue?
Is there anything BTT can do to recover more reliably after Secure Input is released?
Can I provide logs or additional information to help debug this?
I use a tiling window manager (Aerospace) and so secure input really can block me using my system or navigating away from the secure input field , in general I see more problems with Aerospace being blocked while BTT is still responsive. The solution is to try to close the requestor that is causing the block. In an earlier Tahoe I feel like I got input-blocked more than I do in the latest release?
With BTT only some types of keyboard shortcuts can not work while secure input is active - most work fine with recent BTT versions even if secure input is active. What kind of shortcuts are you trying? FN based ones?
In general if the responsible secure input app is constantly changing it usually means the system has not determined which app activated secure input correctly and the attribution is incorrect.
Do you have any security tools installed? Some corporate security suites enforce secure input at all times, which can lead to such weird behavior. (Unfortunately in that case there is no real workaround apart from switching to shortcut types that work with secure input)
//edit: but as @iandol mentioned that setting needs to stay active!
I’m not using FN-based shortcuts. I’ve attached two screenshots of my BTT shortcut setup.
Most of my shortcuts are regular key-based triggers. They mainly launch apps, run Shell Script / Task actions, or run AppleScript actions. Examples include launching Finder, Cursor, Calculator, Terminal, Notion, etc.
I don’t have any corporate security software installed. This is a personal Mac, not company-managed, and I’m not using MDM, antivirus software, CrowdStrike, SentinelOne, Jamf, Microsoft Defender, or anything similar. It’s basically a standard macOS setup.
As mentioned earlier, the Secure Input source reported by BTT changes between Finder, Chrome, ChatGPT, and other apps, so I understand that macOS may be attributing the source incorrectly.
Could you clarify whether single-key triggers are affected by Secure Input, and whether switching to modifier-based shortcuts such as Cmd+Option+letter would make them more reliable?
This seems to be happening much more frequently in recent weeks. I'm on Tahoe 26.5.2. BTT 6.06. I rarely use BTT for keyboard shortcuts, but have recently started using the hyperkey. And that stops working entirely when secure input is activated.
For now, it seems to be working fine when I follow the steps for replying from 1Password to the post you shared. I'll keep an eye on it for a little while longer! https://x.com/1Password/status/2080769769947419135
, in general I see more problems with Aerospace being blocked while BTT is still responsive. The solution is to try to close the requestor that is causing the block. In an earlier Tahoe I feel like I got input-blocked more than I do in the latest release?
