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

Support Bug Reports
,
1

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
Screenshot 2026-07-07 135259.png2399×375 31 KB

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

5

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.

8

Doesn’t fix when the window is a SSH connection

(MacOS)