Protect what matters – even after you're gone. Make a plan for your digital legacy today.
"Add New" search suggestions could be smarter
When I add a new item, and type "bank", I expect the first suggestion to be "bank account". Doesn't that make sense? Instead, I'm shown a list of what I guess are "popular logins" -- various banks that have "bank" in the name. Key Bank, US Bank, M&T Bank, PNC Bank, Royal Bank. Does 1Password think these are the best banks and wants me to have accounts with them? Does it really think it's more likely I'm trying to create a login for one of these, than that I'm simply trying to enter a new bank account? If I look farther down the list, I see some other categories listed: logins, secure notes, credit cards, with the suggested titled: "bank". Does 1Password think I'm trying to create a new credit card item, with title "bank"? No, that's not what I want... Why is "bank account" not at least shown here? I have to click "show all categories" to see it -- the search does not prioritize it over any of the other categories. Even if I type "bank a", the top result is to add a new "Bank of America" login. Only when I type "bank ac" does the new item "bank account" finally filter to the top of the list. That's what I should see from the start! My suggestion is to prioritize new category titles as the first-returned search results when adding a new item. The fact that the "Add New" screen shows (before starting a search) all these new categories at the bottom, makes it seem natural that typing their names would filter that list of categories. But what currently happens is, they are hidden after searching. One unrelated point about the new "Add New" screen: the tiles at the top are not useful to me. I will never click "Getting Started" and "Most Popular Logins" because I've been using 1Password for years. And the "Cryptocurrency Basics" -- I am not interested, and I wish 1Password would not try to push this on me! Must I look at these tiles every time I add a new item? Meanwhile, the list of categories below this is great: simple and nicely displayed. But the overall behavior would be improved if the top results of a search would simply filter these categories (as I've described above). 1Password Version: 8.6.0 Extension Version: Not Provided OS Version: macOS 11.6.3
[Bug] "Title" field triggers password input, disabling non-English keyboards
Environment: App Version: 8.12.8 BETA OS: Android 16, OneUI 8.0 Keyboard: Gboard Description: When creating or editing a Login item in the 1Password Android app, tapping the "Title" field incorrectly triggers Gboard's strict password mode. Because Android handles password fields with extreme strictness, this forces the keyboard into an English-only QWERTY layout and completely disables the ability to use other language inputs (such as Chinese Pinyin). This is clearly an unintentional inputType configuration bug rather than a deliberate privacy feature. Tapping the "Username" field directly below it correctly triggers a standard incognito text mode (similar to Chrome incognito tabs). The Username field protects privacy by preventing dictionary learning, but still respects the user's active keyboard language and allows normal typing. The Title field should behave exactly the same way. Steps to Reproduce: Open the 1Password Android app and tap to add a new Login item (or edit an existing one). Tap into the Title text field. Observe: Gboard switches to a strict password layout (disallowing language switching or non-QWERTY input). Tap into the Username text field. Observe: Gboard switches to a standard incognito layout, safely preventing dictionary learning while still allowing language switching and normal typing. Technical Context & Suggested Fix: The "Title" field appears to be incorrectly assigned an inputType of TYPE_TEXT_VARIATION_PASSWORD (or similar). The "Username" field is already using the correct implementation—likely utilizing IME_FLAG_NO_PERSONALIZED_LEARNING combined with a standard text class. The Title field needs to be updated to match the Username field's configuration so international users can type vault item names in their native languages without being locked into English QWERTY. Impact: This causes severe friction for non-English users or anyone utilizing a multilingual keyboard setup, as it makes typing native-language titles for vault items incredibly frustrating or impossible without external workarounds.
What's new in the About window links to wrong page
When one clicks on "What's New" on this window, I would expect to read the changes in the new Beta (8.10.74-19). But the URL that opens is https://releases.1password.com/mac/8.10/#changelog => that is the changelog of the Production version, not the Beta. BTW: The title of the Settings window is still a mess!
Browser Beta: Feedback regarding the new sign-in experience
So I was suddenly being upgraded to this new experience today, however, it does not seems to be appearing on the https://releases.1password.com/b5x/beta/#changelog. I guess making the login selection up above resolves one very specific issue - sometimes it can annoying to have 1P prompting under a text box, especially when filling in forms. But I don't think this new design is the answer. Main issue - Long mouse travel - Instead of just flicking my mouse to choose my account, I now have to move my mouse all the way top to click it, which is never a trade off I would take to fix the "filling in the form" issue. Secondly, it was not visually better to have a much larger pop up blocking my web view whenever I am logging in.The Advanced setting "Release channel" is not respected
Hi! I did set my 1Password 8 App to the "nightly" builds channel a few weeks ago. At present, I am running: 1Password for Mac 8.11.22 / 81122010, on NIGHTLY channel My advanced setting for the channel is: PRODUCTION / install updates automatically When I click the "Check for updates" button in the About panel, always a new nightly build is installed. I just got 81122010 a few minutes ago. I also tried to set to BETA, but no new beta build has been installed for weeks, although new beta versions were announced on the website. How can I make sure that 1P does really install builds from the correct (selected) update channel?
