Similar to iOS, macOS provides system settings to allow third-party apps to register as password AutoFill sources. This is particularly relevant for the “Set up codes in…” and “AutoFill passwords and passkeys” sections in System Settings.
While Bitwarden handles this role perfectly on iOS, it doesn’t currently appear to be an option on macOS (as of macOS 26.2 and BW client 2026.1.0 (55383). As services increasingly steer users toward passkeys, being able to register Bitwarden as the system provider would greatly help avoid “split” vaults where passkeys inadvertently end up in Apple’s “Passwords” app instead of Bitwarden.
I don’t mean to trivialize the effort or testing required to implement this, but I did some digging into the Apple AuthenticationServices requirements. It seems to hinge on a few key items for the macOS Desktop client:
-
Extension Subclass: Implementing ASCredentialProviderViewController to handle system-level credential requests.
-
Entitlement: Adding the com.apple.developer.authentication-services.autofill-credential-provider entitlement to the app bundle.
-
Info.plist Flag: Explicitly declaring TOTP support by adding the
ProvidesOneTimeCodeskey (set totrue) within theASCredentialProviderExtensionCapabilitiesdictionary. Without this flag, macOS doesn’t recognize the app as a “code generator” candidate for the dropdown menu. -
Onboarding: Leveraging ASSettingsHelper to help users jump directly to the correct toggle in System Settings.
I believe this integration would make the macOS experience feel just as native and seamless as it is on mobile.