# New Agent stuck at Loading Chat after deleting current Chat from Archive

**URL:** <https://forum.cursor.com/t/new-agent-stuck-at-loading-chat-after-deleting-current-chat-from-archive/165060>\
**Category:** Bug Reports\
**Tags:** chat\
**Created:** [July 7, 2026, 7:12pm UTC](https://forum.cursor.com/t/new-agent-stuck-at-loading-chat-after-deleting-current-chat-from-archive/165060 "2026-07-07T19:12:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sgornick](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sgornick/32/104459_2.png) [@sgornick](https://forum.cursor.com/u/sgornick)\
**Post date:** [July 7, 2026, 7:12pm UTC](https://forum.cursor.com/t/new-agent-stuck-at-loading-chat-after-deleting-current-chat-from-archive/165060/1 "2026-07-07T19:12:10Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Cannot delete the currrent conversation from the Cursor IDE without it causing the New Agent tab to show Loading Chat, and nothing more.

### Steps to Reproduce

1.) Show Chat History, Archive my current conversation  
2.) Chat History → Archive, Delete the conversation I archived in 1.

A New Agent tab will show, with “Loading Chat” (and nothing further)

Developer Tools shows (as showing in attached screenshot):

AggregateError: Encountered errors while disposing of store  
ERR [composer] No loaded composer found: Error: [composer] No loaded composer found

### Expected Behavior

Expected behavior:  
New Agent tab, with the edit window for a new conversation

### Screenshots / Screen Recordings

 ![Screenshot 2026-07-07 135259.png](https://us1.discourse-cdn.com/cursor1/original/3X/0/5/05eef3a5b8c659d4a7a5fde8112f2dcafe378ff9.png)

### Operating System

Windows 10/11

### Version Information

Version: 3.10.17 (user setup)  
VS Code Extension API: 1.125.0  
Commit: c89f45b831621cdc5e951694db44fecd8fab1150  
Date: 2026-07-05T06:39:45.228Z  
Layout: IDE  
Build Type: Stable  
Release Track: Default  
Electron: 40.10.3  
Chromium: 144.0.7559.236  
Node.js: 24.15.0  
V8: 14.4.258.32-electron.0  
xterm.js: 6.1.0-beta.256  
OS: Windows\_NT x64 10.0.26200

### Additional Information

This is new behavior … likely since v3.10.17

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [July 8, 2026, 4:33am UTC](https://forum.cursor.com/t/new-agent-stuck-at-loading-chat-after-deleting-current-chat-from-archive/165060/5 "2026-07-08T04:33:24Z")

</div>

Hey, thanks for the detailed report. The steps and the DevTools log really helped. I reproduced it on my side. The trigger is deleting the chat that’s currently open or selected. It’s not tied to Windows or archive. After that, the New Agent tab gets stuck on Loading Chat because of `[composer] No loaded composer found`.

For now, the workaround is Developer: Reload Window via `Cmd/Ctrl+Shift+P`. That brings the tab back to a working state.

We’ve logged the bug on our side. I can’t share a timeline for a fix yet. I’ll post an update in the thread once I have one.

---

<div class="post-metadata">

**Author:** ![jmginer](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jmginer](https://forum.cursor.com/u/jmginer)\
**Post date:** [July 8, 2026, 9:01am UTC](https://forum.cursor.com/t/new-agent-stuck-at-loading-chat-after-deleting-current-chat-from-archive/165060/8 "2026-07-08T09:01:59Z")

</div>

Doesn’t fix when the window is a SSH connection

(MacOS)

---

<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:** [July 10, 2026, 9:02am UTC](https://forum.cursor.com/t/new-agent-stuck-at-loading-chat-after-deleting-current-chat-from-archive/165060/9 "2026-07-10T09:02:37Z")

</div>

Closed on July 10, 2026, 9:02am UTC

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