# Cursor couldn't load any chat in any project all of a sudden

**URL:** <https://forum.cursor.com/t/cursor-couldnt-load-any-chat-in-any-project-all-of-a-sudden/78049>\
**Category:** Bug Reports\
**Created:** [April 11, 2025, 2:47pm UTC](https://forum.cursor.com/t/cursor-couldnt-load-any-chat-in-any-project-all-of-a-sudden/78049 "2025-04-11T14:47:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![yeswecan](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yeswecan/32/27731_2.png) [@yeswecan](https://forum.cursor.com/u/yeswecan)\
**Post date:** [April 11, 2025, 2:47pm UTC](https://forum.cursor.com/t/cursor-couldnt-load-any-chat-in-any-project-all-of-a-sudden/78049/1 "2025-04-11T14:47:47Z")

</div>

Thanks for reporting a bug you have found in Cursor!  
Please add the following info to help us diagnose your issue:

✅ **Check the forum** to ensure the issue hasn’t been reported already  
Did that.

🐞 Provide a **clear description** of the bug  
I open any project, open any chat from history, it shows “Loading…” then back to blank new chat.

🔄 Explain how to **reproduce the bug** (if known)  
I’m not sure how to get rid of this, probably have to research how to reinstall cursor and drop its cache without destroying the chats (which are obviously of huge importance).

📷 Attach **screenshots or recordings** (e.g., `.jpg`, `.png`, `.mp4`).  
Not feel like this is needed in this case. Loading mesage looks normal but it returns me to new chat, that’s all.

💻 Tell us your operating system and your **Cursor version** (e.g., `Windows, 0.x.x`).  
OSX 14.2.1, Cursor 0.48.8

🚫 Tell us if the issue stops you from using Cursor.  
On the verge of stopping me, yes. It’s tough. Not the only bug but this is quite brutal.

Hope it goes away via reinstalling or rebooting, otherwise - not good.

---

<div class="post-metadata">

**Author:** ![yeswecan](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yeswecan/32/27731_2.png) [@yeswecan](https://forum.cursor.com/u/yeswecan)\
**Post date:** [April 11, 2025, 6:29pm UTC](https://forum.cursor.com/t/cursor-couldnt-load-any-chat-in-any-project-all-of-a-sudden/78049/2 "2025-04-11T18:29:39Z")

</div>

I found out that there’s an error in the console that corresponds to this, happens each time a chat failed to load:

```auto
2025-04-11 21:28:04.595 [error] [composer] unloadComposer: composer is still in use with strong handle: Error: [composer] unloadComposer: composer is still in use with strong handle
    at Z8t.unloadComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:591:47075)
    at no.deleteComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:591:76407)
    at vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:50:87348
    at HP (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:50:87102)
    at s.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:50:87337)
    at xh.deleteComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2986:11609)
    at vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:50:87348
    at HP (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:50:87102)
    at s.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:50:87337)
    at xh.handleDeselectingComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2986:5897) [composer] unloadComposer: composer is still in use with strong handle

```

---

<div class="post-metadata">

**Author:** ![yeswecan](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yeswecan/32/27731_2.png) [@yeswecan](https://forum.cursor.com/u/yeswecan)\
**Post date:** [April 11, 2025, 8:31pm UTC](https://forum.cursor.com/t/cursor-couldnt-load-any-chat-in-any-project-all-of-a-sudden/78049/3 "2025-04-11T20:31:45Z")

</div>

Sometimes it prints this into console, different error:

```auto
2025-04-11 23:30:41.464 [error] [canceled] This operation was aborted: ConnectError: [canceled] This operation was aborted
    at t (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2405:131870)
    at async Object.countTokens (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:98:15147)
    at async oni.updateTokenCount (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3063:4843) [canceled] This operation was aborted

```

---

<div class="post-metadata">

**Author:** ![yeswecan](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yeswecan/32/27731_2.png) [@yeswecan](https://forum.cursor.com/u/yeswecan)\
**Post date:** [April 11, 2025, 8:53pm UTC](https://forum.cursor.com/t/cursor-couldnt-load-any-chat-in-any-project-all-of-a-sudden/78049/4 "2025-04-11T20:53:39Z")

</div>

The new chats I create are loaded. All the chats before today are not loading. I checked on the disk in Application Support, they’re all there and the weight seems fine. So they’re not really gone, just stopped being loaded by the frontend.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [May 11, 2025, 8:54pm UTC](https://forum.cursor.com/t/cursor-couldnt-load-any-chat-in-any-project-all-of-a-sudden/78049/5 "2025-05-11T20:54:38Z")

</div>

Closed on May 11, 2025, 8:54pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
