[BUG] Persistent Auth/Onboarding Loop preventing access to Paid Max Plan
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?
Description:
Persistent Authentication/Onboarding Loop on a Paid Max Plan (5 seats).
Details:
Since April 8th, I am unable to use the Claude CLI (claude-code) or the Web Interface. Despite a successful login, the system redirects indefinitely to /onboarding. Even after completing the onboarding steps, the session is not recognized, and the loop restarts.
Environment:
Plan: Claude Max (5 Seats)
Account: georg-schmidt-photography@web.de
Ticket-ID: 215473808533821 (Unresolved for 12 days)
What Should Happen?
Expected Behavior:
After login, the CLI/Web interface should recognize the existing active subscription and grant access to the workspace instead of triggering the onboarding flow repeatedly.
Error Messages/Logs
No specific error code in CLI, just a silent redirect to the browser for onboarding which never completes the authentication handshake. This appears to be a server-side database mapping issue for my specific account.
Steps to Reproduce
- Open terminal and run claude (or go to claude.ai).
- Complete the login process with a paid Max/Team account.
- Observe the redirect to claude.ai/onboarding.
- Complete the onboarding steps.
- Instead of landing in the chat interface, the system redirects back to step 3 (infinite loop).
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
0.2.29
Claude Code Version
latest
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
This auth-loop occurs on both the Web UI and the CLI. It prevents any usage of the tool for my business account. Please check internal Ticket-ID 215473808533821 for billing and account mapping details.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗