Account silently downgraded from Pro without action taken — billing/support issue
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?
What's Wrong?
My account was downgraded from Pro to Free without any action on my part. I did not cancel, request a downgrade, or receive any notification that this was happening.
- Plan before: Pro
- Plan after: Free
- Date noticed: 9/3/2026
- Account email: Will provide privately if needed
- Billing cycle: Annual
Support attempts (all failed):
- Fin AI Agent (in-app support): Stated no ability to escalate to a human and that it can't resolve account sync issues itself
- Email to support@anthropic.com: Stuck in the same FinAI loop I already went through in the desktop app despite requesting human support multiple times
Why I'm filing this here:
This is a claude.ai billing/account issue, not a Claude Code bug — filing here because
per other reports (#48780, #45497, #56281, #58402) this appears to be the only actively
monitored Anthropic repository, and there's no dedicated billing/platform repo.
Impact:
Paying customer with no functional path to a human for a billing dispute or account issue resolution.
Evidence available:
<img width="958" height="1350" alt="Image" src="https://github.com/user-attachments/assets/90101084-b47f-47cf-82b1-cf2e3dacfeb9" />
What Should Happen?
- Restore my account to Pro
- Explain why the downgrade occurred
- Provide a human support response within a reasonable timeframe, with a ticket number
Error Messages/Logs
Steps to Reproduce
This is a persistent account sync issue I have been experiencing since I subscribed to a paid plan.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
9/2/26
Claude Code Version
N/A
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗