Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
Solved
Native Password AutoFill Extension macOS
So one of the people in my family subscription for 1P relies heavily on iCloud Keychain. The nice piece about using the native autofill extension is entries from both show up together in-line. This h...
Hello folks,
The macOS AutoFill feature is now being explored in the nightly version of 1Password! If you're using a nightly build, you'll see 1Password appear as an option for macOS AutoFill.
Since nightly builds are early previews of what we're working on, this feature is still a work in progress and isn't documented. You might notice a few rough edges or areas that aren't fully implemented just yet. Our team is actively refining the experience and working through known issues as we move forward.
We're excited about where this is headed and will share more updates, and a full announcement, down the line. In the meantime, if you have questions or spot anything unexpected while using the nightly version, we'd love to hear from you!
-Dave
I think for me the investment in the safari extensions is throwing good money after bad. I have lost enough time and frustration with it. It is not worth it. I do try it still, but within 1 day if I hit a friction point or bug. And it happens everytime. I turn it off and I go another month. But it doesn’t address the inconsistency between iOS and macOS and autofill which frankly is just weird.
all the good will is gone with the extension. Even if gets better it doesn’t work when you need to use 2 password managers which works on iOS because 1Password supports native autofill.
universal autofill. I use it I like it. No passkeys though. And it doesn’t work for password prompts in iterm2 or terminal. So that stinks.and passkeys well once my wife starts using them that will mean if 1Password doesn’t support them through the native auto fill. I’ll end up having to move to something else which is just disappointing.
I think that is just Safari being Safari.
I switched to Chrome on macOS cause I got fed up with how slow and glitchy browser extensions are in Safari. The glitch extends to all other extensions as well, like the CardPointers extension that I use to enable credit card offers.
But on the other hand, I find myself having to autofill on iOS and it actually works (even if there is so much typing to begin with). It is more tedious compared to Universal Autofill, but if the feature isn't perfectly tuned, or it doesn't work how users expect it to work, what's the point anyways?
I'm just surprised why something so basic isn't implemented but a feature that probably relies on a local model is preferred because of "AI priorities".
