Background
As of version 2026.2.0, search results no longer include the special “Autofill Suggestions” section (which benefits some users, while inconveniencing others). The new behavior has been confirmed by Bitwarden staff to be intended behavior.
Problem Statement
The new UX implementation has a — likely unintended — consequence that should be addressed: When a search result has a URI match to the active web page, there is no longer a one-click path to autofilling. Autofilling on a matching web page now requires three clicks, and along the way, displays a warning message that that is incorrect (after clicking “More Options” and “Autofill”, the user is confronted by the inaccurate statement “This site doesn’t match your saved login details”, and must then make a third click: Autofill without adding, which is not even the default selection). Because autofilling is such a foundational functionality for a password manager browser extension, it is imperative for the UI to allow this essential task to be accomplished with a bare minimum of mouse clicks — three is two too many!
Another problem introduced by this issue is that the method for autofilling login credentials on a URI-matched web page is now different depending on whether or not the browser extension is displaying search results. This is a regression to the inconsistent UX that was present when there were separate “Tab” and “Vault” views in the browser extension. The autofilling workflow should be the same whether the user has performed a search or not.
Proposed Solution
This feature request proposes a one-click autofill feature for login items that have a URI match for the active web page (just like prior to version 2026.2.0). For items that do not have a URI match for the active web page, it should be possible to do a forced autofill (with or without adding the URI) with only two clicks (just like it was possible to do prior to 2025).
The easiest and most streamlined way to implement this would be to add the “Autofill Suggestions” one-click autofill method to all items listed in the browser extension Vault view (whether browsing, filtering, or searching). Specifically, for users who have not enabled the option “Click items in autofill suggestions to fill”, every vault item should have a Fill. Conversely, for users who have enabled the option “Click items in autofill suggestions to fill” (an option which should be renamed just “Click items in to fill”), every vault item should trigger autofill when the item is clicked.
It the vault item is a login item that has a URI match to the active web page, then autofill should occur immediately on the first click, with no additional user intervention required.
On the other hand, if the clicked login item does not have a URI match to the active web page, then the “Confirm Autofill” modal dialog should be displayed (giving the user the options to either “Autofill and add”, “Autofill without adding”, or “Do not autofill”).
Safety
The proposed feature is just as safe as the original behavior, prior the the browser extension UI refresh (a little over a year ago). In the pre-redesign UI, a user could search the vault for any item that did not have a URI match to the active web page, then click the item to view its details, and there click an Autofill button, which would then execute a forced autofill with no further user confirmation required. This design (two-click forced autofill for non-matching login items) served the community well and evidently did not cause any security comprosises for over five years.
The new “Autofill Confirmation” dialog for forced autofilling is a sufficient safeguard for exposing a Fill button on _every vault item. As an additional UI affordance, one could render the Fill button (or the vault item card) with a different appearance for matching and non-matching items.
(as one-click autofill for logins that match active web page is still fully functional – as long as you don’t perform a search in the extension… 
)
not being displayed is unintentional, and related to the fact that the mismatch warning is being incorrectly displayed.
menu when autofill is deemed suspicious.
)