Edson C. Souza

I can confirm the exact same behavior on my machine. Having SecureEventInput enabled continuously while the vault is locked effectively breaks system-wide keyboard interception tools (CGEventTap), affecting everything from custom hotkey daemons and window managers to automation utilities, with zero UI indication as to why. The lifecycle hook for EnableSecureEventInput() / DisableSecureEventInput() should strictly track the active focus state of the master password input field (e.g., NSControlTextDidBeginEditingNotification / NSControlTextDidEndEditingNotification or resignFirstResponder), rather than being coupled to the locked state of the vault. Holding this lock while the app is minimized, in the background, or completely without active window focus contradicts the intended scope outlined in the release notes. Please prioritize scoping the event tap lockout strictly to focused sensitive inputs.

+1

I would like to see this feature too

I would like to see this feature too