Skip to content

feat(browser): scope payment autofill, passkeys and cross-device sync #33

Closed

Description

@trmosala

Problem

These are separate projects beyond the supplied core browser settings benchmark.

Implementation order

Browser backlog item 29 of 29. Phase: Deferred discovery. This is ordered planning, not a claim that Codex implements every item. Items 24–29 are optional additions.

Acceptance criteria

  • Produce separate proposals for payment autofill, passkey management and sync.
  • Identify supported platform APIs, security requirements and user value before any implementation.
  • Keep disabled/absent until each proposal is explicitly accepted; do not imply current support.

Dependencies

Engineering and validation

Reuse existing Chromium/Electron/OS facilities where available. Preserve main-process ownership and permission enforcement, add no placeholder controls, use existing i18n patterns, and test behavior with synthetic fixtures. Document platform limitations. Baseline: browser-tabs at 47fef3e; see packages/cm-browser/README.md and password-security.md.

Activity

  1. trmosala commented on Sep 18, 2026

    @trmosala
    OwnerAuthor

    Published the requested discovery proposals in 4536d8daf (docs(browser): scope future credential features). No runtime code or placeholder controls were added.

    packages/cm-browser/future-credential-proposals.md contains separate proposals for:

    1. Payment autofill — recommendation: do not build a CookieMonster card vault. Keep existing contact/address filling and consider only a provider-owned Payment Request/payment-handler spike after written product need and PCI/compliance approval. PAN/CVC must never enter CookieMonster storage, logs, agent context, backups, or sync.
    2. Passkeys — recommendation: delegate credential custody and user verification to OS/WebAuthn authenticators. Electron 44 supports WebAuthn account-selection mediation and macOS Touch ID configuration, while Windows exposes platform WebAuthn; a future site-mediation spike is plausible. CookieMonster becoming a native Windows/macOS credential-provider/passkey manager is a separate system product and remains deferred.
    3. Cross-device sync — recommendation: do not copy Chromium profiles or the OS-wrapped vault. A named WPP-owned backend could start with versioned nonsecret bookmarks/preferences, then separately reviewed end-to-end encrypted passwords/contacts with device keys, recovery, revocation, rollback protection, tombstones, conflict handling, and independent security review. Cookies/history/downloads/tabs/permissions/grants/passkeys/payment data stay local.

    Each proposal states user value, supported web/Electron/native APIs, concrete security requirements, platform/release evidence, non-goals, and the earliest acceptable next step. The README explicitly states all three features are absent and that the proposals do not authorize implementation.

    Primary references include current Electron Session/WebAuthn/safeStorage documentation, W3C Payment Request/WebAuthn/Secure Payment Confirmation, Microsoft Windows WebAuthn/passkey-manager APIs, Apple Authentication Services, and PCI SSC scope guidance. The normal push hook passed 31/31 typechecks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions