Passkey unlock is the only reason I use 1Password. You will not let me pay for it, and Linux is hard unsupported. Is this project dead?

Forum|Forum|18 days ago
September 12, 2026
3 replies
12 views

I signed up for 1Password for one reason: passkey-only unlock. No master password to remember, nothing to leak, a YubiKey or my phone is the only way in. That model works flawlessly on Mac, iOS, and in the Chrome extension. It is the best thing you have shipped. I would not be here without it.

And I cannot pay you for it. Passkey beta accounts are free and there is no path to a paid plan. I would pay well above the list price for this feature. You built the thing that made me choose you, then made it impossible to give you money for it.

Instead of a bill, I get lockouts. The beta trial has an expiry, and when it lapses my account freezes. That is not a warning email, that is every vault gone until support resets the trial by hand. It happened June 26, 2025 (ticket YZN-42482-864). Your own rep replied that day: "The team is aware of the freeze. My account also froze." No ETA on Linux, and the instruction was to email again next time it happens. It happened again July 3, 2026. A password manager that locks you out on a timer because nobody set a production date is not a beta problem, it is a billing problem you refuse to solve by taking my money.

On Linux it is a wall. 1Password 8.12.36 shows "Unable to sign in. Try again, or contact support for help." The log says why:

```
WARN [1P:op-webauthn-authentication/src/models/error.rs:168] webauthn sign in -- Tried to sign in with webauthn on an unsupported platform, linux
```

That is a deliberate platform check, not a bug. Support now states "1Password accounts that unlock with a passkey aren't compatible with Linux at this time." The beta is closed to new accounts. The last staff word (November 2025) was "more work is still needed." A December 2023 thread asking about Linux has zero replies. That is close to three years of silence on a feature you sold people on.

What this costs me: no desktop app on Linux, no SSH agent, no `op` CLI, no chezmoi integration. The browser extension works, which proves the platform is capable. Everything else about my Linux setup is done. This is the one piece of friction left in my daily life, and it is yours.

I understand the company is focused on AI features right now. Please finish the projects you started before opening new ones. Passkey unlock was announced in 2023, went to beta in 2024, and in 2026 it is still beta, still closed, and still missing a platform.

Straight questions, please answer them straight:

1. Is passkey unlock still an active project with a release target, or is it dead and I should find another solution? "More work is needed" is not an answer after two years.

2. What is the actual blocker on Linux? My guess: the Mac and Windows apps call the OS WebAuthn API and Linux has none. If so, libfido2 over USB covers the YubiKey case today. Chrome built its own stack on Linux and your extension works through it. Phone hybrid transport can come later.

3. Let beta accounts upgrade to a paid plan, and kill the trial expiry. No paying customer would tolerate a scheduled lockout. I want to be a customer whose complaint counts.

4. If Linux doesn’t matter, say so plainly and stop beating your chest about how much you love and support Linux. This is what that support looks like for a passkey account: an app that refuses to sign in, a CLI that cannot run, and a support page that says "not compatible at this time" with no date. Market share is shifting and people expect feature complete products. The experience on macOS and Windows is excellent. Withholding it from Linux when the building blocks are documented is a choice, not a limitation.

Side complaint while I have your attention. On every launch the Linux app creates native messaging manifests for browsers I do not have installed: ~/.config/google-chrome, chromium, BraveSoftware (three channels), vivaldi, microsoft-edge, opera, and ~/.mozilla. Delete them and they come back. Please only write a manifest where the browser actually exists, or give us a setting.

I am at the point of leaving, but I do not want to. You built a great product. Go the final mile and let people use it. Make it a premium feature and let me throw money at your devs. If you were open source I would do it myself. If you're hiring, let me know. I will come on board, get it done, and quit. 😅

Pinned Reply By 1P_Dave

Hello @pixelhabits! 👋

Thank you for your interest in the passkey unlock beta. We’ve been testing passkey unlock for 1Password through a public beta with special individual test accounts (offering a free promotion while testing) over the past few years. The project is currently on hold while we review the feedback we’ve received from participants in the beta, and it’s no longer possible to create new test accounts that unlock with a passkey.

I’ve shared your feedback with our development and product teams so that they’re aware that you’d love to see the feature be incorporated in 1Password accounts in the future.

Side complaint while I have your attention. On every launch the Linux app creates native messaging manifests for browsers I do not have installed: ~/.config/google-chrome, chromium, BraveSoftware (three channels), vivaldi, microsoft-edge, opera, and ~/.mozilla. Delete them and they come back. Please only write a manifest where the browser actually exists, or give us a setting.

Those folders contain native messaging files that let the 1Password desktop app communicate with browser extensions. 1Password installs them for all supported browsers so extensions in browsers installed later will work properly and immediately without any additional configuration needed.

Files for browsers you don’t use can remain and they won’t cause any issues. That being said, I’ve shared your feedback that you’d like to avoid having these be automatically installed with our team internally.

-Dave

1P_DavePinned

1Password Employee

Hello @pixelhabits! 👋

Thank you for your interest in the passkey unlock beta. We’ve been testing passkey unlock for 1Password through a public beta with special individual test accounts (offering a free promotion while testing) over the past few years. The project is currently on hold while we review the feedback we’ve received from participants in the beta, and it’s no longer possible to create new test accounts that unlock with a passkey.

I’ve shared your feedback with our development and product teams so that they’re aware that you’d love to see the feature be incorporated in 1Password accounts in the future.

Side complaint while I have your attention. On every launch the Linux app creates native messaging manifests for browsers I do not have installed: ~/.config/google-chrome, chromium, BraveSoftware (three channels), vivaldi, microsoft-edge, opera, and ~/.mozilla. Delete them and they come back. Please only write a manifest where the browser actually exists, or give us a setting.

Those folders contain native messaging files that let the 1Password desktop app communicate with browser extensions. 1Password installs them for all supported browsers so extensions in browsers installed later will work properly and immediately without any additional configuration needed.

Files for browsers you don’t use can remain and they won’t cause any issues. That being said, I’ve shared your feedback that you’d like to avoid having these be automatically installed with our team internally.

-Dave

P

pixelhabitsAuthor

@1P_Dave I appreciate the response and I wanted to add that I researched the problem more myself and webauthn support in linux has greatly expanded in the last few months and from what claude can tell me this is now just on the development team at 1password to incorporate the project here:
https://github.com/linux-credentials/libwebauthn

1P_Dave

1Password Employee

Thanks for sharing that, and for your feedback! I’ve passed your comments along to our team internally.

-Dave

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO