### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet - [x] This is a single bug report (please file separate reports for different bugs) - [x] I am using the latest version of Claude Code ### What's Wrong? Clicking the magic link in a regular browser window (with an active session) fails with "We were unable to verify you with this link." Opening the exact s

[BUG] Magic link fails with "unable to verify" unless opened in incognito window

Status Open

Reported on v2.1.183

Maintainer reply None cached

Activity 3 comments · opened Jun 21, 2026

Preflight Checklist

[x] I have searched existing issues and this hasn't been reported yet
[x] This is a single bug report (please file separate reports for different bugs)
[x] I am using the latest version of Claude Code

What's Wrong?

Clicking the magic link in a regular browser window (with an active session) fails with "We were unable to verify you with this link." Opening the exact same link in an incognito tab works immediately.

What Should Happen?

Magic link works in a normal browser window

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

Run claude and choose to log in via browser
Click the magic link from the email in a normal browser window
See "We were unable to verify you with this link"
Open the same link in an incognito window → succeeds

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.183 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

3 Comments

DwayneSamuels · 1 month ago

the normal-window/incognito control is useful because it points toward pre-existing browser state rather than the email link itself. one paired capture would make the handoff much more decisive:

same browser build and same untouched magic link in each mode
redirect chain with status codes and final URL
names (not values) of cookies/local-storage keys present before the click
first auth response that differs between normal and incognito, including any safe request/correlation ID
result in a fresh regular browser profile, then after clearing only Anthropic site data
result with extensions disabled in the regular profile

That splits stale session/site data from an extension interaction or a server-side link-consumption race. Please redact the magic-link token, cookie values, and auth response secrets before attaching anything publicly.

A compact browser-handoff template for preserving path, state, and the first failure signal is here: https://github.com/samelogic/assets/tree/master/resources/cant-reproduce-bug-report-template

mockdeep · 1 month ago

Looks like this may be a duplicate of this issue. It can be caused by the ClearURLs extension, so if you disable that it will allow you to log in.

Vercidium · 1 month ago

For clarification I don't use the ClearURLs extension.