Some chats fail to load or open

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Some chats in the “Agents” tab become inaccessible. Clicking a chat (last opened ~7 days ago) either:

  • Does not open the chat panel
  • Opens the panel in the editor after multiple clicks but never loads, even after waiting
    This appears limited to specific chats; other chats open normally. The affected chat was previously functional.

Steps to Reproduce

  1. Open Cursor
  2. Go to the “Agents” tab
  3. Click a chat that was last opened ~7 days ago (or older)
  4. Observe one of:
  • The chat panel does not appear
  • The chat panel appears in the editor but remains in a loading state indefinitely

Expected Behavior

864e5001-7621-47fa-963a-a5674041f6be

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.15 (user setup)
VSCode Version: 1.105.1
Commit: bb2dbaacf30bb7eb9fd48a37812a8f326defa530
Date: 2025-12-30T20:30:37.151Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

Reproducible with the same chat
Other chats in the list open normally
Multiple clicks sometimes make the panel appear, but it still does not load
Waiting does not resolve the loading state

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
Severe Issues After Latest Update: Agents Not Loading, Frequent Crashes
Severe Issues After Latest Update: Agents Not Loading, Frequent Crashes
2

I apologize for loud music in the video (Mute it)

3

Hey, thanks for the report. This is a known issue with loading older chats that affects some users on Windows.

It can sometimes happen when loading long chats with lots of code blocks. The UI component can’t handle initialization.

For debugging, please try:

  1. Help → Toggle Developer Tools → Console
  2. Click the affected chat
  3. Check the Console for errors, especially [composer] No composer data handle found or any authentication errors

For the future, I’d recommend:

  • Export important chats regularly (three dots → Export Chat)
  • Install the SpecStory extension for automatic backups

Please share what you see in the console when you click the chat.

2 Likes
4

This happened to me as well, today I opened cursor and it prompted me to set the initial settings as if I was a new user, it also prompted me to log in with github again, it has no acess to my previous chats, everything seems to be wiped out, except my code (fortunately)!

1 Like
5

Can the feature configuration of version 1.7 be restored? Don’t you think loading chat logs is slow every time you open them? This experience is terribleimage

1 Like
6

Here are logs:

workbench.desktop.main.js:13689 [composer] Error hydrating conversation checkpoint from blob store Error: illegal tag: field no 0 wire type 0

composerMigrations] error migrating composer instance data: ConnectError: [data_loss] Failed to hydrate conversation checkpoint from blob store

workbench.desktop.main.js:566 [composer] Error loading composer data: Error: [composerMigrations] error migrating composer instance data: ConnectError: [data_loss] Failed to hydrate conversation checkpoint from blob store

[composer] Error hydrating conversation checkpoint from blob store Error: illegal tag: field no 0 wire type 0

[composerMigrations] error migrating composer instance data: ConnectError: [data_loss] Failed to hydrate conversation checkpoint from blob store

[composer] Error loading composer data: Error: [composerMigrations] error migrating composer instance data: ConnectError: [data_loss] Failed to hydrate conversation checkpoint from blob store

workbench.desktop.main.js:13855 [composer] No composer data handle found [handleDeselectingComposer]

[composer] Error hydrating conversation checkpoint from blob store Error: illegal tag: field no 0 wire type 0

workbench.desktop.main.js:561 [composerMigrations] error migrating composer instance data: ConnectError: [data_loss] Failed to hydrate conversation checkpoint from blob store

[composer] Error loading composer data: Error: [composerMigrations] error migrating composer instance data: ConnectError: [data_loss] Failed to hydrate conversation checkpoint from blob store

[composer] Error hydrating conversation checkpoint from blob store Error: illegal tag: field no 0 wire type 0

[composerMigrations] error migrating composer instance data: ConnectError: [data_loss] Failed to hydrate conversation checkpoint from blob store

[composer] Error loading composer data: Error: [composerMigrations] error migrating composer instance data: ConnectError: [data_loss] Failed to hydrate conversation checkpoint from blob store

[composer] No composer data handle found [handleDeselectingComposer]
7

Thanks for the logs! This confirms the issue: this chat’s checkpoint data got corrupted during migration.

[data_loss] Failed to hydrate conversation checkpoint from blob store
illegal tag: field no 0 wire type 0

Unfortunately, this specific chat can’t be recovered. The checkpoint data is corrupted at the serialization level.

This is a known issue, and the team is working on improving chat storage stability. To help prevent data loss in the future:

  • Export important chats regularly (three dots, then Export Transcript)
  • The SpecStory extension can help with automatic backups

Sorry for the trouble.

1 Like
8

same, once updating to the latest stable version, never happened before and the chat wasnt even long

BUT actually ALL OLDER chats are corrupted now???

and the Agent chat window freezes up

1 Like