Firefox 150 and Passkeys: Where Things Stand

The short version

Passkeys in Peach work in Firefox right now. We’re using the same DOM-level approach that Bitwarden and 1Password use while we wait for Mozilla to close a bug in Firefox 150’s native passkey API. The moment they do, Peach switches to the native path automatically.

What changed in Firefox 150

Firefox 150 shipped with the API infrastructure that makes native, third-party passkey support possible without workarounds. This is the milestone we’ve been building toward. Peach already has the native Firefox passkey implementation in the extension — it’s live code targeting Firefox 150’s API directly.

The bug

During testing, we found a specific issue in Firefox 150’s passkey implementation that causes certain authentication flows to fail end-to-end. We’ve filed the bug on Bugzilla and it’s under review.

We’re not going to ship a broken native path while the upstream bug is open.

What’s working right now

While the Bugzilla ticket is open, Peach uses the DOM-level monkeypatching technique that every major password manager relies on to support passkeys in Firefox today. Bitwarden uses it. 1Password uses it. The technique works: passkeys save, fill, and authenticate correctly in Firefox with Peach installed.

The difference between the two approaches is entirely internal to how the extension hooks into the browser. From your side, the experience is the same.

What happens when Mozilla ships the fix

Nothing you need to do. Peach detects that the native API is working correctly and switches to it. The code path is already in the extension. No update on your part, no configuration change — it just works cleanly instead of through a compatibility shim.

We’ll post a follow-up here when the Bugzilla ticket closes.

Track the bug: Bugzilla #2036967