macOS: native AutoFill provider for passwords (not just passkeys)

[melihemreguler]

Summary

Bitwarden's macOS desktop app already ships a native AutoFill credential provider extension, but today it only provides passkeys to the system AutoFill — not passwords. This is a proposal (and an offer to help) to close that gap so users can select Bitwarden as their system password AutoFill provider on macOS.

Community demand for this is here: https://community.bitwarden.com/t/autofill-with-macos-26-tahoe/89661

Why this is not blocked by macOS

• The extension targets macOS 14.2; third-party password AutoFill providers are supported system-wide since macOS Sonoma.
• The extension already declares the generic com.apple.developer.authentication-services.autofill-credential-provider entitlement, which covers passwords as well as passkeys.
• The ObjC sync command already registers ASPasswordCredentialIdentity entries into ASCredentialIdentityStore, the renderer already syncs password credentials, and the status command reports password: YES.

What's actually missing

The "provide a password on request" path. Concretely:

1. Info.plist only declares ProvidesPasskeys (needs ProvidesPasswords).
2. CredentialProviderViewController only handles ASPasskeyCredentialRequest; ASPasswordCredentialRequest isn't handled.
3. There is no prepare_password_assertion IPC flow analogous to the existing passkey assertion flow (Rust autofill_provider → napi → Electron main → preload → renderer), so the extension has no way to ask the unlocked app for a password and complete with ASPasswordCredential(user:password:).

All of this would sit behind the existing macos-native-credential-sync feature flag, and would reuse the existing modal-mode user-confirmation UX used by passkeys (no new crypto — passwords are read from already-decrypted CipherViews).

Questions for the team

• Is this already on the internal roadmap? I noticed the active refactor in [PM-23485] Share types between autofill_provider and napi crates #18787 (PM-23485) touches exactly these files and consolidates the napi / autofill_provider types.
• Is an external contribution for the password-provisioning piece welcome, or would you prefer to keep it internal?
• If welcome: should it be built on top of [PM-23485] Share types between autofill_provider and napi crates #18787 once it lands (to avoid duplicating the type structure it removes)?

Happy to put up a draft PR behind the feature flag once there's a green light. I've signed the CLA.

[github-actions[bot]]

✨ Thank you for your code contribution proposal! While the Bitwarden team reviews your submission, we encourage you to check out our contribution guidelines.

Please ensure that your code contribution includes a detailed description of what you would like to contribute, along with any relevant screenshots and links to existing feature requests. This information helps us gather feedback from the community and Bitwarden team members before you start writing code.

To keep discussions focused, posts that do not include a proposal for a code contribution will be removed.

• 💡 For feature requests and general discussion, please visit the Bitwarden Community Forums.
• ℹ️ For questions and support, visit the Bitwarden Help Center.
• 🐛 To report a potential bug, please visit the corresponding repo. Server | Clients | iOS | Android

Thank you for contributing to Bitwarden!