Repository navigation
Breaks Claude.AI login #510
Description
Activity
Just encountered this issue too.
Apparently, the problem was caused by the trailing
==. Unfortunately, according to RFC3986, they're completely legal in URI fragments, so it's definitely a bug.The relevant part of the URI grammar from the RFC:
URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ] fragment = *( pchar / "/" / "?" ) pchar = unreserved / pct-encoded / sub-delims / ":" / "@" pct-encoded = "%" HEXDIG HEXDIG sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "="Same here - just noticed the
=at the end of the URL was missing - which was giving me more headache than I ever imagined it would.The solution would be either:
- Whitelist Claude's login URL from ClearURLs
- Give users the ability to whitelist certain domains/URLs
Reacted by ChefExperteI dug into this and the
claude.ailogin break looks like a real bug in ClearURLs' fragment handling, not just a site-specific incompatibility.The likely problem is that fragment values are being parsed and reconstructed in a lossy way. In particular, fragments containing legal payloads like base64-style tokens with trailing
=/==can be rewritten incorrectly, which would explain why Claude magic links stop working.So I think there are two separate follow-ups here:
- A bugfix PR to preserve fragment content correctly and add regression coverage for cases like
#token==. - A separate feature PR to add a per-site disable/whitelist option, so users have an escape hatch when a site breaks before a fix is released.
I’m planning to handle these as two PRs rather than one combined change, so the correctness fix can be reviewed and shipped independently of the UI/feature work.
Reacted by sirati and WhitespaceQ- A bugfix PR to preserve fragment content correctly and add regression coverage for cases like
I opened a PR for the Claude-related breakage: #514
The fix is scoped to fragment preservation. The current fragment parser was reconstructing hash payloads in a lossy way when they contained trailing
=/==or additional=characters, which can break opaque tokens like the ones used in Claude magic links.This PR updates fragment parsing so it:
- splits only on the first
= - preserves everything after that verbatim
- keeps empty fragment values intact
That means cases like these now round-trip correctly:
#token=#token==#state=abc==#foo=bar=baz
I kept this separate from the proposed per-site disable feature so the correctness fix can be reviewed and shipped independently.
Reacted by Tim Pierce, A. Glez. B. and Saber- splits only on the first
- added a commit that references this issue
on Jul 10, 2026 - added a parent issue
on Jul 30, 2026
on claude.ai email magic links, the addon removes the trailing == (probably of the base64 encoding) which makes it impossible to login to claude