Microsoft Authenticator vs Bitwarden

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Probes show no llms.txt, no markdown docs, and no OpenAPI spec available for Microsoft Authenticator's documentation site; there is no evidence of agent-oriented documentation format.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/authenticator/microsoft-authenticator-faqs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

   Bitwarden✓fullprobed9/10

   Bitwarden serves a live llms.txt at bitwarden.com/llms.txt (HTTP 200) with structured content, and help pages ship real per-page markdown mirrors (e.g., cli.md) confirming genuine agent-oriented documentation rather than a stub. This is directly confirmed by runtime probes, not just claims. Missing for 10: no independent third-party corroboration of an agent actually consuming these docs end-to-end in a workflow.

   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”
   • [probe] “PROBE runtime (recorded 2026-09-15): bitwarden.com serves a live llms.txt ('# Bitwarden — The most trusted open source password manager...')…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden ships an official CLI with API-key authentication explicitly documented as suitable for automated workflows/CI, plus a Public API for org automation and a headless 'bw serve' mode confirmed at runtime. missing for 10: no CI-specific tutorial/example pipeline (e.g., GitHub Actions) in evidence, and one community report notes CLI 'bw list' unexpectedly dumping plaintext secrets, a minor safety caveat for automation use.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed9/10

   Bitwarden ships a first-party, GPL-3.0 MCP server (bitwarden/mcp-server) published to npm, and a runtime probe confirms it completes a full stdio handshake, showing it works as documented rather than just being an announcement. Missing for 10: independent third-party review of the MCP server's tool set/security beyond the vendor probe.

   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed9/10

   Bitwarden ships a documented, fully-featured official CLI (bw) with vault management, API key auth for automated workflows, and a runtime-verified 'bw serve' mode exposing a local REST API well-suited to agentic/AI use. missing for 10: independent third-party benchmarking of agent integration quality beyond one community anecdote about plaintext output behavior.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “official CLI documented at https://bitwarden.com/help/cli/”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Microsoft Authenticator is a consumer mobile app with no evidence of a documented public API for programmatic/AI-driven control; probes for llms.txt, docs-md, and OpenAPI specs all returned 404s.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/authenticator/microsoft-authenticator-faqs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden documents a Public API for organization management (bitwarden-docs-8), a personal API key for automated/programmatic access (bitwarden-docs-9), and a full-featured CLI (bitwarden-docs-7, bitwarden-probe-4) with a documented `bw serve` REST mode enabling agent-driven vault access (bitwarden-probe-rt-1); this constitutes a documented public API surface an AI-native user could drive. missing for 10: a public OpenAPI/swagger spec resolves 404 on probed endpoints (bitwarden-probe-2), and one community report flags a CLI safety/UX issue (bitwarden-comm-13) showing rough edges in automation ergonomics.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialprobed4/10

   Bitwarden documents a personal API key for CLI/automated workflows and a Public API/CLI (including `bw serve` and an official MCP server) that an agent could use, but there's no evidence of fine-grained, least-privilege scoping (e.g., read-only, per-item, or per-collection API keys) — the personal API key and CLI access appear to grant broad vault access rather than scoped permissions, and a hands-on report shows `bw list` dumping full plaintext secrets rather than a restricted subset. missing for 10: documented scoped/restricted API key types, per-agent permission grants, or evidence that MCP/CLI access can be limited to specific vault items rather than the whole vault.

   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialprobed4/10

   Evidence shows Bitwarden exposes a Public API, CLI, personal API keys for automation, and an official MCP server (all of which an AI-native builder could integrate against), but there is no evidence of a dedicated, language-specific 'official SDK' (e.g., a bitwarden/sdk repo) and the OpenAPI/swagger spec probes all returned 404, suggesting no machine-readable API contract is published. missing for 10: explicit official SDK repositories/language bindings, published OpenAPI spec, independent developer corroboration of SDK usage.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”
   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   Bitwarden offers CLI/API/MCP server access that agents could use, but there is no evidence of a mechanism for setting up autonomous, scheduled, or background-running automations (e.g., triggers, workflows, cron-like jobs) — it only provides interfaces for on-demand vault access. missing for 10: any documented scheduling/trigger/workflow automation feature, evidence of background/autonomous execution, or vendor claims of persistent automation setup.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

2. ai-native userOperate the product with natural-language commands

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden ships an official MCP server (bitwarden/mcp-server) that completed a live stdio handshake, letting AI agents/assistants issue natural-language commands to manage the vault, backed by a full-featured CLI and llms.txt for AI-friendly docs. Missing for 10: no independent hands-on demonstration of a natural-language command actually retrieving/creating vault items via the MCP server, and community feedback flags CLI output risks (e.g., plaintext dumps) that complicate safe agentic use.

   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

Api quality

1. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Microsoft Authenticator—none0/10

   Microsoft Authenticator is a consumer mobile app for authentication, not an API product, and no OpenAPI/machine-readable spec is offered; probes for openapi.json, llms.txt, and docs-md endpoints all returned 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/authenticator/microsoft-authenticator-faqs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

   Bitwarden—none0/10

   Bitwarden documents a Public API and CLI, but a probe for common OpenAPI/Swagger spec URLs (openapi.json, swagger.json, .well-known/openapi.json) all returned 404, and no evidence pack item shows a downloadable machine-readable API spec. Missing for 10: any documented OpenAPI/Swagger file, spec download link, or API reference generator output.

   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”

   proof ↗⚑ flag

2. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   Bitwarden documents a Public API and CLI/personal API key access, but there is no evidence of API versioning scheme or a documented deprecation policy; probes for an OpenAPI spec (bitwarden-probe-2) all returned 404s, and no docs mention version headers, breaking-change policy, or sunset timelines.

   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://bitwarden.com/openapi.json, https://bitwarden.com/swagger.json, https://bitwarden.com/api/op…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden~partialcommunity6/10

   The CLI (bw list/create/edit/delete) and Public API expose scriptable, item-level access that can be chained for bulk operations, and import/export functions handle whole-vault bulk transfers of many items at once; community evidence (bw list dumping the entire vault) confirms bulk read actually works. However, there is no first-party documentation of a dedicated bulk-edit/bulk-tag/bulk-delete command or batch endpoint — bulk operations require the user to script them themselves rather than a built-in bulk API. Missing for 10: documented native bulk-update/bulk-delete commands, batch API endpoints for many items, and independent hands-on confirmation of large-scale automated edits succeeding.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Microsoft Authenticator is a consumer mobile app with no evidence of any public API for programmatic control of authentication actions; probes for API/docs endpoints all 404. No evidence supports API parity with UI functionality.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/authenticator/microsoft-authenticator-faqs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

   Bitwarden~partialprobed6/10

   Bitwarden ships a fully-featured CLI and a Vault Management API (`bw serve`) covering item/vault CRUD, TOTP retrieval, and org management via a Public API and personal API key for automated workflows, giving strong but not fully documented parity with the UI. There's no explicit vendor claim or evidence that every UI feature (e.g., passkey autofill, browser-context auto-fill, vault health reports) is exposed via API/CLI, and a hands-on report shows the CLI's `bw list` behaves differently than expected (dumping all secrets) rather than mirroring UI workflows cleanly. missing for 10: explicit API/CLI equivalents for passkey autofill and browser-based auto-fill, API access to vault health reports, and a documented feature-parity statement.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Bitwarden
   Microsoft Authenticator~partialcommunity3/10

   Microsoft documents an 'Export Passwords' feature for autofill data, but this covers only saved passwords, not the OTP/account seeds this app is centrally used for; TOTP/account data is only preserved via proprietary encrypted 'Cloud Backup' tied to a Microsoft account, not an open, portable format. Community evidence goes further, describing non-standard QR codes that other TOTP clients reject and users switching to open-source alternatives (Aegis) specifically because Authenticator lacks true open-format export/backup. missing for 10: open-format export of TOTP secrets/accounts, documented data-portability/leave workflow, independent confirmation that exported data works outside Microsoft's ecosystem.

   • [claimed-docs] “Scroll down to the Autofill section and select Export Passwords.”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [claimed-docs] “Scroll down to the Autofill section and select Export Passwords... Import your passwords.”
   • [community] “Even for Microsoft accounts, use an alternative app for 2FA/MFA. Recently I switched to the open source Aegis, which allows encrypted backup…”
   • [community] “people pick MS Authenticator - it's because microsoft basically forces it on you, uses dark patterns to avoid letting you use any other stan…”

   proof ↗⚑ flag

   Bitwarden✓fullclaimed9/10

   Bitwarden's docs explicitly support exporting full vault data (logins, notes) for backup or transfer, plus separate authenticator/TOTP export in open formats (JSON), and CLI/API access for automated bulk export. This directly satisfies the 'export all data in open formats and leave' story with strong first-party documentation. Missing for 10: no independent/hands-on confirmation of export format fidelity or completeness verification by a third party.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Microsoft Authenticator is closed-source proprietary software; no evidence of any open-license source availability, and probes for docs/API artifacts also failed.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/authenticator/microsoft-authenticator-faqs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”

   proof ↗⚑ flag

   Bitwarden~partialprobed6/10

   Community evidence and the MCP server repo confirm Bitwarden ships components under open licenses (e.g., bitwarden/mcp-server is GPL-3.0) and is broadly known/marketed as 'the most trusted open source password manager,' and users cite valuing its open client source. However, the same evidence documents a real controversy where Bitwarden relicensed its SDK away from a fully open license, only reversing course after backlash — a concrete counter-example to unconditional openness. missing for 10: explicit license file/repo evidence for the core vault clients, resolution details confirming all components are now uniformly open-licensed, independent audit confirming no remaining non-open components.

   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [community] “Props for them to step in the right direction, it wasn’t obvious at all for a few days what they would do (re: SDK relicensing controversy).”
   • [community] “Thank you to Bitwarden for relicensing back to Free/Open License... I no longer recommend Bitwarden for normal people because the built-in p…”
   • [community] “I’m relieved... I hope they realized that being FOSS is their moat... I’m still not sure how I feel about them now. Trust in the company has…”
   • [community] “I use BitWarden because I'd never trust a password manager with closed source clients... Needless to say I move to the next ethical e2ee pas…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullprobed9/10

   Bitwarden provides official, well-documented on-premise/self-hosting instructions for Linux servers, and it is open-source, aligning strongly with an AI-native user's openness needs. missing for 10: independent hands-on verification of self-hosted deployment specifically (evidence is docs-only, not community confirmation of self-hosting success).

   • [claimed-docs] “This article will walk you through the procedure to install and deploy Bitwarden to your own Linux server.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”

   proof ↗⚑ flag

Storage

1. everyday userThe app stores passkeys and signs me into websites and apps with them, not just TOTP codes

   weight 3 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The evidence pack describes password-based sign-in removal, TOTP codes, push notifications, and password autofill/export, but nowhere mentions passkeys (FIDO2/WebAuthn credentials) being stored or used to sign into websites/apps. Missing for 10: any documentation of passkey creation, storage, or sign-in via Authenticator, and any independent confirmation of passkey support.

   • [claimed-docs] “Microsoft Authenticator is a free app that helps you sign in to all your accounts without using a password - just use a fingerprint, face re…”
   • [claimed-docs] “As the only way to sign in - just tap an approval on your phone to sign in. This is called going passwordless.”
   • [claimed-docs] “As a way to sign in every time, by using a one-time password code to increase account security. This is called two-step verification or mult…”

   proof ↗⚑ flag

   Bitwarden✓fullclaimed8/10

   Bitwarden documents storing passkeys in the vault and using the browser extension or mobile apps to autofill/sign in with them across websites and apps, going beyond TOTP-only support (bitwarden-docs-4), which aligns directly with the story's requirement of passkey-based sign-in, not just TOTP codes. Missing for 10: independent/hands-on user reports specifically confirming passkey sign-in reliability (community evidence only discusses TOTP/autofill issues, not passkeys) and detail on cross-platform (desktop app) passkey support beyond browser/mobile.

   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”

   proof ↗⚑ flag

Sync

1. power userMy passkeys sync across ecosystems — iOS, Android, Windows, Linux, browsers — instead of being locked to one platform vendor

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The evidence pack covers Microsoft Authenticator's TOTP codes, push-notification MFA, cloud backup, and password autofill (now being discontinued), but contains no mention of passkey creation, storage, or cross-platform/cross-vendor passkey syncing across iOS, Android, Windows, Linux, or browsers. Passkey sync is a fair axis for an authenticator app, but nothing in the pack demonstrates it.

   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [community] “Microsoft Authenticator--a mobile app that provides 2FA--is discontinuing its password autofill feature and the passwords stored/used with t…”

   proof ↗⚑ flag

   Bitwarden~partialclaimed6/10

   Bitwarden explicitly stores passkeys in the vault and lets the browser extension and mobile apps autofill them across apps and sites, which is the platform-agnostic model (unlike Apple/Google's device-locked passkey sync) [bitwarden-docs-4]. However, the docs only call out browser extension and mobile apps, not desktop apps on Windows/Linux specifically, and there's no independent hands-on confirmation of passkey sync working seamlessly across all five named platforms. Missing for 10: explicit desktop (Windows/Linux) passkey autofill documentation, and independent/community verification of cross-platform passkey sync reliability.

   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”

   proof ↗⚑ flag

Export

1. power userExport all my TOTP secrets in an open, readable format and leave for another app whenever I choose — no lock-in

   weight 3 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Docs describe cloud backup/restore and password export/import, but none of this covers exporting TOTP secrets in an open format for use in another app; community evidence explicitly states Microsoft issues non-standard QR codes that other TOTP clients reject, indicating deliberate lock-in rather than portability.

   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [claimed-docs] “Scroll down to the Autofill section and select Export Passwords.”
   • [community] “people pick MS Authenticator - it's because microsoft basically forces it on you, uses dark patterns to avoid letting you use any other stan…”
   • [community] “Even for Microsoft accounts, use an alternative app for 2FA/MFA. Recently I switched to the open source Aegis, which allows encrypted backup…”

   proof ↗⚑ flag

   Bitwarden~partialclaimed4/10

   Bitwarden documents a general vault export (JSON/CSV) for 'logins and notes' and back-up/transfer purposes, but the evidence never explicitly confirms that TOTP secrets are included in that export or specifies an open, human-readable format for them — only import paths for other authenticators (Google Authenticator QR, LastPass JSON, 2FAS) are detailed, which is the opposite direction (lock-in mitigation on entry, not exit). Missing for 10: explicit confirmation that TOTP seeds are present in the standard export file, documentation of the exact readable TOTP export format, and any independent/hands-on verification that exported TOTP secrets can be reimported elsewhere.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”

   proof ↗⚑ flag

Import

1. power userImport tokens in bulk from other authenticator apps instead of re-enrolling every account by hand

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The evidence pack only covers backing up/restoring Authenticator's own accounts via cloud backup, exporting passwords, and standard account setup via QR/manual entry — there is no mention of any bulk-import feature for pulling tokens from other authenticator apps (e.g., Google Authenticator, Aegis) into Microsoft Authenticator. Community evidence even suggests the opposite direction problem (comm-6: MS's QR codes are non-standard so other apps reject them), reinforcing that cross-app portability isn't supported.

   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [community] “people pick MS Authenticator - it's because microsoft basically forces it on you, uses dark patterns to avoid letting you use any other stan…”

   proof ↗⚑ flag

   Bitwarden✓fullclaimed8/10

   Bitwarden's official docs explicitly support bulk import of TOTP/authenticator tokens from Google Authenticator (QR), LastPass Authenticator (JSON), and 2FAS (.2fas) backups, directly enabling power users to migrate accounts without re-enrolling each one by hand. This is a first-party, documented dedicated import flow, not a workaround. missing for 10: independent hands-on confirmation of the bulk import UX working smoothly, and coverage of additional popular authenticator export formats (e.g., Authy, Microsoft Authenticator).

   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”

   proof ↗⚑ flag

Migration

1. everyday userMoving to a new phone transfers all my tokens in one guided step

   weight 2 · round to Bitwarden
   Microsoft Authenticator!disputedcontradicted5/10

   Docs describe a guided backup/restore flow (enable Cloud Backup, then restore accounts on a new device) via microsoft-authenticator-docs-9/13, which is the core mechanism for the story. However, hands-on community evidence reports the process failing catastrophically — one user's update wiped all data and locked them out of every account (microsoft-authenticator-comm-1), while another user reports no such issue (microsoft-authenticator-comm-2), showing the reliability of the 'one guided step' transfer is contested rather than confirmed. Missing for 10: independent verification that restore reliably works across devices/OS versions, and no acknowledgment/fix from Microsoft for the reported data-loss bug.

   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [community] “This happened to me when I updated MS Authenticator after not updating it for a while. It wiped out all data, and I got locked out of all ac…”
   • [community] “I've been using Microsoft's one for my work accounts... I've never gotten that dialog, and have not had any issues with the accounts I've ad…”

   proof ↗⚑ flag

   Bitwarden~partialcommunity6/10

   Bitwarden's cloud vault syncs logins, passkeys, and TOTP codes across devices automatically (docs-1, docs-2, docs-4), so logging into a new phone with the same account would pull in tokens without manual export/import — effectively delivering the outcome. However, no evidence describes a dedicated 'guided' new-device setup wizard, and one community report (bitwarden-comm-9) describes lost generated data tied to connectivity issues, raising reliability caveats for a seamless one-step transfer. Missing for 10: documented guided device-migration flow/wizard, and independent hands-on confirmation that TOTP/passkeys transfer flawlessly to a new phone.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [community] “I tried switching to Bitwarden and forced myself to live with it for 3 months. I gave up when it lost generated password. Apparently it is q…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Microsoft Authenticator—none0/10

   No evidence Microsoft Authenticator offers any data residency/region selection controls for AI-native users; this is an authentication app, not a data-storage platform, but the story is arguably still applicable since it stores backups (cloud backup, account data) somewhere. No documentation mentions region choice or residency options.

   ⚑ flag

   Bitwarden—none0/10

   No evidence pack item mentions data residency, region selection, or self-hosting for regional compliance beyond a generic on-premise Linux install guide, which does not address choosing a storage region. Missing for 10: any documentation of region/data-residency selection (e.g., EU vs US data centers), enterprise residency options, or explicit control over where vault data is stored.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden—none0/10

   The evidence pack contains no documentation, policy statement, or setting from Bitwarden addressing whether vault data or user data is used to train AI models, nor any opt-out mechanism for such use. This is a fair privacy-posture question for a SaaS handling sensitive personal data, but nothing in the pack confirms or denies a stance, so it cannot be credited as delivered.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Microsoft Authenticator~partialcommunity3/10

   The app offers a toggle for sharing non-personal usage data and lets users enable/disable cloud backup or export/delete stored passwords, giving some control over what data is retained, but there is no documented account/data deletion policy, retention period, or explicit 'delete my data' feature, and community reports note unexpected data loss/location tracking rather than user-controlled retention. missing for 10: explicit data retention/deletion policy, dedicated 'delete my account data' control, independent verification that deletion actually removes backend data.

   • [claimed-docs] “You can also allow the sharing of additional non-personal usage data by turning on the "Usage Data" toggle button on the app's Settings page…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [community] “It also tracks your position all the time. That is the bigger problem to me. [exodus-privacy report on com.azure.authenticator]”
   • [community] “This happened to me when I updated MS Authenticator after not updating it for a while. It wiped out all data, and I got locked out of all ac…”

   proof ↗⚑ flag

   Bitwarden~partialcommunity3/10

   Bitwarden docs show users can export their vault data (for backup or account transfer) and community evidence indicates an account-deletion path exists (export → delete account → recreate), but there is no dedicated, first-party documentation on data retention policies, granular deletion controls, or how these apply to AI/agent access (e.g., MCP server or CLI-served vault data). Missing for 10: explicit retention policy documentation, dedicated account/vault deletion docs, and clarity on data lifecycle when accessed via CLI/MCP for AI agents.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”
   • [community] “BitWarden has lost the trust. There was a blocker bug on iOS, they went radio silent on follow-ups, and their fix suggestion was 'export dat…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to Microsoft Authenticator
   Microsoft Authenticator!disputedcontradicted4/10

   Microsoft's own docs mention an opt-in 'Usage Data' toggle that lets users control sharing of additional non-personal usage data, suggesting some telemetry control (microsoft-authenticator-docs-16). However, independent community reporting citing an Exodus Privacy audit says the app 'tracks your position all the time,' contradicting the notion that users can fully opt out of tracking (microsoft-authenticator-comm-5), and there is no documentation of a comprehensive telemetry/diagnostics opt-out beyond that single toggle. Missing for 10: explicit documentation of a full telemetry/diagnostics opt-out, first-party clarification of the location-tracking discrepancy, and independent verification that the toggle actually stops all usage tracking.

   • [claimed-docs] “You can also allow the sharing of additional non-personal usage data by turning on the "Usage Data" toggle button on the app's Settings page…”
   • [community] “It also tracks your position all the time. That is the bigger problem to me. [exodus-privacy report on com.azure.authenticator]”

   proof ↗⚑ flag

   Bitwarden—none0/10

   The evidence pack contains no documentation, settings, or community reports describing a telemetry/usage-tracking opt-out control in Bitwarden clients, CLI, or self-hosted server. While the axis is fair to ask of any privacy-focused product, nothing here confirms such a toggle exists or how it works.

   ⚑ flag

App lock

1. everyday userThe app itself locks behind biometrics or a PIN, so a borrowed phone doesn't expose my codes

   weight 2 · round to Microsoft Authenticator
   Microsoft Authenticator✓fullclaimed8/10

   Docs explicitly describe App Lock requiring device PIN or biometric authentication every time Authenticator is opened, directly matching the story. Missing for 10: independent/hands-on confirmation of App Lock reliability and default-on status.

   • [claimed-docs] “When App Lock is enabled, you'll be asked to authenticate using your device PIN or biometric every time you open Authenticator.”
   • [claimed-docs] “Microsoft Authenticator is a free app that helps you sign in to all your accounts without using a password - just use a fingerprint, face re…”

   proof ↗⚑ flag

   Bitwarden~partialcommunity3/10

   No official documentation in the evidence pack describes a PIN/biometric app-lock feature; the only signal is an indirect community comment implying fingerprint unlock already exists on some platforms but is missing on Linux, which weakly corroborates the capability without detailing scope or coverage. Missing for 10: first-party docs on biometric/PIN unlock, mobile-specific confirmation, and independent hands-on validation of the lock behavior.

   • [community] “Yeah it's nice and all but I wish they brought fingerprint auth to Linux already.”

   proof ↗⚑ flag

Audits

1. security engineerThe vendor publishes independent security audits of the app and its sync protocol

   weight 2 · round drawn
   Microsoft Authenticator—none0/10

   No evidence of any published independent security audit of Microsoft Authenticator or its sync protocol; documentation only covers feature descriptions, and community threads discuss bugs, privacy concerns, and forced adoption but never an audit report. Missing for 10: any third-party audit report, pen-test disclosure, or vendor reference to an independent security assessment of the app or backup/sync protocol.

   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [community] “Even for Microsoft accounts, use an alternative app for 2FA/MFA. Recently I switched to the open source Aegis, which allows encrypted backup…”
   • [community] “It also tracks your position all the time. That is the bigger problem to me. [exodus-privacy report on com.azure.authenticator]”

   proof ↗⚑ flag

   Bitwarden—none0/10

   No evidence pack items reference independent third-party security audits, penetration tests, or cryptographic/protocol reviews of Bitwarden's app or sync protocol; the pack only covers docs on features (TOTP, autofill, CLI, import/export) and community sentiment/complaints unrelated to audits. Missing for 10: published audit reports (e.g., Cure53), audit scope/dates, sync protocol review findings, remediation disclosures.

   ⚑ flag

Monitoring

1. power userThe app warns me when a service I use is breached or a stored credential is weak, reused, or exposed

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   No evidence that Microsoft Authenticator monitors for breached services or evaluates stored credentials for weakness/reuse/exposure; its password autofill feature is even being discontinued rather than expanded with security scanning. Missing for 10: breach monitoring, weak/reused password detection, exposed credential alerts.

   • [community] “Microsoft Authenticator--a mobile app that provides 2FA--is discontinuing its password autofill feature and the passwords stored/used with t…”

   proof ↗⚑ flag

   Bitwarden~partialclaimed5/10

   Bitwarden's Vault Health Reports (docs-11/17) explicitly check for reused and weak passwords locally on the client, covering part of the story, but no evidence in the pack documents breach monitoring (e.g., known data-breach alerts) or an 'exposed passwords' check against breach databases. Missing for 10: evidence of breach/exposure alerts for compromised services, and any exposed-credential detection feature.

   • [claimed-docs] “Vault health reports can help you evaluate the security of your Bitwarden individual or organization vault... Reports... are run locally on …”
   • [claimed-docs] “Vault health reports can help you evaluate the security of your Bitwarden individual or organization vault. Reports, such as the Reused Pass…”

   proof ↗⚑ flag

Push

1. it adminPush-based sign-in includes phishing defenses — number matching, location context, and admin-enforced MFA policies

   weight 2 · round to Microsoft Authenticator
   Microsoft Authenticator~partialcommunity5/10

   Evidence confirms admin-enforced push MFA policies (docs-3, comm-8, comm-9) and location-based context checks (docs-15), but there is no explicit mention of number matching as a phishing-resistant feature anywhere in the pack, and community threads focus on other issues (backup bugs, forced adoption) rather than validating anti-phishing controls. Missing for 10: number matching feature documentation, independent verification of phishing-resistance efficacy, and conditional access/policy configuration details for admins.

   • [claimed-docs] “You can set up notifications for your work or school account (if allowed by your administrator) or for your personal Microsoft account.”
   • [claimed-docs] “You'll need to share your location once every hour to ensure you're still within a country where you are allowed to access the resource.”
   • [community] “IME some MS shops enforce use of it for 2fa to access company resources like vpn and etc. - for eg, the only reason this app exists on my ph…”
   • [community] “My company used to allow TOTP so many TOTP apps could be used instead of Microsoft Authenticator but my company disabled that a while ago. N…”

   proof ↗⚑ flag

   Bitwarden—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Server

1. it adminSelf-host the sync server on my own infrastructure and keep every secret inside my perimeter

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bitwarden✓fullclaimed8/10

   Bitwarden provides official documentation for installing and deploying the self-hosted server on a Linux server, keeping vault data on the admin's own infrastructure — the core of this story. Missing for 10: independent hands-on verification of a real-world self-hosted deployment and details on ongoing maintenance/upgrade complexity for self-hosted instances.

   • [claimed-docs] “This article will walk you through the procedure to install and deploy Bitwarden to your own Linux server.”

   proof ↗⚑ flag

Source

1. security engineerThe client apps are open source, so the code handling my seeds can be inspected and community-reviewed

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   No evidence that Microsoft Authenticator's client code is open source; it is a closed, proprietary Microsoft product with no public repository or community code review mentioned anywhere in the evidence pack.

   ⚑ flag

   Bitwarden~partialprobed6/10

   Bitwarden markets itself as 'the most trusted open source password manager' and community members explicitly cite open-source clients as the reason they trust it with secrets (bitwarden-probe-1, bitwarden-comm-15). However, the evidence also documents a real controversy where SDK code (used by clients) was briefly relicensed away from a fully open license before being reverted after community pressure, which shows scrutiny worked but also that openness has not always been airtight (bitwarden-comm-1, bitwarden-comm-3, bitwarden-comm-4). Missing for 10: direct links to client-app GitHub repos, explicit confirmation that seed/TOTP-handling code specifically is open and audited, and independent third-party code audits corroborating the open-source claim.

   • [probe] “PROBE llms.txt: HTTP 200 at https://bitwarden.com/llms.txt # Bitwarden > The most trusted open source password manager for passwords, passk…”
   • [community] “I use BitWarden because I'd never trust a password manager with closed source clients... Needless to say I move to the next ethical e2ee pas…”
   • [community] “Props for them to step in the right direction, it wasn’t obvious at all for a few days what they would do (re: SDK relicensing controversy).”
   • [community] “Thank you to Bitwarden for relicensing back to Free/Open License... I no longer recommend Bitwarden for normal people because the built-in p…”
   • [community] “I’m relieved... I hope they realized that being FOSS is their moat... I’m still not sure how I feel about them now. Trust in the company has…”

   proof ↗⚑ flag

Automation

1. ai-native userAn agent can fetch a current TOTP code programmatically — via CLI or API — to complete a 2FA login inside an automated workflow

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Microsoft Authenticator is a mobile app with no documented CLI or API for programmatic TOTP retrieval; evidence even indicates its QR codes are non-standard and reject other TOTP clients, and probes confirm no API/OpenAPI surface exists. No evidence of any automation-friendly access to codes.

   • [community] “people pick MS Authenticator - it's because microsoft basically forces it on you, uses dark patterns to avoid letting you use any other stan…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”

   proof ↗⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden's integrated authenticator generates TOTP codes (bitwarden-docs-1) and the CLI is documented as a full vault-management tool suitable for automated workflows via personal API key (bitwarden-docs-7, bitwarden-docs-9); runtime probes confirm 'bw serve' exposes a local REST Vault Management API and an official MCP server completes a full handshake, both surfaces an agent could use to fetch TOTP codes programmatically (bitwarden-probe-rt-1, bitwarden-probe-rt-2). Hands-on community evidence independently corroborates that 'bw list' actually returns current TOTP codes in plaintext, confirming the CLI does return live TOTP data (bitwarden-comm-13). Missing for 10: explicit documentation naming a dedicated 'get totp' command/API endpoint and a clean (non-complaint) hands-on workflow example.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [community] “I had a really bad experience with the bitwarden cli. I ran 'bw list', assuming it would list names, but it listed everything including pass…”

   proof ↗⚑ flag

2. ai-native userExpose the vault through a local programmatic endpoint an agent can query for codes and secrets without screen-scraping the app

   weight 1 · round to Bitwarden
   Microsoft Authenticator—none0/10

   No evidence of any local API, CLI, or programmatic endpoint for querying codes/secrets; probes confirm no llms.txt, docs-md, or OpenAPI endpoints exist, and the app is designed as a closed mobile experience with screen-capture disabled by default.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/authenticator/microsoft-authenticator-faqs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”
   • [claimed-docs] “To see your OTP codes in screenshots or allow other apps to capture the Authenticator screen, turn on Screen Capture in Authenticator's Sett…”

   proof ↗⚑ flag

   Bitwarden✓fullprobed8/10

   Bitwarden's CLI supports a documented `bw serve` mode exposing the vault as a local RESTful API, and Bitwarden ships an official MCP server (bitwarden/mcp-server) that completed a live stdio handshake, both giving agents programmatic access to vault items and TOTP codes without screen-scraping. missing for 10: no independent hands-on validation of `bw serve` specifically for TOTP retrieval by an agent, and no broader third-party corroboration beyond the vendor-run probes.

   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”
   • [probe] “official MCP server documented at https://github.com/bitwarden/mcp-server”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”

   proof ↗⚑ flag

Browser

1. everyday userA browser extension autofills my TOTP codes and passkeys during login instead of making me retype them

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Evidence shows Microsoft Authenticator is a mobile app generating OTP codes and offering an in-app password Autofill feature, but there is no mention of a browser extension that autofills TOTP codes or passkeys, and community evidence indicates the password autofill feature itself is being discontinued entirely (comm-11), not extended to TOTP/passkey autofill.

   • [claimed-docs] “Scroll down to the Autofill section and select Export Passwords.”
   • [claimed-docs] “Scroll down to the Autofill section and select Export Passwords... Import your passwords.”
   • [community] “Microsoft Authenticator--a mobile app that provides 2FA--is discontinuing its password autofill feature and the passwords stored/used with t…”

   proof ↗⚑ flag

   Bitwarden✓fullcommunity8/10

   Docs confirm browser extension autofills matching credentials on login pages (docs-12), autofills stored passkeys across apps/websites (docs-4), and generates/syncs TOTP codes (docs-1, docs-2) which are surfaced during autofill in the extension. One community mention notes TOTP setup friction, but no concrete evidence contradicts the core autofill-of-TOTP/passkeys capability. Missing for 10: independent hands-on confirmation specifically that TOTP codes (not just passwords/passkeys) are auto-filled into login forms without manual copy-paste.

   • [claimed-docs] “When you visit a website, the browser extension recognizes it and enters matching credentials from your vault into the login fields.”
   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [community] “I always enjoyed the value that Bitwarden provides: free to use, password generator, and a vault to keep other texts. But somehow I never go…”

   proof ↗⚑ flag

Desktop

1. power userA first-class desktop app gives me codes and vault access on my computer, not just on mobile

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   All evidence describes Microsoft Authenticator as a mobile app (phone/wearable), with no mention of a desktop application for codes or vault access; the product is explicitly mobile-only.

   ⚑ flag

   Bitwarden~partialprobed5/10

   Evidence confirms TOTP codes sync across 'Bitwarden apps' and vault access is available via browser extension and CLI on a computer, implying desktop-class access, but no citation explicitly documents a native desktop application (GUI) separate from the browser extension/CLI. Missing for 10: explicit desktop app documentation, screenshots/feature parity claims, and independent confirmation that a first-class desktop GUI (not just extension/CLI) exists and works well.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “When you visit a website, the browser extension recognizes it and enters matching credentials from your vault into the login fields.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”

   proof ↗⚑ flag

Watch

1. everyday userRead my codes from my smartwatch without pulling out my phone

   weight 1 · round to Microsoft Authenticator
   Microsoft Authenticator~partialclaimed4/10

   Docs confirm Authenticator notifications can be mirrored to a wearable device, which implies some code/approval visibility without pulling out the phone, but there's no explicit confirmation that time-based OTP codes themselves are readable on a smartwatch screen, nor any hands-on/community corroboration of this specific wearable experience. missing for 10: explicit documentation that OTP codes (not just approval notifications) display on smartwatch, independent/hands-on confirmation of the wearable experience.

   • [claimed-docs] “you can mirror Authenticator notifications from your phone to your wearable device.”

   proof ↗⚑ flag

   Bitwarden—none0/10

   The evidence pack covers TOTP generation, syncing, browser extension, CLI, and API features, but contains no mention of a smartwatch app, Wear OS/watchOS companion, or any glanceable code display for wearables. This is a fair capability question for a password manager with a built-in authenticator, but no evidence shows it is delivered.

   ⚑ flag

Backup

1. security engineerBackups are end-to-end encrypted with a key the vendor never holds, and the encryption design is documented

   weight 3 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Docs confirm a Cloud Backup feature exists (microsoft-authenticator-docs-9, -13) but provide no description of end-to-end encryption or a vendor-inaccessible key, and no encryption design documentation is cited anywhere. Community commentary even contrasts Microsoft's backup with an alternative app that explicitly offers 'encrypted backups' (microsoft-authenticator-comm-4), implying this property isn't established for Microsoft Authenticator.

   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [community] “Even for Microsoft accounts, use an alternative app for 2FA/MFA. Recently I switched to the open source Aegis, which allows encrypted backup…”

   proof ↗⚑ flag

   Bitwarden~partialclaimed4/10

   Docs confirm Bitwarden supports vault export/import and mention an 'encrypted exports' option (bitwarden-docs-5, bitwarden-docs-6, bitwarden-docs-16), implying some backups can be encrypted, but no evidence pack item documents the underlying encryption design, key derivation, or explicitly states the vendor cannot access backup contents. missing for 10: a linked security whitepaper or architecture doc describing zero-knowledge key management for exports, explicit vendor-can't-decrypt-backups statement, and independent verification of the encrypted export format.

   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault”

   proof ↗⚑ flag

Multi device

1. everyday userMy tokens are available on my phone, tablet, and computer at the same time, kept in sync automatically

   weight 2 · round to Bitwarden
   Microsoft Authenticator!disputedcontradicted4/10

   Docs describe Cloud Backup that lets you restore accounts to a new device (docs-9, docs-13), but this is backup/restore rather than true simultaneous multi-device sync across phone, tablet, and computer — there's no evidence of a tablet or desktop client. Community reports directly contradict reliability of this backup: users report Authenticator updates wiping all account data and causing lockouts (comm-1, comm-3), undermining the claim that data stays reliably available across devices. Missing for 10: evidence of simultaneous real-time sync across phone/tablet/desktop clients, and resolution of documented data-loss/backup failure reports.

   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [community] “This happened to me when I updated MS Authenticator after not updating it for a while. It wiped out all data, and I got locked out of all ac…”
   • [community] “using microsoft authenticator I just ran into this recently... it's a known issue that microsoft has no announced plan of fixing... I knew t…”

   proof ↗⚑ flag

   Bitwarden!disputedcontradicted6/10

   Bitwarden's docs describe cloud-based vault sync (TOTP codes staying synchronized across apps, passkeys usable across browser extension and mobile apps, auto-fill working consistently) which underlies cross-device availability of stored items (bitwarden-docs-2, bitwarden-docs-4, bitwarden-docs-12). However, a hands-on community report describes losing a generated password due to sync failures on bad connections, calling it 'quite common' (bitwarden-comm-9), directly contradicting the claim of seamless automatic sync. missing for 10: independent verification of reliable real-time sync across phone/tablet/computer simultaneously, and resolution/acknowledgment of the reported data-loss-on-sync issue.

   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Save passkeys in your Bitwarden vault and use the browser extension or mobile apps to autofill them across the apps and websites you use eve…”
   • [claimed-docs] “When you visit a website, the browser extension recognizes it and enters matching credentials from your vault into the login fields.”
   • [community] “I tried switching to Bitwarden and forced myself to live with it for 3 months. I gave up when it lost generated password. Apparently it is q…”

   proof ↗⚑ flag

Recovery

1. everyday userLosing my phone doesn't lose my accounts — a documented recovery path restores my tokens on a new device

   weight 3 · round to Bitwarden
   Microsoft Authenticator!disputedcontradicted5/10

   Microsoft documents a Cloud Backup feature explicitly designed to restore accounts on a new device after phone loss (docs-9, docs-13), which matches the story's claim of a documented recovery path. However, a concrete hands-on community report describes the opposite outcome — an app update wiped all backed-up data and locked the user out of every account, with the poster citing it as a known reliability issue (comm-1, comm-3) — directly contradicting the documented recovery guarantee. missing for 10: independent verification that Cloud Backup restore reliably works, resolution of the reported wipe/lockout bug, and clarity on how backup interacts with app updates.

   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”
   • [community] “This happened to me when I updated MS Authenticator after not updating it for a while. It wiped out all data, and I got locked out of all ac…”
   • [community] “using microsoft authenticator I just ran into this recently... it's a known issue that microsoft has no announced plan of fixing... I knew t…”

   proof ↗⚑ flag

   Bitwarden~partialcommunity6/10

   Bitwarden's docs show that TOTP codes are synced across the Bitwarden apps (docs-2) and that vault data (including logins) can be exported/imported to restore to a new install (docs-5, docs-6), which together give a de facto path to recover accounts/tokens on a new device after losing a phone. However there is no explicit 'lost my phone' recovery guide, and community reports mention TOTP/sync reliability problems (bitwarden-comm-12, bitwarden-comm-9) that add real-world caveats. Missing for 10: a dedicated 'device loss/account recovery' doc, evidence of automatic cloud vault sync restoring a fresh install without manual export/import, and confirmation that community-reported sync/TOTP glitches don't block this flow.

   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Export your vault data, including logins and notes, to back up important information or transfer to a new Bitwarden vault.”
   • [claimed-docs] “Import logins and data from different password managers, other Bitwarden vaults, or encrypted exports to instantly transfer your information…”
   • [community] “I always enjoyed the value that Bitwarden provides: free to use, password generator, and a vault to keep other texts. But somehow I never go…”
   • [community] “I tried switching to Bitwarden and forced myself to live with it for 3 months. I gave up when it lost generated password. Apparently it is q…”

   proof ↗⚑ flag

Automation

1. ai-native userAn agent can create and update vault entries — seeding new TOTP secrets, storing credentials — through documented programmatic surfaces

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   No evidence of any API, CLI, or programmatic surface for creating/updating vault entries or TOTP secrets; Microsoft Authenticator is a manual mobile app with QR-based account addition, and probes for API/docs endpoints returned 404s. missing for 10: any documented API/SDK/CLI for programmatic vault management, evidence of agent-accessible interfaces, confirmation of automated secret seeding.

   • [probe] “PROBE llms.txt: HTTP 404 at https://support.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://support.microsoft.com/en-us/authenticator/microsoft-authenticator-faqs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://support.microsoft.com/openapi.json, https://support.microsoft.com/swagger.json, https://supp…”
   • [claimed-docs] “Scan the QR code or download and install Authenticator from the Apple app store.”

   proof ↗⚑ flag

   Bitwarden✓fullprobed7/10

   Bitwarden documents multiple programmatic surfaces for vault management — the fully-featured CLI (which supports create/edit item operations and a `bw serve` mode exposing a local REST API for TOTP/items), a personal API key explicitly recommended for 'automated workflows' and 'external applications,' and an official first-party MCP server that completed a live stdio handshake, giving agents a documented path to create and update vault entries including TOTP secrets. Missing for 10: an explicit doc/code example showing the exact CLI/API call syntax for adding a TOTP field to a new item, and independent (non-vendor) confirmation that an agent successfully created/updated entries end-to-end via these surfaces.

   • [claimed-docs] “The Bitwarden command-line interface (CLI) is a powerful, fully-featured tool for accessing and managing your vault.”
   • [claimed-docs] “Using the personal API key for CLI authentication is suitable for automated workflows, for providing access to an external appli”
   • [probe] “official CLI documented at https://bitwarden.com/help/cli/”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official bw CLI installs keylessly from npm (@bitwarden/cli, registry latest 2026.8.0) and prints i…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Bitwarden's OFFICIAL MCP server completed a FULL keyless stdio initialize handshake — `npx -y @bitwarde…”

   proof ↗⚑ flag

Policy

1. it adminEnforce org-wide policies — require app lock, restrict export, mandate strong master credentials — across every member's app

   weight 1 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Evidence only hints that notifications may be gated 'if allowed by your administrator' and that location-sharing is required for conditional access, but there is no documentation of an admin console or policy set that lets IT enforce app lock, restrict export, or mandate strong master credentials across all org members. Community evidence even suggests admins lack granular control tools (comm-6), reinforcing the absence of such enterprise policy enforcement in this pack.

   • [claimed-docs] “You can set up notifications for your work or school account (if allowed by your administrator) or for your personal Microsoft account.”
   • [claimed-docs] “When App Lock is enabled, you'll be asked to authenticate using your device PIN or biometric every time you open Authenticator.”
   • [claimed-docs] “You'll need to share your location once every hour to ensure you're still within a country where you are allowed to access the resource.”
   • [community] “people pick MS Authenticator - it's because microsoft basically forces it on you, uses dark patterns to avoid letting you use any other stan…”

   proof ↗⚑ flag

   Bitwarden~partialclaimed3/10

   The evidence only shows that Bitwarden's Public API lets organizations manage 'members, collections, groups, event logs, and policies,' implying policy management exists, but there is no documentation shown for specific policies like app-lock enforcement, export restriction, or master-password strength requirements. Missing for 10: explicit documentation of individual policy types (master password strength, disable personal vault export, require app lock/timeout), admin console UI screenshots or workflow, and any hands-on confirmation that these policies are enforced across all members' apps.

   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”

   proof ↗⚑ flag

Sharing

1. it adminMy team can share TOTP-protected logins through shared vaults or collections with per-member access control

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   Microsoft Authenticator is a personal/individual authenticator app with no evidence of shared vaults, collections, or per-member access control for teams; its passwords feature is even being discontinued. Missing for 10: shared vault/collection feature, per-member access control, admin sharing management console.

   • [community] “Microsoft Authenticator--a mobile app that provides 2FA--is discontinuing its password autofill feature and the passwords stored/used with t…”
   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [claimed-docs] “Turn on the Cloud Backup toggle. Select a Microsoft personal account where the backup will be stored.”

   proof ↗⚑ flag

   Bitwarden~partialcommunity6/10

   Bitwarden's docs confirm built-in TOTP generation/sync (bitwarden-docs-1, bitwarden-docs-2) and its Public API supports managing organization members, collections, and groups (bitwarden-docs-8), and a real-world team user cites 'safer account sharing, including 2FA' as a killer feature (bitwarden-comm-8). However, the evidence pack lacks explicit documentation tying TOTP fields to collection-level per-member permissions/access control, so the granular sharing mechanics aren't directly evidenced. Missing for 10: dedicated docs on collection permission levels (view/edit/manage) applied to TOTP-containing items, and independent confirmation of this exact workflow.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “The Bitwarden Public API provides organizations a suite of tools for managing members, collections, groups, event logs, and policies.”
   • [community] “We use BitWarden at work, paying $3600/year. Their product is great for teams... The killer feature for me has been safer account sharing, i…”

   proof ↗⚑ flag

Enrollment

1. everyday userScan a QR code and immediately start generating TOTP codes for a new account

   weight 3 · round to Bitwarden
   Microsoft Authenticator!disputedcontradicted5/10

   Microsoft's own docs confirm the app supports one-time-password codes for two-step verification (docs-12), implying QR-based account setup generates TOTP codes offline. However, hands-on community reports describe a known QR-scan bug that forces users to cancel the dialog and add accounts manually without the QR code (comm-3), and another user notes the QR codes Microsoft issues for its own accounts are non-standard and rejected by other TOTP clients (comm-6), directly contradicting a smooth 'scan and immediately generate' experience. missing for 10: no first-party doc walking through the exact 'add account via QR scan' flow, and no resolution/acknowledgment of the reported scan failures.

   • [claimed-docs] “As a way to sign in every time, by using a one-time password code to increase account security. This is called two-step verification or mult…”
   • [community] “using microsoft authenticator I just ran into this recently... it's a known issue that microsoft has no announced plan of fixing... I knew t…”
   • [community] “people pick MS Authenticator - it's because microsoft basically forces it on you, uses dark patterns to avoid letting you use any other stan…”

   proof ↗⚑ flag

   Bitwarden~partialcommunity6/10

   Docs confirm Bitwarden's integrated authenticator automatically generates rotating TOTP codes once a key/QR is added to a login item (bitwarden-docs-1, bitwarden-docs-13), which covers the core capability, but the pack lacks explicit documentation of the actual camera-scan-QR flow for a brand-new account (only QR-based *import* from another authenticator app is documented, bitwarden-docs-3/14). One community report also describes difficulty getting TOTP working at all (bitwarden-comm-12), though it's anecdotal and not a concrete reproducible failure. missing for 10: explicit doc/screenshot of scanning a QR to add a brand-new TOTP secret (not import), and independent hands-on confirmation that codes generate immediately after scan.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Let's start your Bitwarden browser extension journey by adding a new login item to your vault”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”
   • [community] “I always enjoyed the value that Bitwarden provides: free to use, password generator, and a vault to keep other texts. But somehow I never go…”

   proof ↗⚑ flag

Offline

1. power userCodes generate fully offline — no network, no vendor account required just to see my TOTP codes

   weight 2 · round to Microsoft Authenticator
   Microsoft Authenticator!disputedcontradicted4/10

   Microsoft's own docs claim codes work without an internet connection or phone service (microsoft-authenticator-docs-2), but hands-on community reports contradict this for real-world enterprise use: one user reports 'ms authenticator doesn't generate a code until I first log into the vpn using exchange creds' (microsoft-authenticator-comm-10), and another notes the app issues non-standard QR codes that lock users into the vendor's app rather than plain TOTP (microsoft-authenticator-comm-6), undermining the 'no vendor account required' and pure-offline claims for many real deployments. Missing for 10: independent technical verification of offline TOTP generation across account types, and confirmation that no Microsoft account/login is ever required to view codes.

   • [claimed-docs] “The codes don't require you to be on the internet or connected to data, so you don't need phone service to sign in.”
   • [community] “it seems to be a push notification where the ms authenticator doesn't generate a code until I first log into the vpn using exchange creds.”
   • [community] “people pick MS Authenticator - it's because microsoft basically forces it on you, uses dark patterns to avoid letting you use any other stan…”
   • [community] “My company used to allow TOTP so many TOTP apps could be used instead of Microsoft Authenticator but my company disabled that a while ago. N…”

   proof ↗⚑ flag

   Bitwarden—none0/10

   Bitwarden's TOTP generation is tightly coupled to the vault: codes are stored and computed inside a Bitwarden vault item, which requires a Bitwarden account/vault (docs-1, docs-2) and typically syncs across the vendor's cloud infrastructure. No evidence describes a standalone, account-free offline TOTP mode; self-hosting (docs-10) still requires an account/server setup, not a vendor-free path. missing for 10: evidence of a no-account, no-vendor-server offline TOTP mode; confirmation that code generation works without ever creating/authenticating a Bitwarden account.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “This article will walk you through the procedure to install and deploy Bitwarden to your own Linux server.”

   proof ↗⚑ flag

Organization

1. power userKeep dozens of tokens organized — search, folders or groups, and service icons — so the right code is always two taps away

   weight 2 · round to Bitwarden
   Microsoft Authenticator—none0/10

   No evidence describes organizational features like search, folders/groups, or per-account service icons for managing many tokens; docs cover backup, passwordless sign-in, and notifications but not organization/search UX. Community evidence even suggests account list issues (duplicate/overwrite concerns) rather than robust organization tools. Missing for full credit: any mention of search, folder/grouping, or icon-based organization of accounts.

   • [claimed-docs] “This article describes how to back up information on all the accounts you have in Authenticator so that if you lose your mobile or get a new…”
   • [community] “I have many accounts with the same user names, and they don't get overwritten. There might be some design flaw somewhere, but it's surely no…”

   proof ↗⚑ flag

   Bitwarden~partialclaimed4/10

   Docs confirm Bitwarden generates and syncs TOTP codes across devices and lets users import/export authenticator data (bitwarden-docs-1, bitwarden-docs-2, bitwarden-docs-3), which supports storing many tokens, but nothing in the evidence pack speaks to search, folders/groups, or service icons specifically for TOTP entries — organization is only implied through the general vault (login) item structure. missing for 10: explicit documentation of folder/collection organization for TOTP items, search functionality across TOTP entries, and service icon display for stored codes.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”
   • [claimed-docs] “Connect Authenticator with Password Manager to sync your verification codes. Once activated, the Bitwarden apps stay synchronized with any c…”
   • [claimed-docs] “Google Authenticator (QR code): Import from Google Authenticator using a QR code... LastPass (JSON): Import a LastPass Authenticator account…”

   proof ↗⚑ flag

Variants

1. power userNon-standard tokens work too — Steam Guard, HOTP counters, custom periods and digit lengths

   weight 2 · round drawn
   Microsoft Authenticator—none0/10

   No evidence anywhere in the pack indicates Microsoft Authenticator supports HOTP counters, Steam Guard, or custom period/digit-length TOTP tokens; docs only describe standard push/OTP sign-in flows. Community evidence even suggests the opposite — its QR codes are non-standard TOTP and rejected by other clients, implying inflexibility rather than support for non-standard token types.

   • [claimed-docs] “As a way to sign in every time, by using a one-time password code to increase account security. This is called two-step verification or mult…”
   • [community] “people pick MS Authenticator - it's because microsoft basically forces it on you, uses dark patterns to avoid letting you use any other stan…”

   proof ↗⚑ flag

   Bitwarden—none0/10

   The evidence only describes Bitwarden's standard TOTP support (six-digit SHA-1 codes rotating every 30 seconds) with no mention of Steam Guard tokens, HOTP counters, or custom periods/digit lengths anywhere in the docs, community, or probe items.

   • [claimed-docs] “it automatically produces the time-based one-time passwords (TOTPs), six-digit codes using SHA-1 that rotate every 30 seconds”

   proof ↗⚑ flag