Red x next to file it was editing and it's unable to edit any files?

Support Bug Reports
1

image
image431×850 29.1 KB

Hi, so it’s becoming pretty common that now it displays a red x mark next to the file it was trying to edit, it goes away after sometime but it’s making my workflow unreliable.

edit:
here are the errors
workbench.desktop.main.js:965 [composer] ToolFormer: error in toolWrappedStream undefined
toolWrappedStream @ workbench.desktop.main.js:965
workbench.desktop.main.js:1918 [composer] Error in AI response: ConnectError: [canceled] This operation was aborted
at yhs.$endAiConnectTransportReportError (workbench.desktop.main.js:2318:111488)
at zmi.S (workbench.desktop.main.js:4948:42054)
at zmi.Q (workbench.desktop.main.js:4948:41832)
at zmi.M (workbench.desktop.main.js:4948:40920)
at zmi.L (workbench.desktop.main.js:4948:40021)
at K9e.value (workbench.desktop.main.js:4948:38813)
at M.B (workbench.desktop.main.js:57:748)
at M.fire (workbench.desktop.main.js:57:967)
at _X.fire (workbench.desktop.main.js:2300:10356)
at l.onmessage (workbench.desktop.main.js:4993:11916)
(anonymous) @ workbench.desktop.main.js:1918
workbench.desktop.main.js:1918 [composer] Failed to get complete AI response
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:1918
workbench.desktop.main.js:965 [composer] ToolFormer: error in toolWrappedStream toolu_01VCE6UmxPSkPS659CJAVQuN
toolWrappedStream @ workbench.desktop.main.js:965
workbench.desktop.main.js:591 ConnectError: [resource_exhausted] Error
at yhs.$endAiConnectTransportReportError (workbench.desktop.main.js:2318:111488)
at zmi.S (workbench.desktop.main.js:4948:42054)
at zmi.Q (workbench.desktop.main.js:4948:41832)
at zmi.M (workbench.desktop.main.js:4948:40920)
at zmi.L (workbench.desktop.main.js:4948:40021)
at K9e.value (workbench.desktop.main.js:4948:38813)
at M.B (workbench.desktop.main.js:57:748)
at M.fire (workbench.desktop.main.js:57:967)
at _X.fire (workbench.desktop.main.js:2300:10356)
at l.onmessage (workbench.desktop.main.js:4993:11916)
streamResponse @ workbench.desktop.main.js:591
workbench.desktop.main.js:1918 [composer] Error in AI response: ConnectError: [resource_exhausted] Error
at yhs.$endAiConnectTransportReportError (workbench.desktop.main.js:2318:111488)
at zmi.S (workbench.desktop.main.js:4948:42054)
at zmi.Q (workbench.desktop.main.js:4948:41832)
at zmi.M (workbench.desktop.main.js:4948:40920)
at zmi.L (workbench.desktop.main.js:4948:40021)
at K9e.value (workbench.desktop.main.js:4948:38813)
at M.B (workbench.desktop.main.js:57:748)
at M.fire (workbench.desktop.main.js:57:967)
at _X.fire (workbench.desktop.main.js:2300:10356)
at l.onmessage (workbench.desktop.main.js:4993:11916)
(anonymous) @ workbench.desktop.main.js:1918
workbench.desktop.main.js:1918 [composer] Failed to get complete AI response
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:1918
3workbench.desktop.main.js:953 Error checking file existence: Error: Unable to resolve filesystem provider with relative file path ‘cursor.aisettings:cursor/aisettings’
(anonymous) @ workbench.desktop.main.js:953
726workbench.desktop.main.js:645 InlineDiffService#addLine: line contains newline characters, which is not supported
addLinesToDiff @ workbench.desktop.main.js:645
workbench.desktop.main.js:965 [composer] ToolFormer: error in toolWrappedStream toolu_01JEEtJboUZ8x7PZmD6uwAeR
toolWrappedStream @ workbench.desktop.main.js:965
workbench.desktop.main.js:591 ConnectError: [resource_exhausted] Error
at yhs.$endAiConnectTransportReportError (workbench.desktop.main.js:2318:111488)
at zmi.S (workbench.desktop.main.js:4948:42054)
at zmi.Q (workbench.desktop.main.js:4948:41832)
at zmi.M (workbench.desktop.main.js:4948:40920)
at zmi.L (workbench.desktop.main.js:4948:40021)
at K9e.value (workbench.desktop.main.js:4948:38813)
at M.B (workbench.desktop.main.js:57:748)
at M.fire (workbench.desktop.main.js:57:967)
at _X.fire (workbench.desktop.main.js:2300:10356)
at l.onmessage (workbench.desktop.main.js:4993:11916)
streamResponse @ workbench.desktop.main.js:591
workbench.desktop.main.js:1918 [composer] Error in AI response: ConnectError: [resource_exhausted] Error
at yhs.$endAiConnectTransportReportError (workbench.desktop.main.js:2318:111488)
at zmi.S (workbench.desktop.main.js:4948:42054)
at zmi.Q (workbench.desktop.main.js:4948:41832)
at zmi.M (workbench.desktop.main.js:4948:40920)
at zmi.L (workbench.desktop.main.js:4948:40021)
at K9e.value (workbench.desktop.main.js:4948:38813)
at M.B (workbench.desktop.main.js:57:748)
at M.fire (workbench.desktop.main.js:57:967)
at _X.fire (workbench.desktop.main.js:2300:10356)
at l.onmessage (workbench.desktop.main.js:4993:11916)
(anonymous) @ workbench.desktop.main.js:1918
workbench.desktop.main.js:1918 [composer] Failed to get complete AI response
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:1918
6workbench.desktop.main.js:953 Error checking file existence: Error: Unable to resolve filesystem provider with relative file path ‘cursor.aisettings:cursor/aisettings’
(anonymous) @ workbench.desktop.main.js:953
workbench.desktop.main.js:965 [composer] ToolFormer: error in toolWrappedStream toolu_012dhwGqvyjv3pUbKxhgxaLr
toolWrappedStream @ workbench.desktop.main.js:965
workbench.desktop.main.js:591 ConnectError: [resource_exhausted] Error
at yhs.$endAiConnectTransportReportError (workbench.desktop.main.js:2318:111488)
at zmi.S (workbench.desktop.main.js:4948:42054)
at zmi.Q (workbench.desktop.main.js:4948:41832)
at zmi.M (workbench.desktop.main.js:4948:40920)
at zmi.L (workbench.desktop.main.js:4948:40021)
at K9e.value (workbench.desktop.main.js:4948:38813)
at M.B (workbench.desktop.main.js:57:748)
at M.fire (workbench.desktop.main.js:57:967)
at _X.fire (workbench.desktop.main.js:2300:10356)
at l.onmessage (workbench.desktop.main.js:4993:11916)
streamResponse @ workbench.desktop.main.js:591
workbench.desktop.main.js:1918 [composer] Error in AI response: ConnectError: [resource_exhausted] Error
at yhs.$endAiConnectTransportReportError (workbench.desktop.main.js:2318:111488)
at zmi.S (workbench.desktop.main.js:4948:42054)
at zmi.Q (workbench.desktop.main.js:4948:41832)
at zmi.M (workbench.desktop.main.js:4948:40920)
at zmi.L (workbench.desktop.main.js:4948:40021)
at K9e.value (workbench.desktop.main.js:4948:38813)
at M.B (workbench.desktop.main.js:57:748)
at M.fire (workbench.desktop.main.js:57:967)
at _X.fire (workbench.desktop.main.js:2300:10356)
at l.onmessage (workbench.desktop.main.js:4993:11916)
(anonymous) @ workbench.desktop.main.js:1918
workbench.desktop.main.js:1918 [composer] Failed to get complete AI response
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:1918
3workbench.desktop.main.js:953 Error checking file existence: Error: Unable to resolve filesystem provider with relative file path ‘cursor.aisettings:cursor/aisettings’

2

Any solution? i am getting same issue, also it crashes evry 5-10 minutes

3

Would you be able to share some request IDs for the failed requests when this happens? I’ve seen this a few times in the last 24hrs and will escalate it with the Cursor team. It would really help to get a few request IDs for them to debug.

4

Have you tried toggling between 3.5 and 3.7? That’s unstuck it for me a couple of times. For example: working on 3.7 and it stalls, repeat the same request on 3.5, return to 3.7 for the next one after it completes.

5

I’m having the same issue. At first, switching between 3.5 and 3.7 still worked, but now it has completely stopped.

6

Sorry, it stopped happening for a while but it’s happening again now,
Here you go @three
0f40fd10-436f-491b-a2bf-2af831c6ff90
a3b51021-743d-48cb-bbd8-95ce00b8838e
3f641b5a-ef0a-4cd1-9650-040c19cb0fae
ec1ee027-70bb-40a3-af59-ecddf8c1a48b
a7b3c340-0870-4cfc-9c5e-33694d0be32e
42e9aaf5-b5c5-48f0-8c08-2686952b76f1
Also, incase it helps, sometimes it fixes it to delete the whole conversation where it starts and then make a new one, but it doesn’t work if you don’t delete the whole conversation.

7

Thanks @oscurritos, I’ll make sure the Cursor team sees these.

8

Could you ask them if there’s any solutions that could even just temporarily fix the issue? It’s gotten a lot worse, I’ve tried everything and it’s still not working since I replied to your message, so around a day and it’s still unusable. @three