šŸ”œ Auto-type/Autofill for logging into other desktop apps (Windows, MacOS, Linux)

I’ve been experimenting with it ever since it became accessible via TestFlight on MacOS.

Is the Safari inline autofill glitchy with this? Absolutely.
Does it work? Surprisingly, to some extent (passkeys can be used, for example).

Nevertheless, the TestFlight build has numerous problems on iOS as well. It’ll be interesting to see whether it works better on MacOS as they address the ongoing iOS issues. That is, assuming they don’t withdraw the build from MacOS, as it’s evidently not an intentional MacOS rollout.

Nonetheless, it clearly shows the potential for native MacOS autofill.

+1 Is there any progress? I have been waiting for too long.

1+ This would make my workflow easier

+1, really looking forward to it too!

@gtran Great to see this news:

I know you mentioned the plan is to stay on Electron and the mobile app situation is motivated by Xaramin sunset, but could it be reconsidered that the new native iOS / iPadOO app could become a macOS native app? Apple provides frameworks via SwiftUI or Catalyst for this.

It would be a big differentiator against 1Password (who uses Electron and has lost users for that reason), and with Apple entering the game too in iOS 18 and macOS 15 with a standalone passwords app for iCloud Keychain, folks who want native experiences may pick Apple over Bitwarden..

Thanks for considering.

2 Likes

+1 waiting, just bought premium

This would have the additonal benefit of finally enabling Fido2WebAuthn for login on Macs. Still can’t believe such an essential feature is missing and apparently not actively being worked on

1 Like

Any update on this please?

This would be a killer feature for me. Most of my autofilling is done from macOS and this would really improve how this works.

iCloud keychain password storage lacks a number of features I need - but the general experience of logging into websites and apps is so much easier / friction-free than Bitwarden’s own implementation.

+1

This has to be the single most important MacOS feature. Can we have an update on the pipeline?

Switching to MacOS = switching AWAY from Bitwarden without this feature. Safari integration only does half the job. Bitwarden becomes a burden rather than an assistant without OS support.

Mac has it own very slick, fully integrated, cloud-backed password management system to compete with. It is only cross platform support that lets Bitwarden even begin to retain Mac user market share, without OS integration that battle is as good as lost.

1 Like

As a long time Bitwarden user & recent macOS convert, I would really like to see this handled better (speaking to macOS on this). However, if BW has an opportunity to bridge this gap, it would really be appreciated. +1

+1
I am regrettably looking at other options. I would definitely come back if/when this feature was made available.

Can’t use Bitwarden until this is a feature unfortunately. +1 Any updates on this?

This is the last piece of the puzzle for me to replace 1password

Agreed. Please implement this. With macOS Sequoia coming soon with a dedicated passwords app, Bitwarden is likely going to lose more desktop users. I want to switch my passkeys to Bitwarden from iCloud Keychain, but will not until there is a native app for MacOS. Now that the iOS app is written in Swift, it should be relatively simple to port it to Mac. I don’t see why there should be any major holdup.

@gtran @bw-admin Please implement this. This is the last missing piece for me to use Bitwarden full time inside my mac-only organization.

Adding to this, in iOS 18, it has AutoFill support for 3rd party password manager. So add in one shot also, because not all apps (especially banks) support native password autofill.

Hi team,

It’s clear that this feature is not a priority despite years of ongoing user demand. Can you share what’s considered more important and if there’s any plan to address this in the near future? Transparency would help set expectations.

Thanks.

+1
I have just realized with great shock that this functionality is not available. :astonished:

Looking forward to seeing this feature enabled, is there any ETA for it at the minute - surely its not a difficult implementation.