Has anyone else found the recent Autofill UI update on Android to be a major step backward in terms of user experience?

About a month ago, the Autofill behavior changed from displaying suggestions above the keyboard (keyboard accessory view) to showing an inline dropdown directly attached to the text fields. Ever since this update, it has been causing several frustrating issues:

• Flickering UI: The suggestion menu constantly flickers right beneath the text input field while trying to type.
• Focus Hijacking: When tapping a field to type manually, the Autofill prompt pops up and interrupts focus, making standard typing difficult.
• Severe Glitches / Keyboard Closure: In certain apps, the dropdown gets permanently stuck on screen. As soon as the keyboard opens, the Autofill overlay instantly forces it closed, completely blocking input.

The previous UI—where suggestions appeared quietly above the keyboard—was far more reliable, non-intrusive, and user-friendly. It stayed out of the way until needed, rather than constantly fighting for screen focus and disrupting thProposed Solution:

Rather than forcing the inline UI on everyone, please consider adding a toggle setting in the app (e.g., Settings > Autofill Style) that allows users to switch back to the classic keyboard-attached suggestions. This would give users who prefer the less intrusive, seamless experience the option to keep using it without disrupting those who like the new design.

Is anyone else experiencing these UI glitches on Android? I hope the 1Password team sees this and considers giving us the choice.

How to change 1Password autofill prompt on Firefox? I prefer the top left or the in-field prompt instead of this top center prompt

I am trying to figure out if I can export just passkeys not logins or any other data. Earlier this year, I moved away from 1Password after using it for 10–15 years. I got almost all my data moved into Apple Passwords and UpLock and it’s been working well. The one thing I don’t have are my passkeys. While this isn’t the end of the world because it’s only 15 logins, it would be nice to have them.

I researched that in iOS 26.4 or iOS 26.5 there is a new credential manager exchange process which allows you to move passkeys. However, it looks like it moves more than just passkeys. If I’m not mistaken, it moves everything, which would be a pain because I don’t want it to duplicate the logins I already have saved. So I’m looking to confirm: first, does it move just the passkeys or all login data too, as it mentions in the wording?

Second to that, my only other thought for a way around this might be to pay for a month of 1Password. Move the passkeys to a new vault, and then export just that single vault through the credential exchange process. If you foresee any problems with this logic, please feel free to chime in and tell me, as I’m all ears.

Unsure if this is best place for this but I have seen a few of these here in the past. I've used 1password since the very first beta and will die on any hill about it being the best option in almost every circumstance. I use it personally and as a team account and am trying to push it across my entire org as a org wide solution.

Having said that, I have a single feature request that may be a little more power user focused.

I run a relatively long set of keys for different services across different companies and projects I work on. Some are for github / bitbucket access, some are for ssh access, and I guess some are for different services that require ssh key authentication.

What I'd love to see is an option to have multiple agent sockets running. I have my keys spread across different vaults for their various purposes so having the ability to have different sockets that maybe are linked to individual vaults and managed through my ssh config would be invaluable to me. I get that the SSH agent communication protocol doesn't include any host details so linking host to keys isn't possible.

Further sockets can't be treated as a standard URI and passing params as a part so that's out.

The request isn't so much so I can run more than the average 6 keys but really sometimes I have to iterate through a flow of deny>deny>deny>approve before it gets the appropriate key for the request that's being done. This is particularly bad when claude is attempting to do things with git.