Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Universal Autofill (CMD+\) not working with latest Chrome on macOS (142.0.7444.60)
With the latest update of Chrome on macOS, Universal Autofill’s CMD+\ is no longer working properly with the Chrome extension.
Problem: CMD+\ does not automatically autofill form fields on any website.
Instead, you see the “Search 1Password” quick access popup, which indicates it does not detect the website you are on when you press CMD+\
- macOS version: Sequoia 15.7.1
- 1Password for Mac version: 8.11.16 (81116035 on PRODUCTION channel)
- Google Chrome version: 142.0.7444.60
- 1Password extension version: 8.11.16.35
Additional troubleshooting information:
- 1Password “Connect with 1Password in the browser” is checked/enabled
- 1Password extension “Integrate this extension with the 1Password desktop app” is enabled and “Integration status” shows “Connected 🟢”
- The following does not fix this problem:
- Quitting 1Password and Chrome, and restarting both
- Removing and reinstalling the 1Password browser extension
- Restarting my computer
- 1Password Beta extension version 8.11.18.30 has the same problem
33 Replies
I just want to chime in here and say that I've also been experiencing this issue, and have been going back to at least early September. I contacted customer support at that point in time, and they didn't seem to realize this was a known issue.
I echo the sentiment that this has been a pretty significant disruption. It's frustrating that it still hasn't been resolved, especially given the significant percentage of 1Password's user base that must be on Mac and using Chrome or other Chromium browsers.
At the very least, I would hope that the 1Password team would be able to offer some timeline so that its customers can have a reasonable expectation as to when this will be working normally again. But I'm not finding anything of the sort in this thread.
I've been a loyal 1Password customer for about 15 years. I may have to reconsider that loyalty if this issue persists much longer.
- 1P_Dave
Moderator
alexcr and gloreglabert
I’m really sorry for the ongoing disruption this has caused, I know how frustrating it is when things don’t work as expected. Our development team is actively investigating the issue. We’ve identified that 1Password is currently having trouble reliably collecting field information in Chromium-based browsers. This doesn’t affect non-Chromium browsers like Safari or Firefox, where the issue doesn’t occur.
Right now, we’re testing a few different approaches to improve the reliability of how we gather field data from pages opened in Chromium browsers. I’ll be sure to keep this thread updated as soon as we have any progress or new information to share. For the time being, the following workarounds exist:
- Use 1Password in the browser (the browser extension) to fill your login information into Chromium browsers instead of using Universal Autofill: Get to know 1Password in your browser
- Use a non-Chromium browser like Safari or Firefox if you'd like to continue to use Universal Autofill.
Thanks so much for your continued patience while we work on this.-Dave
1P_Dave Any feedback on the option of updating the extension to allow the same behavior to be accomplished with a single keystroke via the extension mentioned earlier in this thread? That approach should have no OS dependencies and would allow us to mimic the behavior of "Universal" autofill. From what I remember this used to be possible via the "old style" extension before universal autofill existed.
I think it's very clear that 1Password doesn't view this (or home and/or Mac users more broadly) as any kind of priority. The sole reason I'm still using 1Password at this point is inertia -- I've been a user for about the same length of time as you. I would never recommend it to anyone as a new user, and this is a perfect demonstration of why -- core functionality of the product is unreliable and effectively unmaintained.
Exactly. That's what's particularly frustrating here: This is what I think most people would consider to be "core functionality." As such, the lack or urgency in addressing this...it's just unacceptable.
Hi 1P_Dave, just wanted to check in on this since the last update mentioned coordination with Apple and other partners. Has there been any movement or new insight since then?
Universal Autofill still isn't usable for me in Chrome, and it's unfortunately a pretty big disruption to my daily workflow, so I'm very eager to know if there's anything new to share or try.
Thanks a lot for looking into this, much appreciated 🙏🏼.
macOS: Version 26.2 (25C56)
Chrome: 143.0.7499.170
1Password: 8.11.22 (PRODUCTION)- 1P_Dave
I’m sorry for the ongoing disruption to your workflow. I’ve taken another look, and there aren’t any new updates yet; the details in this post are still the most up to date.
-Dave
Thanks for checking again and for the update, 1P_Dave. Looking forward to this being resolved.
I assume there are no updates here? It seems we're either (1) waiting on Apple to change something in macOS, (2) waiting on the dev team to patch the problem, or (3) the issue isn't sufficiently high priority for the dev team to devote real attention to. But either way, at some point it starts to feel disingenuous to advertise a "Universal Autofill" feature that doesn't work on the most popular browser platform, hasn't worked in months, and the only notice of that is buried in a community forum.
- 1P_Dave
reub, gloreglabert, dndrsn, prox
I'm sorry for the continued impact that the issue is causing. Our development team's initial investigation revealed an issue with how the macOS accessibility API reports form field information from Chromium windows to the 1Password desktop app's Universal Autofill feature (Command-Backslash). We've reported this to Apple and we're currently working with our partners there to find a resolution to the issue. Universal AutoFill continues to work in non-Chromium apps.
Since the issue involves Chromium, macOS, and 1Password, I don't have an ETA on when this will be resolved. For the time being, the two best workarounds are:
- Use 1Password in the browser (the browser extension) to fill your login information into Chromium browsers instead of using Universal Autofill: Get to know 1Password in your browser
- Use a non-Chromium browser like Firefox if you'd like to continue to use Universal Autofill. I know that this won't be possible for most people but I wanted to mention it just in case it helps.
I'll continue to provide any updates that I can as our team works to resolve this issue together with our partners.-Dave
1Password in the browser doesn’t address the problem completely. With 1Password in the browser, it now requires 2 keystrokes/mouse clicks instead of 1 keyboard shortcut to autofill fields.
- Keyboard shortcut to open 1Password in the Browser
- Enter / click to Autofill
Can an option be added to 1Password in the browser so it behaves like Universal Autofill and autofills automatically? It should autofill automatically if there’s a login that matches the domain and only 1 login for the domain; otherwise, the browser extension popup should show with the login matches for you to choose from.
1P_Dave Given the impact of this issue and the time elapsed, would you consider offering more information for users whose experience is impaired until this is fixed? As others are noting as well, just knowing that 1Password is aware of it is neither a commitment or a timeline (even an anticipated one).
So...is this an issue that the development team is planning to actually fix? I understand that they're "aware of" the issue, but it's apparently been affecting some Chromium-based browsers for months, and that it's now been affecting all of them for several weeks. Coupled with the lack of communication and the fact that several 1Password updates have come and gone without any fix, that doesn't make me confident that it's actually ever going to be fixed.
Is there actually work in progress to get this fixed, or at what point should we assume that this is basically a dead feature that won't be coming back?
FWIW, this has been an issue with Brave for months. It started affecting Chrome more recently. This makes 1P far less useful for me. If the browser extension had a keyboard shortcut to autofill the same way with a single keystroke, this wouldn't be such an issue.
Oh, that’s not promising, but since Chrome is used by around 70% of people worldwide, I hope the 1Password team will jump on it and fix it quickly.
Adding yet another voice to the pile. This issue is wasting my time on a daily basis and the fact that it's been ongoing for over a week with no material updates is not promising...
Little update:
I've tested Microsoft Edge and Brave and there it doesn't work as in Chrome. Only magically works for me in Arc, not sure if it will helps with anything, but decided to share.
Came here to post same. CMD \ used to autofill browser forms now brings up search 1pw and wants to set main pw for Chrome app not browser.
Chrome 142.0.7444.60 (Official Build) (arm64)
- 1P_Dave
