Google Authenticator vs 1Password

Agent access

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

   weight 2 · round to 1Password
   Google 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

   1Password✓fullprobed9/10

   1Password.dev and support.1password.com both serve confirmed llms.txt/llms-full.txt files plus markdown mirrors of every docs page, and this is directly verified via live probes, not just claims. missing for 10: independent third-party (non-vendor) confirmation that agents actually consume these files successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://support.1password.com/llms.txt # 1Password Support > LLM-friendly exports of English public support gui…”
   • [probe] “PROBE runtime (recorded 2026-09-15): 1password.dev serves llms.txt ('# 1Password Developer Documentation') plus llms-full.txt, and every doc…”
   • [claimed-docs] “The 1Password Environments MCP Server lets MCP clients such as Claude Code, Codex, Cursor, and Kiro securely manage your 1Password Environme…”
   • [probe] “PROBE runtime (recorded 2026-09-15): 1Password's public docs MCP server at https://www.1password.dev/mcp completed a FULL keyless initialize…”

   proof ↗⚑ flag

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

   weight 2 · round to 1Password
   Google 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

   1Password✓fullprobed8/10

   1Password ships a dedicated CLI (confirmed packaged via Homebrew cask), Service Accounts explicitly for automating secrets in CI/infrastructure without extra services, Connect Servers exposing a REST API for machine workflows, and a Credential Broker for CI/CD short-lived access — all first-party documented and headless by design. Missing for 10: independent hands-on case studies/community reports specifically validating CI pipeline usage rather than just vendor docs.

   • [claimed-docs] “1Password CLI brings 1Password to your terminal. Learn how to install the CLI, then integrate it with your 1Password app and sign in with To…”
   • [claimed-docs] “Use the 1Password Credential Broker to give CI/CD and other machine workflows short-lived access to secrets, without managing service accoun…”
   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [claimed-docs] “1Password Service Accounts help automate secrets management in your applications and infrastructure without the need to deploy additional se…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official op CLI is packaged in Homebrew as the 1password-cli cask ('Command-line interface for 1Pas…”
   • [probe] “official CLI documented at https://www.1password.dev/cli/get-started”

   proof ↗⚑ flag

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

   weight 3 · round to 1Password
   Google 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

   1Password✓fullprobed8/10

   1Password ships an official Environments MCP Server that lets MCP clients (Claude Code, Codex, Cursor, Kiro) securely manage 1Password Environments without exposing secrets to the agent, and a runtime probe confirms a live keyless MCP initialize handshake against 1Password's own MCP endpoint. This is first-party documentation plus real runtime corroboration of the server actually working. Missing for 10: broader independent/community hands-on reports beyond the vendor probe, and clarity since the Environments MCP server is explicitly marked Beta.

   • [claimed-docs] “The 1Password Environments MCP Server lets MCP clients such as Claude Code, Codex, Cursor, and Kiro securely manage your 1Password Environme…”
   • [probe] “official MCP server documented at https://www.1password.dev/environments/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-15): 1Password's public docs MCP server at https://www.1password.dev/mcp completed a FULL keyless initialize…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to 1Password
   Google 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

   1Password✓fullprobed9/10

   1Password ships an official `op` CLI with detailed docs, reference commands, Homebrew packaging, and integration with secrets automation, service accounts, and SSH/Git workflows, making it well-suited to AI-native/agentic scripting. missing for 10: independent hands-on review or benchmark of the CLI's use in agentic workflows beyond vendor docs and packaging.

   • [claimed-docs] “1Password CLI brings 1Password to your terminal. Learn how to install the CLI, then integrate it with your 1Password app and sign in with To…”
   • [claimed-docs] “op item list --vault Private”
   • [probe] “official CLI documented at https://www.1password.dev/cli/get-started”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official op CLI is packaged in Homebrew as the 1password-cli cask ('Command-line interface for 1Pas…”
   • [claimed-docs] “Use the 1Password SSH Agent to authenticate all your Git and SSH workflows.”

   proof ↗⚑ flag

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

   weight 3 · round to 1Password
   Google 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

   1Password✓fullprobed9/10

   1Password exposes a well-documented public API surface for programmatic control: a scriptable CLI (op), official SDKs in Go/JS/Python, a Connect Server REST API, Service Accounts, Events API, and even a public MCP server for AI agents — all backed by first-party docs and confirmed via runtime probes (CLI packaged in Homebrew, MCP handshake succeeding, llms.txt/markdown mirrors of docs). This directly satisfies an AI-native user's need to drive the product via documented APIs rather than only a GUI. Missing for 10: independent third-party developer testimonials/case studies of building against these APIs beyond vendor docs and probes.

   • [claimed-docs] “1Password CLI brings 1Password to your terminal. Learn how to install the CLI, then integrate it with your 1Password app and sign in with To…”
   • [claimed-docs] “op item list --vault Private”
   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [claimed-docs] “1Password Service Accounts help automate secrets management in your applications and infrastructure without the need to deploy additional se…”
   • [claimed-docs] “1Password SDKs allow you to build integrations that programmatically interact with 1Password using Go, JavaScript, or Python.”
   • [github] “Build integrations that programmatically interact with 1Password.”
   • [claimed-docs] “The 1Password Environments MCP Server lets MCP clients such as Claude Code, Codex, Cursor, and Kiro securely manage your 1Password Environme…”
   • [probe] “official MCP server documented at https://www.1password.dev/environments/mcp-server”
   • [probe] “official CLI documented at https://www.1password.dev/cli/get-started”
   • [probe] “PROBE runtime (recorded 2026-09-15): 1Password's public docs MCP server at https://www.1password.dev/mcp completed a FULL keyless initialize…”
   • [probe] “PROBE runtime (recorded 2026-09-15): 1password.dev serves llms.txt ('# 1Password Developer Documentation') plus llms-full.txt, and every doc…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official op CLI is packaged in Homebrew as the 1password-cli cask ('Command-line interface for 1Pas…”

   proof ↗⚑ flag

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

   weight 2 · round to 1Password
   Google 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

   1Password~partialprobed6/10

   1Password Service Accounts and Connect Servers support scoped, vault-limited, short-lived credentials for machine/agent workflows, and the Environments MCP Server explicitly avoids returning secrets to the agent, which aligns with least-privilege agent access. However, evidence doesn't show fine-grained per-agent scoping controls, credential rotation/expiry specifics, or audit tooling tailored to AI agents specifically (vs generic machine/service workflows). missing for 10: documentation of granular per-agent permission scoping, credential lifecycle/expiry controls for agents, and independent/hands-on verification of least-privilege enforcement in agent contexts.

   • [claimed-docs] “Use the 1Password Credential Broker to give CI/CD and other machine workflows short-lived access to secrets, without managing service accoun…”
   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [claimed-docs] “1Password Service Accounts help automate secrets management in your applications and infrastructure without the need to deploy additional se…”
   • [claimed-docs] “The 1Password Environments MCP Server lets MCP clients such as Claude Code, Codex, Cursor, and Kiro securely manage your 1Password Environme…”
   • [probe] “PROBE runtime (recorded 2026-09-15): 1Password's public docs MCP server at https://www.1password.dev/mcp completed a FULL keyless initialize…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to 1Password
   Google 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

   1Password✓fullprobed8/10

   1Password ships official SDKs for Go, JavaScript, and Python for programmatically interacting with vaults, secrets, and items, backed by GitHub repos, docs, and complementary CLI/Connect/Service Accounts tooling for automation workflows. missing for 10: independent third-party developer testimonials/case studies validating real-world SDK usage beyond vendor docs and GitHub repo descriptions.

   • [claimed-docs] “Secure your applications: Load secrets into your code with secret references or read environment variables from 1Password Environments.”
   • [claimed-docs] “Automate item management: Programmatically manage items in your 1Password account.”
   • [claimed-docs] “1Password SDKs allow you to build integrations that programmatically interact with 1Password using Go, JavaScript, or Python.”
   • [github] “Build integrations that programmatically interact with 1Password.”
   • [claimed-docs] “1Password Service Accounts help automate secrets management in your applications and infrastructure without the need to deploy additional se…”
   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official op CLI is packaged in Homebrew as the 1password-cli cask ('Command-line interface for 1Pas…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to 1Password
   Google 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

   1Password~partialprobed5/10

   1Password provides machine-facing automation building blocks — Service Accounts, Connect Servers, Credential Broker, CLI, and SDKs — that let CI/CD pipelines and other unattended workflows fetch secrets autonomously in the background, and the Environments MCP Server lets AI agents manage secrets without human intervention. However, there's no evidence of a general-purpose scheduler, trigger system, or orchestration layer for building broader 'automations' beyond secrets retrieval/injection. Missing for 10: native scheduling/triggers, workflow orchestration UI, and evidence of autonomous multi-step automations beyond secret access.

   • [claimed-docs] “Use the 1Password Credential Broker to give CI/CD and other machine workflows short-lived access to secrets, without managing service accoun…”
   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [claimed-docs] “1Password Service Accounts help automate secrets management in your applications and infrastructure without the need to deploy additional se…”
   • [claimed-docs] “Secure your applications: Load secrets into your code with secret references or read environment variables from 1Password Environments.”
   • [claimed-docs] “1Password SDKs allow you to build integrations that programmatically interact with 1Password using Go, JavaScript, or Python.”
   • [probe] “PROBE runtime (recorded 2026-09-15): 1Password's public docs MCP server at https://www.1password.dev/mcp completed a FULL keyless initialize…”
   • [claimed-docs] “The 1Password Environments MCP Server lets MCP clients such as Claude Code, Codex, Cursor, and Kiro securely manage your 1Password Environme…”

   proof ↗⚑ flag

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

   weight 2 · round to 1Password
   Google 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

   1Password~partialprobed6/10

   1Password ships an official Environments MCP Server that lets AI agents (Claude Code, Codex, Cursor, Kiro) manage 1Password Environments via natural-language prompts through MCP clients, and a public docs MCP server for AI-readable documentation — genuine natural-language operability. However this is explicitly Beta and scoped only to Environments/secrets management, not the broader vault/login/passkey functionality that makes up most of 1Password's product surface, and the primary automation surface (CLI, SDKs) is structured commands, not natural language. Missing for 10: NL control over core password/vault/item management, general-availability status of the MCP server, independent hands-on verification of the NL workflow.

   • [claimed-docs] “The 1Password Environments MCP Server lets MCP clients such as Claude Code, Codex, Cursor, and Kiro securely manage your 1Password Environme…”
   • [probe] “PROBE runtime (recorded 2026-09-15): 1Password's public docs MCP server at https://www.1password.dev/mcp completed a FULL keyless initialize…”
   • [probe] “official MCP server documented at https://www.1password.dev/environments/mcp-server”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Google 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

   1Password—none0/10

   The evidence pack shows 1Password has developer APIs, SDKs, CLI, and Connect servers, but nowhere does it document API versioning schemes or a formal deprecation policy for these interfaces. Missing for 10: explicit API version numbers/headers, a published deprecation/sunset policy, changelog or migration guides for breaking changes.

   ⚑ flag

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

   weight 2 · round to 1Password
   Google 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

   1Password~partialprobed6/10

   The 1Password CLI (`op item list`, etc.) and SDKs explicitly support programmatic, scriptable management of items ('Automate item management: Programmatically manage items in your 1Password account'), which enables bulk operations via scripting loops or SDK calls. However, there is no dedicated bulk-edit/batch-update command or documentation showing native multi-item bulk operations (e.g., bulk delete, bulk tag) — missing for 10: explicit bulk-operation commands/API endpoints, documented examples of bulk updates across many items, and independent verification of bulk-scale performance.

   • [claimed-docs] “op item list --vault Private”
   • [claimed-docs] “Automate item management: Programmatically manage items in your 1Password account.”
   • [claimed-docs] “1Password SDKs allow you to build integrations that programmatically interact with 1Password using Go, JavaScript, or Python.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official op CLI is packaged in Homebrew as the 1password-cli cask ('Command-line interface for 1Pas…”

   proof ↗⚑ flag

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

   weight 2 · round to 1Password
   Google 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

   1Password~partialclaimed5/10

   1Password's CLI, SDKs (Go/JS/Python), Connect Server, and Service Accounts let AI/automation programmatically read, create, and manage vault items and secrets ([1password-docs-2],[1password-docs-4],[1password-docs-5],[1password-docs-8],[1password-docs-26]), which covers the core secrets-management workflows. However, many UI-only capabilities — passkey creation/autofill in the browser extension, Watchtower breach/weak-password monitoring, Apple Watch lookups, import/export flows, SSH agent autofill — have no documented API/CLI equivalent, so full UI/API parity is not evidenced. Missing for 10: API-exposed passkey management, Watchtower/security-alerts API, and full item-type/browser-feature parity via CLI or SDK.

   • [claimed-docs] “op item list --vault Private”
   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [claimed-docs] “1Password Service Accounts help automate secrets management in your applications and infrastructure without the need to deploy additional se…”
   • [claimed-docs] “Automate item management: Programmatically manage items in your 1Password account.”
   • [claimed-docs] “1Password SDKs allow you to build integrations that programmatically interact with 1Password using Go, JavaScript, or Python.”
   • [claimed-docs] “Watchtower tells you about breaches, weak passwords, duplicate items, and other security problems with the items you have saved in 1Password…”
   • [claimed-docs] “you can now create, manage, and sign in with passkeys on a growing number of websites and apps directly from the 1Password browser extension”
   • [claimed-docs] “1Password lets you easily sign in to sites, use suggested passwords, and find what you need – all without leaving your browser.”

   proof ↗⚑ flag

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

   weight 3 · round to 1Password
   Google Authenticator!disputedcontradicted3/10

   Docs show a QR-code based transfer/export feature for moving codes between devices (docs-3, docs-11, comm-9, comm-18), but this is a proprietary re-import-only format tied to Google Authenticator itself, not an open, portable format usable elsewhere. Community evidence explicitly contradicts any 'open format export' claim: users report Google 'makes it stupendously difficult to just get a simple text export to a file' and that 'Google Authenticator does not allow you to include your codes in your backup, even when it's encrypted,' with data tied to a Google Account that can vanish if banned. Missing for 10: any documented open/standard export format (e.g., plain TOTP URI list, CSV, encrypted portable file), and evidence of true account-independent data portability.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “To manually transfer Authenticator codes to a new device, you need: Your old device with Google Authenticator codes”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “Google Authenticator does not allow you to include your codes in your backup, even when it's encrypted. So due to Google Authenticator, losi…”
   • [community] “Google Authenticator already has a QR-Code based very easy export procedure, I just backup my GAuth to my spare phone and tablet. It feels s…”
   • [community] “Google Authenticator has a feature to allow export of all saved codes into one QR code for re-import into Google Authenticator running on an…”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   1Password~partialclaimed5/10

   1Password documents a built-in export feature explicitly for moving data to another app, and separately documents CSV import compatibility, implying an open-format export path (e.g. CSV) exists — but the evidence never states which formats export actually produces (1Password's native export is typically 1PUX, not just CSV) nor confirms full data coverage (attachments, SSH keys, secure notes) is included. missing for 10: explicit confirmation that exported format is open/interoperable (not proprietary 1PUX), evidence of full-fidelity data portability, and independent/hands-on confirmation of successful migration.

   • [claimed-docs] “You can export your information from the 1Password apps if you want to move it to a different app.”
   • [claimed-docs] “You can import data into 1Password from many different browsers and applications, including applications that export data in the comma-separ…”
   • [claimed-docs] “Learn how to transfer your passwords and other information from other applications into 1Password.”

   proof ↗⚑ flag

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

   weight 2 · round to Google Authenticator
   Google Authenticator~partialclaimed4/10

   The official GitHub repo (google/google-authenticator) publicly hosts source for HOTP/TOTP implementations across platforms and a PAM module, suggesting some source is open, but the evidence never states an explicit open-source license nor confirms the current mobile app's source is included/maintained there. missing for 10: explicit license text (e.g., Apache 2.0) confirmation, evidence the current Android/iOS app source (not just legacy PAM/CLI code) is published, and any independent corroboration of license terms.

   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”
   • [github] “Pluggable Authentication Module, aka PAM.”

   proof ↗⚑ flag

   1Password—none0/10

   1Password is closed-source proprietary software; the evidence pack shows CLI, SDKs, MCP servers and docs, but nothing indicating source code is published under an open license. Missing for 10: any evidence of an open-source license, public source repository, or statement of source availability.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Google Authenticator—none0/10

   Google Authenticator's core mobile app is closed-source and tied to Google account infrastructure for sync (docs-1, docs-4); the only open-source artifacts on GitHub are OTP-generator libraries and a PAM module, not the actual app users run, and there's no documented way to self-host the core product. Community threads reinforce this, complaining about lack of control over codes and dependency on Google's cloud (comm-6, comm-7, comm-12).

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “Pluggable Authentication Module, aka PAM.”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   1Password—none0/10

   1Password is a cloud-hosted SaaS vault; the only 'self-hosted' pieces are Connect Servers/Environments proxies that still require a cloud 1Password account behind them, not the core vault itself. Community comments explicitly confirm the loss of local/offline vault storage and no self-host option ('no native apps, no local vault storage... VC rot has already set in'), and there is no docs evidence of a self-hostable core product.

   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [community] “Use a tiny portion of that to continue support for local, non-cloud-based vault files please.”
   • [community] “Except they have already started to diminish what used to make 1P great. We now get no native apps, no local vault storage, no upfront payme…”

   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 1Password
   Google Authenticator—none0/10

   All evidence describes Google Authenticator solely as a TOTP/HOTP code generator with cloud sync of codes; there is no mention of passkey storage or passkey-based sign-in anywhere in the docs, GitHub description, or community discussion.

   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”

   proof ↗⚑ flag

   1Password✓fullclaimed8/10

   1Password's own support docs confirm passkey creation, storage, and sign-in on websites/apps directly through 1Password (browser extension and apps), plus Watchtower flagging logins that can upgrade to passkeys, going well beyond just TOTP storage which is also documented separately. Missing for 10: independent hands-on verification of passkey sign-in reliability across many sites and no explicit mobile-app (non-browser) passkey autofill confirmation.

   • [claimed-docs] “you can now create, manage, and sign in with passkeys on a growing number of websites and apps directly from the 1Password browser extension”
   • [claimed-docs] “opening Watchtower in 1Password, which now flags all of your existing logins that could be updated with a passkey”
   • [claimed-docs] “You can use 1Password to save the passkeys you create for your accounts and sign in to websites with passkeys in your browser.”
   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”

   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 1Password
   Google 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

   1Password~partialcommunity6/10

   1Password's docs show passkeys can be created, saved, and used from the browser extension across 'a growing number of websites and apps' and Watchtower flags logins for passkey upgrade, implying sync across whatever platform the extension/app runs on rather than vendor lock-in. However the evidence pack never explicitly confirms native passkey support/sync parity on Linux or Android apps (only browser extension and Apple-ecosystem mentions like Apple Watch/Touch ID), and an older community comment specifically raises concerns about a missing Linux client, leaving cross-platform parity unconfirmed by direct docs. Missing for 10: explicit Linux and Android app passkey documentation, independent hands-on confirmation of parity across all five listed platforms.

   • [claimed-docs] “you can now create, manage, and sign in with passkeys on a growing number of websites and apps directly from the 1Password browser extension”
   • [claimed-docs] “opening Watchtower in 1Password, which now flags all of your existing logins that could be updated with a passkey”
   • [claimed-docs] “You can use 1Password to save the passkeys you create for your accounts and sign in to websites with passkeys in your browser.”
   • [community] “Mandatory 'No Linux client' comment :| Does anyone have any insight if this is a pure business decision or there's something holding them ba…”

   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 1Password
   Google Authenticator!disputedcontradicted3/10

   Docs and community posts confirm a QR-code 'export' exists, but it is a proprietary migration QR built for transferring to another Google Authenticator instance, not an open/readable text format, and users explicitly report Google 'makes it stupendously difficult to just get a simple text export to a file' and that codes cannot be included in backups. This directly contradicts the story's requirement of an open, readable, portable export for switching apps freely. Missing for 10: an official plain-text/otpauth-URI export, documented compatibility with third-party apps, and confirmation the QR format is standardized/open rather than proprietary.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “To manually transfer Authenticator codes to a new device, you need: Your old device with Google Authenticator codes”
   • [community] “Google Authenticator already has a QR-Code based very easy export procedure, I just backup my GAuth to my spare phone and tablet. It feels s…”
   • [community] “Google Authenticator has a feature to allow export of all saved codes into one QR code for re-import into Google Authenticator running on an…”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “Google Authenticator does not allow you to include your codes in your backup, even when it's encrypted. So due to Google Authenticator, losi…”

   proof ↗⚑ flag

   1Password~partialclaimed4/10

   1Password documents a general export feature to move data to another app ([1password-docs-15]), and TOTP/OTP storage is documented ([1password-docs-20]), but no evidence specifies that TOTP secrets are included in the export or that the export format is an open, readable standard (e.g., otpauth:// URIs or plain text) rather than 1Password's proprietary 1PUX format. Missing for 10: explicit confirmation that TOTP secrets are exportable, evidence of an open/readable export format, and independent/hands-on corroboration of successful migration of OTP secrets to another app.

   • [claimed-docs] “You can export your information from the 1Password apps if you want to move it to a different app.”
   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”

   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 1Password
   Google Authenticator—none0/10

   Evidence only covers transferring/syncing Google Authenticator codes between devices running Google Authenticator itself (QR export/import, Google Account sync), not bulk import of tokens originating in other authenticator apps (e.g., Authy, Microsoft Authenticator). No documentation or community report describes cross-app bulk import.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [claimed-docs] “To manually transfer Authenticator codes to a new device, you need: Your old device with Google Authenticator codes”
   • [community] “Google Authenticator has a feature to allow export of all saved codes into one QR code for re-import into Google Authenticator running on an…”

   proof ↗⚑ flag

   1Password~partialclaimed4/10

   1Password documents general import from other apps/browsers via CSV and the newer Credential Exchange standard on iOS 26+, and it supports storing one-time passwords, but no evidence explicitly confirms bulk import of authenticator/OTP tokens specifically from other authenticator apps (e.g., Google Authenticator, Authy) rather than just passwords/logins. Missing for 10: explicit documentation of OTP-specific bulk import/migration flow from named authenticator apps, and any hands-on/community confirmation that OTP secrets survive the CSV or Credential Exchange import.

   • [claimed-docs] “You can import data into 1Password from many different browsers and applications, including applications that export data in the comma-separ…”
   • [claimed-docs] “If you use 1Password on iOS or iPadOS 26 or later, you can import data directly from apps that support the Credential Exchange standard.”
   • [claimed-docs] “Learn how to transfer your passwords and other information from other applications into 1Password.”
   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”

   proof ↗⚑ flag

Migration

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

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

   Google's own docs describe a guided one-step transfer via signing into a Google Account (auto-sync) or scanning a QR export code between old/new devices, which matches the story closely. However, multiple hands-on community reports concretely contradict this working reliably in practice—users report app upgrades wiping all tokens, phone replacements losing TOTP keys despite expecting sync/backup, and account bans erasing synced codes entirely. missing for 10: independent verification that the guided transfer works consistently without data loss, and resolution of documented upgrade/sync failures.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [community] “I recently had a broken phone replaced and had depended on a backup to have my TOTP keys on my new phone. It was not a part of the phone bac…”
   • [community] “Don't upgrade! I just had this unpleasant experience and warned everyone... Warning: Google Authenticator upgrade loses all accounts.”
   • [community] “Every time I upgraded to a new iOS 7 beta, it wiped my Google Authenticator account tokens... I can't log in to my CampBX account anymore.”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   1Password—none0/10

   The evidence pack covers CLI/SDK/Connect integrations, browser passkeys, import/export from other apps, and OTP storage, but nothing describes a guided 'move to new phone' flow that automatically transfers all tokens/OTPs in one step. Cloud sync via account sign-in is 1Password's usual mechanism, but no citation confirms this specific onboarding experience or that it covers OTP/token migration seamlessly.

   ⚑ flag

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

   weight 2 · round drawn
   Google 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

   1Password—none0/10

   No evidence pack item mentions data residency, regional storage options, or the ability to choose where a vault/account's data is physically stored; 1Password's architecture appears to be a single managed cloud service without documented regional selection. Missing for 10: any documentation of region/residency selection, EU/US data center choice, or self-hosted storage location controls.

   ⚑ flag

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

   weight 3 · round drawn
   Google 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

   1Password—none0/10

   No evidence in the pack addresses any policy, setting, or documentation about opting out of or preventing data use for AI model training; the pack covers CLI/SDK/Connect/SSH/passkeys but nothing about AI training data usage or opt-outs.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Google Authenticator
   Google Authenticator~partialcommunity4/10

   Google Authenticator lets users delete individual codes (swipe to delete), edit/reassign codes, and use the app without a Google account (avoiding cloud retention entirely), giving some control over what data is stored and removed. However, there is no documented account-level 'delete all my data' or data-export-to-file control, and community reports describe difficulty exporting/backing up codes and total data loss if a Google account is banned or deleted, undermining full user control over retention. missing for 10: explicit data export/portability controls, account-wide deletion/retention settings, and confirmation that deleting codes removes them from Google's backend, not just the local view.

   • [claimed-docs] “To delete an Authenticator code on Android, swipe right on any code to show the delete option.”
   • [claimed-docs] “When you first open the app, tap Use without an account.”
   • [claimed-docs] “For additional protection, you can turn on Privacy Screen in Google Authenticator. This requires a verification from your device, like a PIN…”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “Google Authenticator does not allow you to include your codes in your backup, even when it's encrypted. So due to Google Authenticator, losi…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   1Password—none0/10

   The pack shows data export/import and an MCP design that avoids returning secrets to agents, but there is no evidence of explicit controls for data retention policies or deletion (e.g., audit-log retention settings, vault/item purge, GDPR-style deletion) tailored to AI-native workflows. missing for 10: retention policy controls, explicit deletion/purge mechanisms for AI-consumed data, documentation tying these to AI agent use.

   ⚑ flag

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

   weight 2 · round drawn
   Google 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

   1Password—none0/10

   No evidence pack item addresses telemetry/usage-tracking opt-out settings or privacy controls for AI-native usage; all evidence covers unrelated features like CLI, SSH, SDKs, and password management. This is a fair axis for any product handling sensitive data, but no documentation or community evidence confirms or denies a telemetry opt-out option.

   ⚑ 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 Google Authenticator
   Google Authenticator✓fullclaimed8/10

   Google's own docs describe a 'Privacy Screen' feature requiring PIN, pattern, or biometric verification before the app can be used, directly matching the story. No community evidence contradicts this specific lock-screen feature (complaints focus on sync/backup, not app-lock). Missing for 10: independent hands-on confirmation of the Privacy Screen feature working reliably across devices.

   • [claimed-docs] “For additional protection, you can turn on Privacy Screen in Google Authenticator. This requires a verification from your device, like a PIN…”

   proof ↗⚑ flag

   1Password—none0/10

   The evidence pack only covers CLI/SDK sign-in via system authentication (Touch ID/Windows Hello) for developer tooling, not the everyday consumer app's biometric/PIN lock screen protecting saved logins or OTP codes on a borrowed phone. No documentation or community evidence in the pack describes the mobile/desktop app requiring biometrics or PIN to unlock and view items like one-time passwords.

   ⚑ flag

Audits

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

   weight 2 · round drawn
   Google Authenticator—none0/10

   No evidence of any independent security audit of the app or its cloud sync protocol; a notable 2023 independent security researcher analysis found the sync data was unencrypted, but no formal published audit exists in the evidence pack, only community complaints about sync/backup reliability and trust concerns.

   ⚑ flag

   1Password—none0/10

   No evidence in the pack references independent third-party security audits, pen-test reports, or cryptographic protocol reviews of 1Password's app or sync protocol (e.g., no mention of the publicly known white paper audits by NCC Group/etc.). All citations cover CLI, SDKs, SSH, passkeys, and general product docs, none addressing audit publication.

   ⚑ 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 1Password
   Google 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

   1Password✓fullclaimed8/10

   Watchtower explicitly flags breaches, weak passwords, duplicate/reused items, and other security problems across saved items, directly matching the story's requirements, and it's surfaced natively in the app/browser extension (also flagging passkey-upgrade opportunities). Missing for 10: independent hands-on verification of Watchtower's breach-detection accuracy/coverage beyond vendor docs.

   • [claimed-docs] “Watchtower tells you about breaches, weak passwords, duplicate items, and other security problems with the items you have saved in 1Password…”
   • [claimed-docs] “opening Watchtower in 1Password, which now flags all of your existing logins that could be updated with a passkey”

   proof ↗⚑ flag

Push

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

   weight 2 · round drawn
   Google 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

   1Password—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 1Password
   Google 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

   1Password!disputedcontradicted4/10

   1Password markets a 'Connect Server' that can be deployed in a company's own infrastructure to access items via REST API (docs-4), which sounds like partial self-hosting, but this is only a caching/access layer in front of 1Password's cloud vaults, not a full self-hosted sync server. Community evidence directly contradicts the idea that secrets can stay entirely within an admin's perimeter: users note 1Password has 'no local vault storage' anymore and ask the vendor to 'continue support for local, non-cloud-based vault files' (comm-7, comm-8), confirming that the cloud remains the source of truth. Missing for 10: any documented on-prem deployment of the full sync/vault backend, migration guide for self-hosted secret storage, or evidence that Connect Server operates without 1Password's cloud.

   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [community] “Use a tiny portion of that to continue support for local, non-cloud-based vault files please.”
   • [community] “Except they have already started to diminish what used to make 1P great. We now get no native apps, no local vault storage, no upfront payme…”

   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 Google Authenticator
   Google Authenticator~partialclaimed4/10

   The GitHub repo (google/google-authenticator) documents open-source implementations of HOTP/TOTP and a PAM module, giving some basis for code review, but the evidence pack has no confirmation that the current shipped Android/iOS apps (which now handle cloud sync of seeds) actually correspond to this repo or receive active community review. missing for 10: evidence that the live mobile app source matches the published repo, evidence of active maintenance/community audits of the seed-handling code, and independent confirmation of code correctness.

   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”
   • [github] “Pluggable Authentication Module, aka PAM.”

   proof ↗⚑ flag

   1Password—none0/10

   No evidence in the pack indicates 1Password's client apps are open source or available for community code review; all citations describe closed commercial SDKs, CLI, Connect servers, and browser extension features without any open-source licensing or public repository claims for the core vault/client apps themselves. missing for 10: any statement of open-source licensing for 1Password clients, a public source repository for the desktop/mobile/browser apps, or third-party audit citing open code review.

   ⚑ 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 1Password
   Google Authenticator—none0/10

   Google Authenticator is a mobile/PAM app with no documented CLI or API for programmatic TOTP retrieval; evidence only covers manual app UI actions (sync, QR export, editing codes) and community complaints about backup/sync issues, none of which show agent-accessible code fetching.

   ⚑ flag

   1Password~partialprobed4/10

   1Password docs confirm OTP storage/lookup in the app (docs-20, docs-24, docs-19) and a general-purpose CLI/SDK for programmatic item access (docs-1, docs-2, docs-26, probe-rt-3), which together imply an agent could retrieve a TOTP field via CLI, but no evidence explicitly documents a TOTP-specific command or API response format for pulling a live 2FA code in an automated workflow. missing for 10: explicit CLI/API documentation of TOTP field retrieval (e.g., a `--otp` flag or field type), and any example/community confirmation of an agent completing 2FA end-to-end.

   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords, bank account details, pa…”
   • [claimed-docs] “1Password CLI brings 1Password to your terminal. Learn how to install the CLI, then integrate it with your 1Password app and sign in with To…”
   • [claimed-docs] “op item list --vault Private”
   • [claimed-docs] “1Password SDKs allow you to build integrations that programmatically interact with 1Password using Go, JavaScript, or Python.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official op CLI is packaged in Homebrew as the 1password-cli cask ('Command-line interface for 1Pas…”

   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 1Password
   Google 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

   1Password✓fullprobed8/10

   The 1Password CLI (`op`) and SDKs/Connect Server provide a local, scriptable, programmatic interface (not screen-scraping) that returns items, secrets, and OTP codes directly, and this is corroborated by real-world packaging (Homebrew cask) confirming it's a genuine local endpoint agents can shell out to. Missing for 10: no direct hands-on evidence of an AI agent actually querying the CLI/Connect Server for codes, and the newer MCP server explicitly withholds raw secrets from the agent, so full 'codes and secrets' access is only fully realized via CLI/SDK, not MCP.

   • [claimed-docs] “1Password CLI brings 1Password to your terminal. Learn how to install the CLI, then integrate it with your 1Password app and sign in with To…”
   • [claimed-docs] “op item list --vault Private”
   • [claimed-docs] “Use the 1Password Credential Broker to give CI/CD and other machine workflows short-lived access to secrets, without managing service accoun…”
   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [claimed-docs] “1Password SDKs allow you to build integrations that programmatically interact with 1Password using Go, JavaScript, or Python.”
   • [probe] “official CLI documented at https://www.1password.dev/cli/get-started”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official op CLI is packaged in Homebrew as the 1password-cli cask ('Command-line interface for 1Pas…”
   • [probe] “PROBE runtime (recorded 2026-09-15): 1Password's public docs MCP server at https://www.1password.dev/mcp completed a FULL keyless initialize…”

   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 1Password
   Google 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

   1Password✓fullcommunity8/10

   Docs confirm browser extension autofills passkeys during sign-in and stores/retrieves one-time passwords (TOTP), covering both parts of the story, with community corroboration of browser extension quality and iframe-aware autofill behavior. Missing for 10: explicit first-party statement or hands-on demo showing TOTP codes specifically autofilled (rather than just 'stored/accessed') and independent confirmation of passkey autofill working reliably across sites.

   • [claimed-docs] “you can now create, manage, and sign in with passkeys on a growing number of websites and apps directly from the 1Password browser extension”
   • [claimed-docs] “You can use 1Password to save the passkeys you create for your accounts and sign in to websites with passkeys in your browser.”
   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”
   • [claimed-docs] “1Password lets you easily sign in to sites, use suggested passwords, and find what you need – all without leaving your browser.”
   • [community] “1Password fills iframes based on their domain rather than the parents... In my opinion this is the right security model.”
   • [community] “Both the Fastmail and Privacy integrations have made 1Password a joy to use in the past few years. I've used premium BitWarden in the past, …”

   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 1Password
   Google Authenticator—none0/10

   No evidence of a desktop application; Google Authenticator is documented and discussed only as a mobile app with QR-based transfer/sync between phones, not a desktop client or vault.

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”

   proof ↗⚑ flag

   1Password~partialcommunity5/10

   Evidence confirms a desktop 1Password app exists (CLI integrates with 'the 1Password app' via Touch ID/Windows Hello, and community references to the Electron-based desktop client) and that vault/OTP data is stored centrally and accessible from apps generally, but no evidence pack item explicitly documents desktop-specific vault UI or OTP display screens, and community notes flag desktop app quality concerns (Electron complaints, no native app comments). missing for 10: dedicated desktop-app feature docs (OTP display, vault browsing UI on Mac/Windows/Linux), first-party screenshots or hands-on confirmation of parity with mobile, and resolution of the Electron/native-app criticism.

   • [claimed-docs] “1Password CLI brings 1Password to your terminal. Learn how to install the CLI, then integrate it with your 1Password app and sign in with To…”
   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”
   • [community] “Except they have already started to diminish what used to make 1P great. We now get no native apps, no local vault storage, no upfront payme…”
   • [community] “It would be nice to say goodbye to Electron, though... (referring to 1Password's desktop app).”
   • [community] “Mandatory 'No Linux client' comment :| Does anyone have any insight if this is a pure business decision or there's something holding them ba…”

   proof ↗⚑ flag

Watch

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

   weight 1 · round to 1Password
   Google 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

   1Password✓fullclaimed8/10

   1Password explicitly documents Apple Watch support for quickly looking up saved information including one-time passwords, letting users read codes without pulling out their phone. This directly matches the story, though evidence is limited to Apple Watch (no mention of other smartwatch platforms like Wear OS) and lacks independent hands-on corroboration. Missing for 10: evidence of Android/Wear OS smartwatch support, independent user reviews confirming the watch OTP experience.

   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords, bank account details, pa…”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords”
   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”

   proof ↗⚑ 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 drawn
   Google Authenticator—none0/10

   Docs only describe syncing codes via a Google Account (google-authenticator-docs-1,4) with no mention of end-to-end encryption or a vendor-blind key, and community reports explicitly note that storing codes in 'google cloud doesn't satisfy me' and that losing access to the Google account means losing all 2FA data, implying no such E2E encryption exists.

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [community] “Storing it in the google cloud doesn't satisfy me. I just simply want the codes under my control... google still makes it stupendously diffi…”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   1Password—none0/10

   The evidence pack contains no documentation of 1Password's end-to-end encryption architecture, Secret Key design, or zero-knowledge claims for vaults/backups — it only covers CLI/SDK/Connect/SSH tooling and unrelated community commentary on UX and pricing. Without any citation describing the encryption design or vendor-key-never-held guarantee, this axis is unevidenced.

   ⚑ 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 1Password
   Google Authenticator~partialcommunity5/10

   Google's docs confirm automatic cross-device sync via Google Account sign-in, works offline, and supports multiple accounts (docs-1,4,5,10), but Authenticator is a mobile-only app with no native desktop/computer client, so the 'computer' leg of the story is unsupported. Community reports also cite historical sync/backup failures and account-loss risk tying codes to a Google Account (comm-1, comm-7, comm-12, comm-13), showing real caveats even if not disproving the current sync feature outright. Missing for 10: a computer/desktop client, independent hands-on confirmation the modern sync feature works reliably across all device types without data loss.

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [claimed-docs] “Authenticator can sync codes for multiple Google Accounts and display them from the same mobile device.”
   • [claimed-docs] “You can still generate codes without an internet connection or mobile service.”
   • [community] “I recently had a broken phone replaced and had depended on a backup to have my TOTP keys on my new phone. It was not a part of the phone bac…”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”
   • [community] “Don't upgrade! I just had this unpleasant experience and warned everyone... Warning: Google Authenticator upgrade loses all accounts.”

   proof ↗⚑ flag

   1Password✓fullcommunity6/10

   Docs show 1Password stores and retrieves one-time-passwords (tokens) across the browser, Apple Watch, and other apps (docs-20, docs-19/24, docs-21), implying that the same vault (and thus tokens) is accessible from phone, tablet, and desktop, and a community comment confirms 'desktop and mobile work great' (comm-9), suggesting real-world cross-device consistency. However none of the evidence explicitly describes the automatic sync mechanism or confirms real-time consistency across all three device types simultaneously. Missing for 10: explicit documentation of the cloud-sync architecture ensuring instant multi-device consistency, and independent testing/benchmarks of sync latency or conflict handling.

   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords, bank account details, pa…”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords”
   • [claimed-docs] “1Password lets you easily sign in to sites, use suggested passwords, and find what you need – all without leaving your browser.”
   • [community] “I've used 1password for years and so far haven't had any problem, all apps (desktop and mobile) work great, but I don't understand why they …”

   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 Google Authenticator
   Google Authenticator!disputedcontradicted5/10

   Google's own docs describe two documented recovery paths — signing into your Google Account to auto-sync codes across devices, or scanning a QR-code export to transfer codes to a new device (google-authenticator-docs-1/3/4/11) — which is exactly the story's ask. However, multiple hands-on community reports concretely contradict reliability of this recovery: users report app upgrades wiping all tokens with no recovery (comm-13, comm-14), phone backups explicitly excluding Authenticator data (comm-1, comm-8), and losing all codes permanently if the tied Google Account is banned/deleted (comm-7, comm-12). Missing for 10: independent verification that account-sync recovery works consistently across real device-loss scenarios, and resolution of the backup-exclusion/account-ban failure modes.

   • [claimed-docs] “With Google Authenticator, you can synchronize your verification codes across all your devices, simply by signing in to your Google Account.”
   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device.”
   • [claimed-docs] “To manually transfer Authenticator codes to a new device, you need: Your old device with Google Authenticator codes”
   • [community] “I recently had a broken phone replaced and had depended on a backup to have my TOTP keys on my new phone. It was not a part of the phone bac…”
   • [community] “Does that mean one can use adb to backup Google Authenticator's data as well? Last time I tried, the app data was explicitly marked as exclu…”
   • [community] “Don't upgrade! I just had this unpleasant experience and warned everyone... Warning: Google Authenticator upgrade loses all accounts.”
   • [community] “Every time I upgraded to a new iOS 7 beta, it wiped my Google Authenticator account tokens... I can't log in to my CampBX account anymore.”
   • [community] “If Google ever decides to kick you out of your account, Authenticator data will be gone. Google has done this on several occasions in the pa…”
   • [community] “Imagine your google account getting deleted cuz you got banned from Google and the suddenly you lose all your 2FA secrets cuz they are part …”

   proof ↗⚑ flag

   1Password—none0/10

   The evidence pack covers 1Password's password/OTP storage, sync, import/export between apps, SSH/passkey features, and developer tooling, but contains no documentation of a lost-device recovery path (e.g., Emergency Kit, Secret Key re-enrollment, account recovery flow) that would restore an everyday user's tokens on a new device after losing their phone. Missing for 10: documented device-loss/account-recovery procedure, evidence of Secret Key or Emergency Kit restoration flow, any confirmation that OTPs specifically survive a lost-device scenario.

   ⚑ 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 1Password
   Google 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

   1Password✓fullprobed7/10

   1Password documents multiple programmatic surfaces (CLI, SDKs in Go/JS/Python, Connect Servers REST API, Service Accounts) explicitly for 'Automate item management: Programmatically manage items in your 1Password account,' which covers creating and updating vault entries including credentials. These are official, well-documented interfaces suitable for agent-driven automation. Missing for 10: an explicit documented example/field reference for seeding TOTP secrets via these APIs, and independent/hands-on verification that write operations (create/update, not just read) work reliably in practice.

   • [claimed-docs] “Automate item management: Programmatically manage items in your 1Password account.”
   • [claimed-docs] “1Password SDKs allow you to build integrations that programmatically interact with 1Password using Go, JavaScript, or Python.”
   • [claimed-docs] “1Password Connect Servers allow you to securely access your 1Password items and vaults in your company's apps and cloud infrastructure using…”
   • [claimed-docs] “1Password Service Accounts help automate secrets management in your applications and infrastructure without the need to deploy additional se…”
   • [claimed-docs] “1Password CLI brings 1Password to your terminal. Learn how to install the CLI, then integrate it with your 1Password app and sign in with To…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the official op CLI is packaged in Homebrew as the 1password-cli cask ('Command-line interface for 1Pas…”

   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 drawn
   Google 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

   1Password—none0/10

   The evidence pack covers CLI/SDK developer tooling, personal password features, import/export, and community sentiment, but contains no documentation of admin console policies for enforcing app lock, restricting export, or mandating master password strength across an organization. This axis clearly applies to a business password manager, but no supporting evidence is present.

   ⚑ flag

Sharing

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

   weight 2 · round drawn
   Google 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

   1Password—none0/10

   The evidence pack covers 1Password's developer tooling (CLI, SDKs, Connect, SSH agent) and personal features (Watchtower, OTP storage, passkeys) but contains no mention of shared vaults, collections, group/per-member permissions, or admin controls for team sharing of TOTP items. Missing for 10: documentation of shared vaults/collections, per-member access control settings, or admin console screenshots showing granular sharing permissions for TOTP logins.

   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”
   • [claimed-docs] “Watchtower tells you about breaches, weak passwords, duplicate items, and other security problems with the items you have saved in 1Password…”

   proof ↗⚑ flag

Enrollment

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

   weight 3 · round to Google Authenticator
   Google Authenticator✓fullclaimed8/10

   Docs and GitHub evidence confirm the app scans QR codes to add accounts and generates RFC 6238 TOTP codes, including offline (docs-3, docs-10, gh-1). Community feedback criticizes backup/sync/loss issues, not the basic scan-and-generate flow, so the core story is undisputed. Missing for 10: independent hands-on confirmation of the exact scan-to-first-code experience and no first-party UX walkthrough beyond support docs.

   • [claimed-docs] “On your old device, create a QR code... On your new device, tap Scan QR code”
   • [claimed-docs] “You can still generate codes without an internet connection or mobile service.”
   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”

   proof ↗⚑ flag

   1Password~partialclaimed4/10

   Docs confirm 1Password stores and generates one-time passwords for two-step verification (docs-20, docs-19/24), which implies TOTP support, but no evidence explicitly describes the QR-code scanning flow for adding a new TOTP account. Missing for 10: explicit documentation or screenshots of QR code scanning to add a new TOTP entry, and independent/hands-on confirmation of the immediate code-generation experience.

   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords, bank account details, pa…”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords”

   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 Google Authenticator
   Google Authenticator✓fullclaimed8/10

   Docs explicitly state you can 'Use without an account' at setup and that codes generate 'without an internet connection or mobile service,' confirming fully offline, account-free TOTP generation (core RFC 6238 implementation per GitHub). Community discussion focuses on backup/sync/account-loss risks, not on offline generation failing, so no contradiction of this specific axis. Missing for 10: independent hands-on confirmation specifically testing offline-without-account code generation.

   • [claimed-docs] “When you first open the app, tap Use without an account.”
   • [claimed-docs] “You can still generate codes without an internet connection or mobile service.”
   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”

   proof ↗⚑ flag

   1Password!disputedcontradicted3/10

   1Password does store and display OTP codes (docs-20, docs-24), but the product fundamentally requires a 1Password account/subscription and cloud-synced vault to unlock and view items — community evidence explicitly states 1Password has moved away from local, non-cloud vault storage ('no native apps, no local vault storage... The VC rot has already set in'), directly contradicting the 'no vendor account required' claim. Missing for 10: any first-party or independent confirmation of a fully offline mode with no account signup/sync dependency, and no evidence disputes this gap.

   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords”
   • [community] “My 1Password installation is grandfathered from a time when it was just a standalone app, without subscription. Will it just stop working on…”
   • [community] “Use a tiny portion of that to continue support for local, non-cloud-based vault files please.”
   • [community] “Except they have already started to diminish what used to make 1P great. We now get no native apps, no local vault storage, no upfront payme…”

   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 1Password
   Google Authenticator—none0/10

   Evidence only shows basic manual reordering (drag-to-reorder), swipe-to-edit/delete, and username/account editing — there is no mention of search, folders/groups, or service icons for organizing many tokens. missing for 10: search functionality, folder/group organization, service icons, any at-scale organization feature for dozens of tokens.

   • [claimed-docs] “To edit your Authenticator code on Android, swipe left on any code to show the edit option.”
   • [claimed-docs] “To organize your Authenticator codes, touch and hold any code, then drag to reorder to a desired location.”
   • [claimed-docs] “To delete an Authenticator code on Android, swipe right on any code to show the delete option.”
   • [claimed-docs] “To edit your Authenticator code on Android, swipe left on any code to show the edit option. You can update the username for the code or chan…”

   proof ↗⚑ flag

   1Password~partialclaimed3/10

   Docs confirm 1Password stores and quickly surfaces one-time passwords (including via Apple Watch) and flags login issues via Watchtower, but the pack provides no evidence of folder/tag/group organization, dedicated search, or service icons for TOTP entries specifically. missing for 10: explicit search functionality, folder/tag/group organization for TOTP items, service icon display for OTP entries, independent hands-on validation of organizing many tokens.

   • [claimed-docs] “Learn how to use 1Password to store and quickly access your one-time passwords when you turn on two-step verification for a website.”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords, bank account details, pa…”
   • [claimed-docs] “Use 1Password on your Apple Watch to quickly look up information: credit card numbers and PINs, one-time passwords”
   • [claimed-docs] “Watchtower tells you about breaches, weak passwords, duplicate items, and other security problems with the items you have saved in 1Password…”

   proof ↗⚑ flag

Variants

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

   weight 2 · round to Google Authenticator
   Google Authenticator~partialclaimed3/10

   The GitHub docs confirm the underlying library supports HOTP (RFC 4226) and TOTP (RFC 6238) algorithms, giving some basis for HOTP counter support, but there is no evidence anywhere in the pack that the consumer app exposes Steam Guard mode, custom periods, or custom digit lengths — the mobile app UI evidence only shows scanning QR codes, editing username, and deleting entries. missing for 10: Steam Guard token support, custom period configuration, custom digit-length configuration, and any UI/setting for manual HOTP counter entry.

   • [github] “These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (…”
   • [github] “The Google Authenticator project includes implementations of one-time passcode generators for several mobile platforms.”
   • [claimed-docs] “To edit your Authenticator code on Android, swipe left on any code to show the edit option.”

   proof ↗⚑ flag

   1Password—none0/10

   The evidence only confirms basic one-time password storage (docs-20, docs-19) but contains no mention of Steam Guard tokens, HOTP counter-based codes, or custom period/digit-length TOTP support. Missing for 10: any documentation of Steam Guard support, HOTP counter handling, or custom period/digit configuration.

   ⚑ flag