[BUG] MAX Plan Paid. Access to IP Cut Off

Resolved 💬 3 comments Opened Apr 20, 2026 by 10-3Lives Closed May 28, 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?

Summary

Paying Claude Max subscriber ($214 charged April 20, 2026, receipt 2362-6656-6119, invoice 0BE9B955-0027). Account authenticates via Google OAuth, email validates, but backend routes to /onboarding?returnTo=/magic-link? with "Create Account" screen instead of loading existing account. Affects claude.ai (Safari/Opera/Chrome), Claude Desktop, and Claude Code CLI simultaneously. iPhone is the only working surface, likely because it has a pre-existing authenticated session.

Matches the signatures in #36797 and #25056 almost verbatim.

Environment

  • macOS current, Apple Silicon (M5 Max MacBook Pro + M4 Pro Mac mini)
  • iPadOS current
  • iOS current (working)
  • Claude Code v2.1.41
  • Account type: Claude Max (Pro+ tier, $214/mo)
  • Auth method: Continue with Google (glennotf@gmail.com)

Reproduction

  1. Open claude.ai in any browser on Mac (tested Safari, Opera, Chrome — fails in all three, ruling out browser cache/cookie)
  2. Click "Continue with Google"
  3. Complete Google OAuth — email validates successfully (confirmed via bottom-of-screen "validated" text in Claude Desktop)
  4. Observed: Redirect to /onboarding?returnTo=/magic-link? with "Let's create your account" screen and a "Not found" indicator in the corner
  5. Expected: Load existing paid account

Same behavior in Claude Desktop (validates then forces signup) and Claude Code (claude CLI throws OAuth error after theme-selection prompt).

API Key Workaround Attempt

Per #25069, #27900, #28438: attempted ANTHROPIC_API_KEY env var bypass after full state wipe (~/.claude.json, ~/.claude/, security delete-generic-password -s "Claude Code-credentials"). Claude Code v2.1.41 still hits post-theme OAuth gate. Returns "Invalid API key. Fix external API key" on freshly-generated key from console.anthropic.com (which I CAN log into — developer surface is intact).

Evidence of Backend State, Not Client State

  • iPhone (with pre-existing cached session) works — strongly suggests client-side state is fine and server-side account lookup is the failure point
  • Three browsers on Mac fail identically — rules out browser-level issues
  • Anthropic's own FIN support bot confirmed via email: "your account is properly set up... the organization_uuid backend errors... may be a server-side account state issue that requires our engineering team's attention" — then closed the ticket 6 hours after charging my card, citing "we haven't heard from you"
  • console.anthropic.com login works fine (confirms I'm not globally locked out — only the consumer product surface rejects me)

Diagnostic Artifacts

Full diagnostic PDF available on request. Includes ranked cause analysis, Safari cookie-jar poisoning hypothesis (ruled out by three-browser Mac failure), Google Workspace DNS migration hypothesis (ruled out by hd-claim architecture), and the stacked two-bug pattern (iPad Safari cookie + Mac server-side orphan).

Related Issues

  • #36797 — identical symptom pattern, closed as invalid without public fix
  • #25056 — backend organization_uuid: Extra inputs are not permitted error
  • #25069 — macOS ANTHROPIC_API_KEY ignored
  • #27900 — interactive mode requires existing OAuth before accepting API key
  • #28438 — post-theme forced-login regression
  • #41886 — claude login doesn't clear stale oauthAccount in config

What I've Tried

  • Full client state wipe (all known paths + keychain)
  • Google permissions revoke at myaccount.google.com/permissions
  • Fresh API key generation (rejected as "invalid" despite console access)
  • Magic link — same /onboarding redirect
  • FIN support ticket — auto-closed same day as billing, no human contact
  • Three browsers on Mac, fresh profiles, incognito mode

Impact

Paid subscriber comprehensively locked out of paid service. No functional path to human support via advertised channels (FIN auto-closes). Billing continues.

Ask

Server-side account state reset / re-link existing subscription. This appears to require engineering, not frontline support, per FIN's own admission.

What Should Happen?

The expected behavior of a company like Anthropic is to be better than the fundamental attribution error. This is clearly not a device problem. You have tagged other's problems with this same thing as "closed" without resolution.

What's the resolution for the fact I can now only access and work with my own IP on my phone?

Error Messages/Logs

Steps to Reproduce

  1. Try to login using Google Authentication as you always have.
  2. Watch your access to your IP disappear after you login.
  3. Try to log back in and get OAuth errors on Claude Code, repeated "enter your email address/you are verified" cycles on Claude Desktop without securing access.
  4. Watch Google Authentication spin in Claude.ai while doing nothing.
  5. Ask for help
  6. Get no reply after two days.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

4.6

Claude Code Version

Can't run Claude Code due to Anthropic caused OAuth errors ,

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗