Hey, let’s figure this out. Most likely, the “plan not recognized” issue is caused by a connection problem, not billing. If the app can’t reach the server, it can’t confirm your subscription.
I need a couple things to diagnose it:
Go to Cursor Settings > Network > Run Diagnostics and paste the results here.
Try disabling HTTP/2: in the app settings Cmd + , search for HTTP/2 and enable Disable HTTP/2. Then restart Cursor.
Try logging out and logging back in from Cursor Settings.
About “loses connection with large chats”: this is a known issue. Long chats can cause disconnects. A workaround is to start a new chat once the current one gets too big.
Are you using a VPN, proxy, or corporate antivirus? That’s a common cause of issues like this on Windows.
I’m fairly sure this is not an HTTP/2 issue and is most likely not a problem on my side. From my perspective, the app is not stable enough to work with, and I cannot rely on it for tasks that require predictable timing.
I’m sorry, but I don’t consider this a stable tool for professional work.
Has anyone else experienced this, or is there a solution?
I see the screenshot with the diagnostics. Authentication UI is red with Timeout waiting for EverythingProvider. That confirms the issue.
This is a bug on our side, not yours. The problem is that the app is sending an outdated auth data format, so the server can’t confirm your subscription. That’s why it says plan not recognized. Your subscription is active Pro+. The issue is the communication between the client and the server.
Please try this. It should reset the cached auth data:
In Cursor Settings, fully sign out of your account
Close Cursor
Open it again and sign in
This isn’t just sign out and back in. Signing out clears the auth cache, which is what’s causing the problem.
The team is aware and it’s not only affecting you. We don’t have an ETA yet, but your report helps us prioritize it.