Unable to Load AI Chat – Chat Pane Stuck Loading and Closes Automatically

Describe the Bug

Description:
When I try to open the AI chat in Cursor, the chat pane gets stuck on the loading screen and then closes automatically after a few seconds. This issue persists even after restarting the application and my computer.

Observed Errors:
[Background Composer] No preferred remote found after 10 attempts
[composer] No composer data handle found

What I’ve Tried:
Restarted Cursor and my computer.
Logged out and back into my Cursor account.
Tried different networks (including mobile hotspot).
Updated Cursor to the latest version (and also tried previous stable versions).
Checked the developer console and logs for errors.

Steps to Reproduce

Steps to Reproduce:
Open Cursor.
Attempt to open the AI chat panel.
Observe that the chat does not load and the pane closes by itself.

Expected Behavior

The chat panel should load and allow me to interact with the AI assistant.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.6 (Universal)
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:16:57.571Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0

Additional Information

macOS version: 24.5.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, this issue is usually related to a large chat history in your project. To solve the problem, try manually deleting most of the history, possibly the oldest chats. You can also try renaming or moving the project. This will help you quickly clear the history.

Additionally, you can delete the history by navigating to this path and sorting the folders by modification date. Choose the one that was used recently, you can delete it or save a backup just in case:

Windows: %APPDATA%\Cursor\User\workspaceStorage
macOS: ~/Library/Application Support/Cursor/User/workspaceStorage
Linux: ~/.config/Cursor/User/workspaceStorage

If your history is important to you, you can try exporting it using this extension: