Why does universal autofill not work everywhere?

Universal autofill should work in any context, anywhere. If I want to insert a password from a login into a text document, I should be able to autofill that. If I want to paste into a password prompt inside of a terminal, I should be able to autofill that. Anywhere I want the password entered, 1password should be helping me to do it.

I don't get the design decision to block autofill unless it is in some certain known context. When I pull up quick access, find my record, navigate to autofill and press enter, shouldn't it fill my password? It's extremely confusing that it just does nothing if it does not recognize the application or context as being "valid for autofill". If I press the button, I want the action to happen.

As it is, the only thing I can do, using quick access in this context, is to hot key or navigate to "copy password" and then use the OS paste (command-v) to paste that password where I want it. This isn't awful, but it's certainly not smooth.

It would be pretty easy to add an "autofill password only" item and to let that fire in any app in any context I choose. Remembering that "autofill password only" (for later use) when I press "fill and update item" would be even better.

I hope this makes sense. Universal autofill is pretty good already. But it's pretty clunky for pasting passwords, via a terminal, into SSH sessions, sudo prompts, IPMI logins, and any other terminal based context where I need to use my stored authentication credentials.

Thanks for reading.

Brian.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided