Secure Input blocking other apps event taps

Hi,

1Password 8.12.26-31 mentions in it’s Release Notes

We’ve fixed an issue where 1Password could keep Secure Input enabled longer than intended.

I’m on 1Password for Mac 8.12.32 (81232018) and I can still reproduce the issue both with the repro steps pitnikola and I mentioned.

It’s quite blocking in my workflow so I will try out Keeper app if the migration is easy. But feel free to reach out for me to test again if you fix it.

Hi ​@adilerchouk, I’m sorry for any confusion caused here, and for the continued disruption to your workflow. The fix you’ve highlighted in our release notes was for a different issue with 1Password and Secure Input. The issue you’ve reported is still being worked on at the moment.

Thanks for checking back in about this, and for your kind offer to test a fix once one is released!

For weeks I’ve been seeing a recurring issue on an M2 MacBook Pro running macOS 26.5.2 (25F80). When it occurs:

• Fn-E won’t open the emoji picker
• Fn-Fn won’t start Dictation
• Alfred snippets stop expanding
• Keyboard Maestro typed-string triggers stop working
• Sometimes the emoji picker opens, but clicking an emoji doesn’t insert it

Running:
ioreg -l -w0 | grep SecureInput

shows that Secure Input is active. Different processes have appeared as the owner, including Proton Mail, Capture One, and loginwindow. In one case, Proton Mail’s PID remained listed even after Proton Mail had quit.

The reliable workaround so far is to unlock 1Password. Immediately afterward, Secure Input clears, ioreg returns no result, and Fn-E, Dictation, Alfred snippets, and Keyboard Maestro all begin working again.

Restarting CharacterPalette, TextInputMenuAgent, TextInputSwitcher, SystemUIServer, Dock, and pboard did not fix it. Logging out and back in does.

Has anyone else seen Secure Input become stuck like this, particularly after sleep/wake? Any idea what might be causing it, or how to clear it properly without relying on 1Password or logging out?

Updated:
Moments ago when I returned to my computer, Apple Music had supposedly captured Secure Input! I think this is an issue with MacOS.

Hi ​@kappabear, I’m sorry to hear you’ve been running into issues with 1Password and Secure Input as well.

To confirm, does the behaviour you’re seeing match the behaviour others have mentioned in this thread - that is, it happens when your device locks/sleeps while 1Password is running, and locked but not focused on your screen, and once you wake your device, that’s when Secure Input is reported as being held by various other processes?

This secure input bug is really annoying, and I don't think even the usually awesome 1Password team has been able to fix it. Instead of closing and reopening the 1Password app, I found a much quicker way to get back to work. Just enter the following commands in the Terminal app, and you can continue working immediately:

killall "1Password Helper"

killall "1Password Helper (Renderer)"

killall "1Password-BrowserSupport"

On my MacBook, Terminal runs in the background all day.

—Carsten

This is extremely frustrating. I rely on several accessibility and efficiency tools—including Superkey and Keyboard Cowboy—to navigate my Mac. When 1Password leaves Secure Input enabled, those applications stop receiving global keyboard shortcuts.

I’ve upgraded to the latest 1Password release, but the problem persists. Focusing 1Password and then switching to another application—or quitting and reopening 1Password—releases Secure Input, but this is only a temporary workaround. Please prioritise a permanent fix. Thank you.

System information

• macOS 26.5.2 (25F84), Apple Silicon/arm64
• MacBook Air (Mac17,3), Apple M5, 24 GB RAM
• 1Password for Mac 8.12.33
• 1Password for Brave extension 8.12.32.33
• Brave 151.1.93.134
• Superkey 1.66
• Keyboard Cowboy 3.28.4
• Karabiner-Elements 16.0.0

Relevant 1Password configuration

• Touch ID and device-based unlocking enabled
• Idle auto-lock: 60 minutes
• “Lock when device locks or sleeps” currently disabled as a workaround
• SSH Agent enabled
• Developer features enabled
• CLI and SDK shared lock state enabled
• Local MCP integration enabled

Symptoms

• The failure usually appears after the Mac sleeps or is locked and subsequently wakes.
• Superkey and Keyboard Cowboy stop detecting global shortcuts.
• Secure Input remains active even though 1Password is in the background and no password field is visibly focused.
• ioreg may report loginwindow or whichever application is currently focused rather than 1Password.
• Bringing 1Password to the foreground and switching away often immediately clears the condition.
• If that fails, quitting and reopening 1Password clears it.
• Logging out also clears it, presumably because the process holding Secure Input is terminated.

This behaviour closely matches the reproduction already reported in this thread: 1Password auto-locks during a lock/sleep transition and its unlock field appears to retain Secure Input after wake.