[DOCS] "New passkey added" security email doesn't match "Trusted devices" UI/docs — no way to verify the alert

Aperta Adatta ai principianti
#111,180 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
68/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
documentation

Direzione di ricerca

Inizia dalla sezione «Trusted Devices» all’indirizzo https://code.claude.com/docs/en/remote-control#trusted-devices e confronta la terminologia con l’avviso di sicurezza descritto nell’issue. Consulta le issue correlate #82095 e #81164 per avere più contesto. Il lavoro è concluso quando la documentazione spiega l’avviso e collega il termine «passkey» ai dispositivi attendibili; l’issue suggerisce anche modifiche più ampie al prodotto e all’Help Center, il cui ambito potrebbe richiedere indicazioni dai maintainer.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:docs area:security documentation enhancement platform:macos
Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/remote-control#trusted-devices

Section/Topic

Trusted Devices — and the "Security alert: new passkey added to your Claude account" email

Current Documentation

The Trusted Devices section explains enrollment, the 18-hour sign-in window, biometric step-up, and managing devices at claude.ai/settings/account#trusted-devices. It says only the device's public key and basic metadata are stored, and that "Require trusted devices" is off by default on Pro/Max.

It does not mention:

  • the word "passkey" as the name users will see in alert emails
  • the security alert email itself
  • where the private key/credential is stored on the device
  • whether enrollment happens when "Require trusted devices" is off

There is also no Help Center article on support.claude.com for this feature.

What's Wrong or Missing?

I received "Security alert: new passkey added to your Claude account" (genuine email, SPF/DKIM/DMARC pass from mail.anthropic.com). Device field: "Electron on Mac OS X". Event: 2026-11-12 00:42 UTC.

I could not verify whether this was me or an attacker:

  1. Searched claude.ai settings for "passkey" → nothing. The setting is called "Trusted devices".
  2. Searched support.claude.com for "passkey" → nothing relevant.
  3. Checked iCloud Keychain, Strongbox and Google Password Manager → no Claude passkey in any of them.
  4. Only found the explanation in the Claude Code Remote Control docs, which the email doesn't link to and which don't mention "passkey" alerts.

I cannot confirm whether Claude Desktop showed an enrollment prompt, or what it said.

The result: an alert that cannot be matched to anything in the product. I genuinely thought my account had been hijacked. Users either panic like this, or learn to ignore these alerts — neither is good for a security notification.

Environment: Claude Desktop on macOS 5.1231.2 (269122), built 2026-11-10. Plan: Max.

Suggested Improvement
  1. Use the same name everywhere: say "trusted device" in the email, or label the setting "Passkeys / Trusted devices".
  2. In the email, name the app (e.g. "Claude Desktop on macOS") instead of "Electron on Mac OS X", and link to claude.ai/settings/account#trusted-devices and to the docs.
  3. Add a Help Center article on support.claude.com: what it is, when enrollment happens (including whether it happens with "Require trusted devices" off), where the credential is stored, and how to remove it.
  4. In the Trusted Devices docs, mention the alert email and what it looks like.
  5. Make the enrollment prompt in Claude Desktop state clearly that a passkey/trusted-device credential is being created.
Impact

High - Prevents users from using a feature

Additional Context

Related: #82095 (asks for Trusted devices / passkey documentation), #81164 (repeated "new trusted device" alert emails for the same device)

Lingua principale
TypeScript
Stelle
156k
Fork
25k
Merge medio
16h 19m
PR unite (30g)
5

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di anthropics/claude-code

Tutte le issue di anthropics/claude-code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.