Hey Dan,
I just chatted with Composer, and the issue is still there… anyway we can figure this out?
Same error,
unresponsive assistant ( chat and composer)
Pro membership
Tried:
*** rewind composer**
*** new chat**
*** Reinstalling ( cursor-0.43.6x86_64.AppImage)**
Still no luck
1 Like
Composer unresponsive… Any Idea how to sort this.
1 Like
Click on new composer it helps me with this issue
Hey Dan… any update here? Is the invite to chat with the engs still available?
1 Like
Started seeing this issue as of the last update as well.
Composer history completely gone. Composer and chat unresponsive as well.
Here is what I see
$ cursor
Error: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_cursorlYUsrN/resources/app/node_modules.asar.unpacked/@vscode/spdlog/build/Release/spdlog.node)
at process.func [as dlopen] (node:electron/js2c/node_init:2:2214)
at Module._extensions..node (node:internal/modules/cjs/loader:1470:18)
at Object.func [as .node] (node:electron/js2c/node_init:2:2441)
at Module.load (node:internal/modules/cjs/loader:1215:32)
at Module._load (node:internal/modules/cjs/loader:1031:12)
at c._load (node:electron/js2c/node_init:2:13801)
at Module.require (node:internal/modules/cjs/loader:1240:19)
at N (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:2:647)
at bindings (/tmp/.mount_cursorlYUsrN/resources/app/node_modules.asar/bindings/bindings.js:112:48)
at Object.<anonymous> (/tmp/.mount_cursorlYUsrN/resources/app/node_modules.asar/@vscode/spdlog/index.js:3:35)
at l._compile (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:2:1261)
at Module._extensions..js (node:internal/modules/cjs/loader:1432:10)
at Module.load (node:internal/modules/cjs/loader:1215:32)
at Module._load (node:internal/modules/cjs/loader:1031:12)
at c._load (node:electron/js2c/node_init:2:13801)
at Module.require (node:internal/modules/cjs/loader:1240:19)
at require (node:internal/modules/helpers:179:18)
at F (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:3:98)
at e.load (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:2:1642)
at p.load (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:1:13512)
at l (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:3:9339)
at Object.errorback (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:3:9458)
at p.triggerErrorback (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:1:13806)
at /tmp/.mount_cursorlYUsrN/resources/app/out/main.js:1:13557
at e.load (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:2:1659)
at p.load (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:1:13512)
at l (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:3:9339)
at a._loadModule (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:3:9467)
at a._resolve (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:4:452)
at a.defineModule (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:3:5561)
at a._relativeRequire (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:3:6185)
at D (/tmp/.mount_cursorlYUsrN/resources/app/out/main.js:3:8517)
at /tmp/.mount_cursorlYUsrN/resources/app/out/vs/code/electron-main/main.js:72:41096
at new Promise (<anonymous>)
at D (/tmp/.mount_cursorlYUsrN/resources/app/out/vs/code/electron-main/main.js:72:41076)
at S.r (/tmp/.mount_cursorlYUsrN/resources/app/out/vs/code/electron-main/main.js:72:42199)
at new S (/tmp/.mount_cursorlYUsrN/resources/app/out/vs/code/electron-main/main.js:72:42074)
at I.q (/tmp/.mount_cursorlYUsrN/resources/app/out/vs/code/electron-main/main.js:72:42747)
at I.createLogger (/tmp/.mount_cursorlYUsrN/resources/app/out/vs/code/electron-main/main.js:71:5364)
at I.createLogger (/tmp/.mount_cursorlYUsrN/resources/app/out/vs/code/electron-main/main.js:72:43149)
at /tmp/.mount_cursorlYUsrN/resources/app/out/vs/code/electron-main/main.js:107:1579
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Me.a (/tmp/.mount_cursorlYUsrN/resources/app/out/vs/code/electron-main/main.js:107:1276) {
code: 'ERR_DLOPEN_FAILED',
phase: 'loading',
moduleId: '@vscode/spdlog',
neededBy: [ '===anonymous2===' ]
Hey, this error usually happens when you are running an OS version that is too old for Cursor.
See here:
Hey,
We’re still looking into this but we making some progress, will reach out if more users are needed, thanks!
Whew, took quite a while but that fix worked, thanks!
Still lost all my composer and chat history though 
I have the same issue. The New Composer helped.
+1! Have had the same issue a number of times. Pro account. Getting really annoying, have lots of valuable history in composer chat history!
So sad another upgrade, new broken features, even worst than loosing some functionality, I hope you and the team find the solution because I am a Fan,
In my case going the previous or a few messages before the failing ones in the composer, did not worked at all. And it seems to be consuming my fast request, I have tried a few times, with agent mode on as well ( that uses even more requests ) I just expect them to work ( and I know Cursor team as well, I want to be supportive, but lost some time trying to fix a bug, that Composer would do in minutes, and after a hour I gave up, to learn there is a bug. The FOMO of fast requests and reduced productivity is just going higher. But I will support the team and hope for good days ahead, it’s been a winter, but summer is comming !
UPDATE :
After reading more messages here I realized that I was in a days old chat, so I tried to start fresh with the + button ( Cmd+N) to create a new composer and it’s running 
! Thankfully 
forgot to add :
Version: 0.43.6
VSCode Version: 1.93.1
Commit: a846435528b4b760494a836f96f0739889253530
Date: 2024-12-06T05:11:55.168Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.1.0
2 Likes
Works for me as well. Thank you
Hey,
This issue is a bug that we identified over the last few days. We managed to diagnose it yesterday and are working on a fix as we speak!
You should hopefully see an update in the near future that resolves these stuck chat/composer session but, for now, starting a new chat/composer session with the plus (+) button should get things working again!
Sorry for any inconvenience caused here!
1 Like
starting a new chat/composer session via + button does not get things working again.
Hey Dan,
Does this mean i can expect cursor composer to work with my history? that’s really critical for me
Thank you for getting a fix out! This has been incredibly frustrating over the last few weeks, happened a few times, I had some invaluable context in a composer chat and started getting desperate, evaluated 4 different mac apps for stitching together screenshots, none worked successfully, tried going into developer tools to identify the scrolling area and take a screenshot of the whole node somehow, doesn’t work…
Talking to ChatGPT about it gave me a lead about GitHub - thomas-pedersen/cursor-chat-browser: A web application for browsing and managing chat histories from the Cursor editor's AI chat feature. View, search, and export your AI conversations in various formats. - which would incidentally be a really handy tool to have working! It launches but doesn’t seem to be able to locate the logs on disk? Did you guys change how you store that stuff on disk perhaps?
Hey,
We aren’t able to support this app, or exporting our chat history through any 3rd party tool as there’s a lot of complexity that goes on behind the scenes!
This is a highly requested feature, and is something we hope to release in the future, but especially with the complexity of the agent having inline terminals, codeblock snippets and text, we want to make sure we do it right!
On a side note, it looks like, from your screenshot, that the app you’re trying to run attempted to call cmd.exe, so it’s possible it only works for Windows!
Hey Dan, are there any updates here?
I still can’t access the composer chat that houses all the relevant context. I’ve been blocked from building my app for a couple of weeks now and I’m getting a bit worried.
Would love just even a sense of timing so i can plan.
I am seeing this issue today and starting a new chat via “+” is not solving for me.