Recently I have been getting this popup in Chrome, whenever opening a (almost any?) page with login fields, that says:
this page is interfering with the Bitwarden experience. The bitwarden inline menu has been temporarily disabled as a safety measure.
I suspect a conflict with MacOS Passwords app, which also auto-fills, but this never happened before after using BW for some months, including also using MacOS Passwords.
Ideas?
@gajahduduk Welcome to the forum!
This is a new feature (merged on Nov. 19, 2025), a comment in the code provides the following explanation.
// Set inline menu to be off; page is aggressively trying to take top position of top layer
The PR that created this change is here:
The parts of the above PR that implement the pop-up warning you’ve seen were based on the following (closed) PR:
Running a second password manager at the same time as Bitwarden is highly probable to create conflicts, and is therefore not recommended.
Please temporarily disable your macOS Passwords app, and check if that solves the problem. If it does, then migrate all passwords stored in the macOS Passwords app to Bitwarden, and stop using the macOS Passwords app altogether.
uggg. thx for your reply.
disabling the MacOS autofill behavior did not fix this problem in chrome.
the previous behavior was sometimes a bit glitchy but basically was ok. any way to revert to that?
otherwise i wonder why this is not a widespread problem. “AutoFill Passwords and Passkeys” option is on by default in MacOS since “Passwords” was introduced. Using Passwords is essentially required – it’s the front end to the MacOS keychain now.
If disabling the macOS Passwords app did not fix the situation, and if it is accurate that you get the warning on “almost any” page, then there may be a problem with your setup, or a bug in the new feature.
I would suggest that you work with customer support to try to troubleshoot the issue, and/or submit a bug report (“New Issue”) on Github.
You said that the issue occurs on “almost any” webpage. If you have found any login forms where the problem does not occur, that might be helpful information for troubleshooting.
Only if you switch to Firefox (which allows you to load old versions of extensions, and to turn off automatic updates). You could also try to side-load an old version of the extension (downloaded from Github) in Chrome, but this is more complicated.
@gajahduduk What MacOS and Chrome versions are you using?
Somehow I suspect, using older BW client versions will be more restricted in the near future, so probably only a temporary solution.
it’s all (almost) current:
MacOS 26.1
Chrome: Version 143.0.7499.170 (Official Build) (arm64)
Perhaps there is a conflict with one of your other extensions. Maybe try disabling your other extensions, leaving only Bitwarden enabled. And if that fixes it, enable them one-at-a-time till you manage to break it again.
ah yes, and it was rather obvious: Apple’s iCloud Passwords chrome extension.
This was probably a “prompted” install when MacOS Passwords app was first introduced, with Chrome as default browser.
Pretty sure the issue is fixed now, but still it would be better for these to be able to co-exist somehow. Passwords handles things BitWarden might not and VV.
anyway – thanks everyone for the help.
Like what?
Blockquote
would need to get back to you on that, but certain things having to do with iCloud logins and passkeys.
Bitwarden has about 8 different ways to autofill credentials. Inline autofill is but one of them. If you wish to inline autofill with iCloud Passwords, you can disable Bitwarden’s inline autofill to avoid conflict.
Running into this too so thanks for the tip to fix, I will try that. @DenBesten, I hear you. But some of us are running iCloud Passwords and BitWarden intentionally. As Gajah said there are some credentials handled better within apple’s ecosystem. We used to be able to use both. Why not offer this as an option that needs to be enabled? It would be great if that could be taken as constructive feedback from the userbase.
Bitwarden staff do monitor the forum, and I’m confident that they will appreciate the user feedback. But, to be clear, none of the volunteer moderators here (e.g., @DenBesten, @Nail1684, or myself) have any special access to Bitwarden management or developers, so please take our responses as what they are: attempts to assist fellow Bitwarden users, often by proposing work-arounds for issues that have been reported.
Another recourse available for forum participants is to post a feature request to propose new features or improvements to existing features.
Based on what I’ve seen reported by various users in the past, running two password managers at once often results in problems. Bitwarden officially recommends disabling other password managers, to “prevent interference with Bitwarden.”
It would be helpful if specific examples could be offered. That would allow us to suggest tailored solutions for you, or it could form the basis for a feature request to develop functionality that is not already available in Bitwarden.
Perhaps I was not clear. One can run both. Of the 8 different ways to autofill Bitwarden credentials, only one of them (inline-autofill) is causing conflict. So, the workaround I propose is to disable that one method and instead use the other seven to access Bitwarden credentials. With the conflict removed, I would then anticipate iCloud passwords to be able to use its version of inline-autofill.
The inline autofill menus are probably the most intrusive of the autofill methods (and most likely to cause conflicts), but to be clear, all autofill techniques in Bitwarden rely on DOM injection, and can therefore be subject to mutual interference by code manipulation performed by other password managers.
There are other strategies for preventing conflict, such as disabling all Bitwarden autofill on those webpages where a user prefers to use a different password manager. This is one of the reasons that I have repeatedly asked for examples… 
From a user perspective, when both were operational, I just chose which one seemed to work best and quickest in any situation to login to a site. So to answer this, in theory, I’d have to re-enable both and be deliberate about answering why sometimes one is better or quicker than the other. But we cannot do that now for reasons of this thread. Now that I’ve disabled iCloud Passwords Chrome extension, if I come across any sites that I think would have worked better with iCloud Passwords (and I’m thinking largely Apple sites are likely), I’ll report back in this thread.
@gajahduduk @motamedn You can try to report this as a bug (Bitwarden extension not compatible with use of iCloud passwords extension) on Github, or contact support to describe the issue. At a minimum, you will get an assessment from Bitwarden as to whether such use is officially supported.