Account: allow changing the email address in-place, instead of forcing a new account

Status Closed — not planned
Maintainer reply None cached
Activity 7 comments · opened Jul 11, 2026 · closed Jul 14, 2026

Summary / Feature request

Please add the ability to change the email address on an existing Claude account in-place (via account settings, with an email-verification step). Today this is impossible.

Current state

Per the Help Center (How do I change the email address associated with my account?), changing your account email is not possible. The only path offered is to cancel the current subscription and create a brand-new account with the new email.

Why this matters

  • Creating a new account means losing conversation history, Projects, and settings, and re-doing subscription/billing. That is a heavy, disruptive cost for what should be a trivial change.
  • Email addresses legitimately change (domain moves, provider switches, alias/forwarding-domain migration, deliverability issues). Being unable to update your own account email feels user-hostile and patronizing, and pushes people toward account churn — or toward cancelling entirely out of principle.
  • It is now a common baseline expectation: essentially every other major service (Google, Microsoft, Proton, GitHub, etc.) supports an in-place, verified email change. Claude being the exception is a notable gap, especially for paying subscribers who have significant history and tooling tied to the account.

Requested behavior

  • In Settings → Account, allow the user to enter a new email address.
  • Send a verification link to the new address; on confirmation, the account email is updated in place.
  • History, Projects, subscription, and all settings stay intact on the same account.
  • Handle SSO/Google-login accounts sensibly (e.g. allow adding/switching a password-based login, or re-linking the identity).

Context

Real-world trigger: a user migrating away from an alias/forwarding email domain across all their services was able to update the email everywhere except Claude — the one service they most depend on — and the only workaround (cancel + recreate) would destroy their history and setup. In-place email change would fully solve this.

Thanks for considering.

View original on GitHub ↗

4 Comments

github-actions[bot] · 3 months ago

Closing for now — this doesn't appear to be about Claude Code. Please open a new issue if this is still relevant.

Colk-tech · 2 months ago

I would be very grateful if this feature could be implemented.

See the comment below:
https://github.com/anthropics/skills/issues/1143#issuecomment-5241301874

7maram7 · 1 month ago

or at least to be able to use a passkey rather than sending an email every time

Z2Flow · 1 month ago

+1
That the code does not exist when Anthropic could write the code with Claude is ironic.
This speaks volumes about Anthropic's care of customers.

Showing cached comments. Read the full discussion on GitHub ↗