[DOCS] "New passkey added" security email doesn't match "Trusted devices" UI/docs — no way to verify the alert
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
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:
- Searched claude.ai settings for "passkey" → nothing. The setting is called "Trusted devices".
- Searched support.claude.com for "passkey" → nothing relevant.
- Checked iCloud Keychain, Strongbox and Google Password Manager → no Claude passkey in any of them.
- 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
- Use the same name everywhere: say "trusted device" in the email, or label the setting "Passkeys / Trusted devices".
- 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.
- 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.
- In the Trusted Devices docs, mention the alert email and what it looks like.
- 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
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anthropics/claude-code
-
area:vscode bug has repro platform:vscode platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anthropics/claude-code#111416 ·
-
area:plugins area:tui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
anthropics/claude-code#111195 ·
-
area:ide enhancement platform:macos platform:vscode
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anthropics/claude-code#111172 ·
-
area:mcp bug has repro platform:linux platform:wsl
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
anthropics/claude-code#111077 ·
-
area:cost area:mcp area:self-hosted-environments bug platform:linux
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
anthropics/claude-code#111048 ·
All issues in anthropics/claude-code
Similar issues
-
fix(resources): `flisk resources api` fails with a bare "too many arguments" and no hint; status, logs, down and networks already explain names are not positionalPossibly taken A pull request linked to this issue is open or already merged. Openarea: cli beginner beginner friendly bug community difficulty: easy dx easy first-timers-only good first issue hacktoberfest help wanted low-hanging fruit mentor available priority: P3 severity: low tech: typescript testing up-for-grabs ux
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
backlog-skill cat:docs documentation effort:s ready-for-agent sev:low
Difficulty 1/5 Under an hour Newbie friendliness 82/100
LucasSantana-Dev/Lucky#3284 ·
Maintainers usually reply within 1 day
-
.aif still missing from the pipeline and library MIME maps, AUDIO_INPUTS, and search aliasesPossibly taken A pull request linked to this issue is open or already merged. Openarea: backend bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
snapotter-hq/SnapOtter#5194 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
homarr-labs/homarr#7671 ·
Maintainers usually reply within 1 day
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw#203385 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day