Skip to main content
Oct 10, 2026 8:48 AM UTC

feature suggestion: intentional random delays in universal login

Universal Login - the feature clicking through login processes - often triggers protection mechanisms of shops, because of 1Password filling all in way faster than usual humans.

Therefore I’d suggest random delays which mustn’t be long, just random. Either in typing single digits or in a delay between filling out textboxes and clicking buttons to avoid 1Password triggering security blocks and lockout delays of users simply using that feature. It should basically mimic a skilled human typing instead of looking like a bot trying to hack into accounts.

3 replies

1P_Dave
1Password Employee
1Password Employee
Oct 20, 2026 3:57 PM UTC

Hello ​@paradonym! 👋

Thank you for the feedback and the suggestion! Would you be able to provide a few examples where you ran into this issue? I’d like to share these with our development team. 

And does turning off auto-submit on those websites help: 

  1. Click on the 1Password icon in your browser’s toolbar. 
  2. Find and select the item in question. 
  3. Click the three dots in the upper right corner of the item. 
  4. Click Don’t sign in automatically. 

-Dave

paradonymAuthor
Oct 20, 2026 6:10 PM UTC

Hi ​@1P_Dave 
Just now I had problems with a process of Google SSO authentication on Referral Links of claude.ai (because they contain individual parts I can’t share them here). Do log out of Google itself, open claude.ai - for my current case it was a referral link of another user - and 1Password clicks through the entire process in speed, which was kind of like Claude.ai button click, popup for Google Sign-In, Google username, Google Password, Google 2FA selection (like Passkey or 2FA Code), which resulted in a message that Google doesn’t allows that login, because of it all being like two seconds or right after the browser actually displayed the contents (like milliseconds after the Browser Dev tools would say that the page loaded completely)…

Had been fixed by just trying it again, which resulted in a way slower process, maybe not via the 1Password “speed” anymore (because I had to manually select my 2FA, but the user message from Google straight out was “your browser can’t be trusted”, which would be a reason a non-technical user would be pretty worried about.