Chat breaking; add tab error and loading blank tab forever

[RafeSacks]

Describe the Bug

When I click on the + to add a new tab I see a notification in the bottom left:

Internal Lexical error: invariant() is meant to be replaced at compile time. There is no runtime version. Error: Reconciliation: could not find DOM element for node key %s

I have a “New Chat” tab that is “Loading Chat” forever. I saw this yesterday but was able to ignore it and use a new tab (this tab can not be closed!). Today I can’t do anything at all.

If I restart the app a number of tabs appear and the far right one is the “loading forever” tab . I can work, but if I try and get Gemini to continue, it seems to die without feedback, or sometimes with a failed to contact provider error, and then all chat, including new tabs, are broken until I restart again.

After restart the new tabs that never opened are in the history:

Steps to Reproduce

There is a chance just the new-tab error was caused when Gemini failed to contact the provider. I switched to GPT-5.1 and it seems to be continuing without breaking tabs. I can create a delete new tabs. The tab that is “loading forever” is still there and I can not close it.

Expected Behavior

No errors or extra tab loading forever.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.0 (Universal)
VSCode Version: 1.105.1
Commit: e4a384a82071fdda72d3442dffc0bcd25a8dfaf0
Date: 2025-11-19T06:32:16.968Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Gemini 3 PRO, GPT-5.1

For AI issues: add Request ID with privacy disabled

4f3d86bb-0416-4ce2-8fa7-efc7db91d98f

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, thanks for the report. It looks like this is a chat UI corruption issue triggered by Gemini provider errors.

First, please update to the latest version:

• You’re on version 2.1.0, and the current latest is 2.1.6
• Go to: Cursor → Check for Updates
• Install the update and restart Cursor

There have been several releases since 2.1.0, and the Lexical DOM error may already be fixed. The timing lines up with recent Gemini 3.0 integration issues that have been actively patched.

If the issue is still there after updating to 2.1.6, let me know.