Can’t create new chats

[sebelobrov]

I can’t create new chats in Agent Mode. Error details are below.

However, old chats work.

This is very strange. Is this just me?

Connection failed. If the problem persists, please check your internet connection or VPN

Request ID: 0d393023-6390-4390-ab1c-18d82ba4687b
ConnectError: [internal] 1322852437248:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

at nsu.$streamAiConnect (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6409:406134)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:565:80832
at async Object.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6477:42602)
at async o (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2815:1269)
at async Promise.allSettled (index 0)
at async fHr.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2815:6519)

[Artemonim]

Bug report it

[sebelobrov]

I did it. No reaction. I pay for the Ultra package. And I keep paying extra when the Ultra tokens run out. And now I can’t work at all because of another bug in the updates. It’s terrible.

[m0rfy (Тоха Воробей)]

fast fix disable http2 in setting

I assume this is due to frozen background chats that do not display work after an erroneous session closure and continue to maintain the connection.
An interesting fact is that sometimes you can see tasks doubling in the plan precisely because of several connections. From there, many tokens are now growing x2, x4, and so on.

[andrewh (Andrew Milich)]

@sebelobrov

0d393023-6390-4390-ab1c-18d82ba4687b

We’re not seeing widespread reports of this - recommend going to settings and running network diagnostics

[Dietrich_von_Zorger]

Same problem here. Request ID: aba384e8-da18-4959-9f5d-4bf260f33f9f
ConnectError: [internal] 288768:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:…\third_party\boringssl\src\ssl\tls_record.cc:486:SSL alert number 40

at nsu.$streamAiConnect (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%BE/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6409:406134)
at async vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%BE/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:565:80832
at async Object.run (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%BE/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6477:42602)
at async o (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%BE/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:2815:1269)
at async Promise.allSettled (index 0)
at async fHr.run (vscode-file://vscode-app/c:/Users/%D0%94%D0%BC%D0%B8%D1%82%D1%80%D0%BE/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:2815:6519)

[Dietrich_von_Zorger]

Changing this fixed problem though

[Rein_Wu (Rein)]

Go back to cursor 2.0.77, new version is never working to me

[Rein_Wu (Rein)]

Are you kidding me? I reported this error 11 days ago: Stops working again - Connection Error

[sebelobrov]

Thank you. This solved the problem.

[Igor_Mages (Igor Magès)]

All computers (various cities) of my company having this issue too after updating. This is real.

[Igor_Mages (Igor Magès)]

■■■■■■ response from a ■■■■■■ engineer

[Igor_Mages (Igor Magès)]

[sebelobrov]

@m0rfy

An interesting fact is that sometimes you can see tasks doubling in the plan precisely because of several connections. From there, many tokens are now growing x2, x4, and so on.

Am I correct in assuming I’m now paying 2-3x token usage? Is that why I maxed out my Ultra plan in just three days?

[m0rfy (Тоха Воробей)]

I think yes, and cursor well need reset tokens for all users.

Just used deep research, analysis from Nov 7 – Dec 7, 2025, confirm a critical regression in the Agent State Machine. The system exhibits “Split-Brain” behavior where the UI state desynchronizes from the Backend/Shadow Workspace state, leading to the accumulation of orphaned (“zombie”) processes.

Technical Diagnosis:

1. Session Leaking & PID Accumulation

Observation: Multiple Cursor Helper (Renderer) processes persist with high CPU usage after the main window is idle.

Hypothesis: The dispose() logic for Shadow Workspaces fails during soft timeouts. The parent process spawns a new worker but leaves the old worker’s IPC channel open.

Impact: Concurrent writes to globalStorage (SQLite WAL locking) and state.vscdb bloat (up to 13GB confirmed reports).

2. The “Packet Delta” Anomaly

Metric: \Delta P = P_{sent} - P_{rendered}.

Anomaly: In the “Terminal No Output” bug, the backend executes the shell command successfully (Exit Code 0), meaning packets were generated. However, they were routed to the Session ID of a zombie listener, not the active UI.

Security Implication: Backend rules allow multiple active sessions per user token to access distinct data paths simultaneously. Without strict serialization, this results in context cross-contamination (Project A data leaking into Project B’s stream).

3. Triplication Race Condition

The “Shadow Workspace” is intended to be a singleton for linting/diffing. Currently, it appears to be spawning multiple instances (A, B, C) on retries.

Race: Instances A, B, and C function competitively. When a diff is computed, all three push Apply events to the main thread. The main thread lacks a deduplication filter (e.g., checking event.nonce against current_session.nonce), resulting in the same code block being appended 2-3 times.