Step-by-Step Fix
1) Reproduce once and capture the redirect URL
- Note the exact URL you land on after login
- Note timestamp and browser
This helps diagnose SSO/workspace loops.
2) Do the incognito test
- Open an incognito/private window
- Visit Claude and log in
If it works, it’s local browser state.
3) Clear only Claude site data
In your normal browser:
- clear site data for
claude.ai - close all Claude tabs
- reopen and sign in
4) Disable extensions and strict cookie settings
Temporarily disable:
- ad blockers
- privacy/script blockers
- cookie auto-delete tools
Also ensure cookies are allowed for Claude.
5) Turn off VPN/proxy and switch network
- disable VPN/proxy
- try a phone hotspot
If hotspot works, your network is filtering auth.
6) Check workspace/SSO context
If you’re on a team/workspace:
- confirm you’re logging into the correct email
- confirm you have access to the workspace
A common “login loop” is being authenticated but denied workspace access.
Common Root Causes
- stale cookies/session
- extensions blocking auth callbacks
- strict cookie policies
- VPN/proxy/network filtering
- SSO/workspace mismatch
- platform-side auth incident
Why This Happens
When you log into Claude, the authentication system creates a session cookie that stores your identity token. If that cookie fails to save — due to strict browser cookie settings, an extension clearing it, or the browser treating the claude.ai domain as third-party — Claude receives the login callback but cannot persist your session. The next page load detects no valid session and sends you back to the login page, creating a loop. This is almost always a local browser issue, not a Claude account problem.
Prevention Tips
- Keep one clean browser profile for Claude — a dedicated profile with no privacy extensions or strict cookie policies eliminates the most common source of redirect loops
- Allow cookies for claude.ai explicitly — if you use a browser with strict cookie settings (Brave, Firefox with enhanced tracking), add claude.ai to the exceptions list so session cookies are always accepted
- Avoid rapid retries when a loop starts — each retry attempt can create a new broken session fragment; stop, clear site data, and start fresh rather than clicking login repeatedly
- Test with incognito + hotspot before changing account settings — most redirect loops are local; this quick test confirms whether the issue is your browser, your network, or your account before you make any account-level changes
Additional FAQ
Q: The redirect loop only happens at work, but Claude works fine at home. What is different about my work network?
Corporate networks frequently use web filtering proxies that intercept HTTPS traffic and re-sign certificates. This breaks the cookie trust chain for sites like claude.ai, causing session cookies to be rejected. The browser completes login, Claude sets a session cookie, but the proxy strips or rejects it on the next request — so Claude sees an unauthenticated user and redirects to login again. The fix is to use mobile data at work, request that your IT team whitelist claude.ai in the proxy configuration, or use Claude's mobile app which often bypasses web proxy filtering.
Q: Can two-factor authentication or SSO requirements cause a redirect loop?
Yes. If your Claude account is connected to a workspace that uses Single Sign-On (SSO), a mismatch between your SSO session and Claude's session can create a persistent redirect loop. This happens when your SSO token has expired or your account's access to the Claude workspace has been modified. Sign out of both Claude and your SSO provider (Google Workspace, Okta, etc.), then sign back into the SSO provider first and then Claude. If the workspace access was revoked, contact your workspace administrator — they need to restore your access before the login can complete.
Q: I cleared cookies and the loop stopped, but it came back after a few hours. How do I prevent it from recurring?
A recurring redirect loop after cookie clearing suggests something is actively deleting your Claude session cookies. The most common culprits are cookie auto-delete browser extensions (Cookie AutoDelete, ClearURLs, etc.) configured to clear cookies on a timer or when the browser closes. Disable these extensions or add claude.ai and anthropic.com to their whitelist so session cookies are preserved between sessions. Without persistent session cookies, you will need to log in from scratch every time, and if anything briefly interrupts the login flow, the loop can restart.
Q: Does using a password manager cause the redirect loop?
Indirectly, yes — but rarely. Password managers that auto-submit forms can sometimes submit credentials too quickly before the login page has fully initialized, causing the auth flow to fail and redirect. If you use a password manager and notice it submits immediately, try disabling auto-fill for claude.ai and entering credentials manually. This slows the submission down enough for the page to initialize correctly. Modern password managers usually handle this well, so this is an edge case — check extensions first before blaming the password manager.
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.
Q: Why does clearing browser cache fix login issues? Your browser caches session tokens and authentication cookies that prove you are logged in. If these become corrupted or expire mid-session, the browser may present an invalid token on each page load, causing the server to reject the session and redirect you to login. Clearing site-specific data forces the browser to request fresh tokens on the next login, which resolves most session-related loops without affecting your other browser data.
Related Articles
- Claude usage limit reached
- Claude rate limit fix
- Claude blank page white screen
- Claude can't log in fix
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.
Related Articles
- Claude usage limit reached
- Claude rate limit fix
- Claude blank page white screen
- Claude can't log in fix
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.