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

Open Beginner friendly
#111,180 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

Start with the Trusted Devices section at https://code.claude.com/docs/en/remote-control#trusted-devices and compare its terminology with the security alert described in the issue. Check related issues #82095 and #81164 for context. Done means the documentation explains the alert and connects its “passkey” wording to trusted devices; the issue also suggests broader product and Help Center changes whose scope may need maintainer guidance.

Written by the indexing model from the issue text.

Description

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)

Dominant language
TypeScript
Stars
156k
Forks
25k
Avg merge
16h 19m
Merged PRs (30d)
5

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anthropics/claude-code

All issues in anthropics/claude-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.