# Problem with continuing to use chat

**URL:** <https://forum.cursor.com/t/problem-with-continuing-to-use-chat/155168>\
**Category:** Bug Reports\
**Tags:** context, chat\
**Created:** [March 18, 2026, 2:07pm UTC](https://forum.cursor.com/t/problem-with-continuing-to-use-chat/155168 "2026-03-18T14:07:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Milenko\_Stojkovic](https://avatars.discourse-cdn.com/v4/letter/m/258eb7/32.png) [@Milenko\_Stojkovic](https://forum.cursor.com/u/Milenko_Stojkovic)\
**Post date:** [March 18, 2026, 2:07pm UTC](https://forum.cursor.com/t/problem-with-continuing-to-use-chat/155168/1 "2026-03-18T14:07:15Z")

</div>

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

Cursor IDE

### Describe the Bug

I haven’t worked on this project for a couple of weeks. The other chats for this project are working normally. I wanted to continue working in a chat where I had previously addressed a specific issue. I received a message that:  
Connection failed. Please try again, or contact support if the issue persists.

The strange thing is that I have all the previous communication I had in that chat saved.

### Steps to Reproduce

I wanted to continue working in a chat where I had previously addressed a specific issue. I received a message that:  
Connection failed. Please try again, or contact support if the issue persists.

The strange thing is that I have all the previous communication I had in that chat saved.

### Expected Behavior

I expected the chat to continue without any problems. That didn’t happen.

### Operating System

Windows 10/11

### Version Information

Version: 2.6.13 (system setup)  
VSCode Version: 1.105.1  
Commit: 60faf7b51077ed1df1db718157bbfed740d2e160  
Date: 2026-03-06T06:17:49.499Z  
Build Type: Stable  
Release Track: Default  
Electron: 39.6.0  
Chromium: 142.0.7444.265  
Node.js: 22.22.0  
V8: 14.2.231.22-electron.0  
OS: Windows\_NT x64 10.0.26200

### For AI issues: which model did you use?

The models included are:  
Composer 1.5  
GPT-5.3 Codex  
GPT-5.4  
Sonnet 4.6  
Opus 4.6

### For AI issues: add Request ID with privacy disabled

Request ID: 05429b6a-e873-4215-af6b-58f926623c54  
Image selected in conversation was not found on disk: c:\Users\Asus\AppData\Roaming\Cursor\User\workspaceStorage\images\capture-2fdd1e33-fda5-409c-b046-8b875359f191.png  
Error: Image selected in conversation was not found on disk: c:\Users\Asus\AppData\Roaming\Cursor\User\workspaceStorage\images\capture-2fdd1e33-fda5-409c-b046-8b875359f191.png  
at bey (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34286:12955)  
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34286:14295  
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46860:284  
at async Promise.all (index 0)  
at async F3u.\_gatherImageSelections (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46860:242)  
at async Promise.all (index 2)  
at async F3u.buildComposerSelectedContext (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46865:2303)  
at async F3u.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46865:5498)  
at async F3u.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46865:13663)  
at async bMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34308:17597)  
at async Ea (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45790:4826)

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![Stanislav\_Kostomakha](https://avatars.discourse-cdn.com/v4/letter/s/82dd89/32.png) [@Stanislav\_Kostomakha](https://forum.cursor.com/u/Stanislav_Kostomakha)\
**Post date:** [March 18, 2026, 3:37pm UTC](https://forum.cursor.com/t/problem-with-continuing-to-use-chat/155168/4 "2026-03-18T15:37:08Z")

</div>

LOL, right now i have the same issue with approximately same timing: about 2 weeks ago switched to another project, upgraded cursor in meantime and now back to previous project but all my findings and final implementation plan created with Cursor are lost and i’m back to point zero 💩

What i did: i’ve seached all files in cursor settings by keyword ( in my case ticket number ) and found two sets of files like:

1. `%APPDATA%\Cursor\User\globalStorage\state.vscdb[.backup]`
2. `%APPDATA%\Cursor\User\workspaceStorage...\state.vscdb[.backup]`

These files are sqlite3 database, so i copied them to temporal location in same workspace and tasked Cursor to extract what we can have missed. At the time of writing it is still extracting data. When finished i’m going to ask it to analyse previous work and build new Cursor plan (it seems not recovered).

Suspecting in my cause chats were lost because of upgrading Cursor, i didn’t touch anything else this time.

Cheers,

Stas

---

<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:** [March 18, 2026, 4:30pm UTC](https://forum.cursor.com/t/problem-with-continuing-to-use-chat/155168/5 "2026-03-18T16:30:26Z")

</div>

Hey, this is a known bug. The error in the stack trace says it directly:

> Image selected in conversation was not found on disk: c:\Users\Asus\AppData\Roaming\Cursor\User\workspaceStorage\images\capture-2fdd1e33-fda5-409c-b046-8b875359f191.png

If an image was attached in a chat and then the file got deleted or moved on disk, Cursor can crash when trying to resume that chat. The “Connection failed” message is misleading here. The issue is actually local.

Workaround: start a new chat in the same project. Sadly, you can’t continue that exact old chat if the attached image is missing right now.

The team is aware of this bug. There’s no exact ETA yet, but your report helps with prioritization.

@Stanislav_Kostomakha your case might be different. If the chats are completely gone, not just showing “Connection failed”, it’s more likely related to an update, not a deleted image. Can you confirm if the chats disappeared from the history list, or they’re still visible but won’t open?

---

<div class="post-metadata">

**Author:** ![Stanislav\_Kostomakha](https://avatars.discourse-cdn.com/v4/letter/s/82dd89/32.png) [@Stanislav\_Kostomakha](https://forum.cursor.com/u/Stanislav_Kostomakha)\
**Post date:** [March 18, 2026, 5:26pm UTC](https://forum.cursor.com/t/problem-with-continuing-to-use-chat/155168/6 "2026-03-18T17:26:38Z")

</div>

Hi Dean,

Sorry, it was mistake on my side - i found that chat in history, so no problem with it 🙂

Cheers,

Stas

---

<div class="post-metadata">

**Author:** ![Milenko\_Stojkovic](https://avatars.discourse-cdn.com/v4/letter/m/258eb7/32.png) [@Milenko\_Stojkovic](https://forum.cursor.com/u/Milenko_Stojkovic)\
**Post date:** [March 24, 2026, 8:49am UTC](https://forum.cursor.com/t/problem-with-continuing-to-use-chat/155168/7 "2026-03-24T08:49:58Z")

</div>

In the meantime, I solved this in another way. I exported the contents of the old chat to an md file and opened a new chat. In the new chat, I specified the location of the md file, and told it that I wanted to continue working.

---

<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:** [April 15, 2026, 8:50am UTC](https://forum.cursor.com/t/problem-with-continuing-to-use-chat/155168/9 "2026-04-15T08:50:09Z")

</div>

Closed on April 15, 2026, 8:50am UTC

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