Browse Source

Correct windows-native-credential-sync requirements

The plugin only registers when the desktop app runs from an appx package,
and the stable appx of 2026.9.1 does not declare the COM server Windows
needs to activate it (added for stable in bitwarden/clients#23620, not
released yet). So the flag has no effect on current stable builds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RJZPtN8D6FXs3E2x85EodL
pull/7841/head
Michael 1 month ago
parent
commit
1d42355489
  1. 3
      .env.template

3
.env.template

@ -403,7 +403,8 @@
## - "enable-basic-auth-response": Enable HTTP Basic Auth autofill in the browser extension (Browser >= 2026.9.0)
## - "undetermined-cipher-scenario-logic": Enable the rewritten add/update login notification triggering logic in the browser extension (Browser >= 2026.2.0)
## - "biometrics-sdk-ipc": Enable biometric unlock over the SDK IPC framework (Desktop >= 2026.9.0, Browser >= 2026.9.0)
## - "windows-native-credential-sync": Register the desktop app as a passkey provider in Windows, so passkeys in the vault can be used by other apps and browsers (Desktop >= 2026.8.0)
## - "windows-native-credential-sync": Register the desktop app as a passkey provider in Windows, so passkeys in the vault can be used by other apps and browsers.
## Requires the Microsoft Store (appx) build of the desktop app. Stable releases up to and including 2026.9.1 lack the required plugin registration, so it has no effect there yet.
# EXPERIMENTAL_CLIENT_FEATURE_FLAGS=
## Require new device emails. When a user logs in an email is required to be sent.

Loading…
Cancel
Save