Cursor switching to the old billing mode has an error bug

Describe the Bug

Due to model service provider issues and network-related connection errors, users are prompted to retry, but the retries keep failing. However, each retry consumes the user’s valuable 500 quick request attempts!! The error also deducts one attempt.
You can check my request ID
Request ID: 905c156e-6cec-4c03-a2a3-3c5f0657a4e5
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”},“isExpected”:false}

Steps to Reproduce

Reappears suddenly during use or due to network reasons

Expected Behavior

Old billing mode, incorrect point deduction refund and fix this issue

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.0.0 (user setup)
Commit: 1.96.2
Date: 53b99ce608cba35127ae3a050c1738a959750860
Electron: 2025-06-04T19:44:25.253Z
ElectronBuildId: 34.5.1
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.0
OS: 13.2.152.41-electron.0

Additional Information

Request ID: 905c156e-6cec-4c03-a2a3-3c5f0657a4e5
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”},“isExpected”:false}
ConnectError: [unavailable] Error
at pEa.$endAiConnectTransportReportError (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4240:224508)
at uWs.S (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:492:13557)
at uWs.Q (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:492:13335)
at uWs.M (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:492:12423)
at uWs.L (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:492:11524)
at opt.value (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:492:10316)
at we.B (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46:2398)
at we.fire (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46:2617)
at mQe.fire (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4222:10378)
at u.onmessage (vscode-file://vscode-app/c:/Users/Administrator/AppData/Local/Programs/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6679:12344)

Does this stop you from using Cursor

No - Cursor works, but with this issue