Composer is not working

Hi, thanks for reporting an issue with Cursor.

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, please check this box.
on

Describe the Bug

The composer stopped working. Not generating anything.
Was working an hour ago

Steps to Reproduce

Any usage in the composer

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.43.6
VSCode version: 1.93.1

Additional Information

Taken from dev tools console log:

workbench.desktop.main.js:433 Error
at f.create (workbench.desktop.main.js:433:58393)
at y.q [as onDidChange] (workbench.desktop.main.js:436:1100)
at new d (workbench.desktop.main.js:1197:8845)
at c.o (workbench.desktop.main.js:1136:1609)
at c.createInstance (workbench.desktop.main.js:1136:1101)
at new J (workbench.desktop.main.js:1270:7875)
at c.o (workbench.desktop.main.js:1136:1609)
at c.createInstance (workbench.desktop.main.js:1136:1101)
at b.I (workbench.desktop.main.js:1283:1976)
at b.createModel (workbench.desktop.main.js:1284:963)
at L (workbench.desktop.main.js:2567:25450)
at workbench.desktop.main.js:2983:6914
at Proxy.forEach ()
at workbench.desktop.main.js:2983:6812
at Array.forEach ()
at B.composerWasLoadedHook (workbench.desktop.main.js:2983:6798)
at $.pushComposer (workbench.desktop.main.js:2572:13639)
at $.getHandle (workbench.desktop.main.js:2572:14768)
workbench.desktop.main.js:433 [1b5] potential listener LEAK detected, having 772 listeners already. MOST frequent listener (288):
workbench.desktop.main.js:433 Error
at f.create (workbench.desktop.main.js:433:58393)
at $.q [as onDidChange] (workbench.desktop.main.js:436:1100)
at new Q (workbench.desktop.main.js:1287:26542)
at new X (workbench.desktop.main.js:1285:12051)
at new h (workbench.desktop.main.js:2099:35608)
at c.o (workbench.desktop.main.js:1136:1609)
at c.createInstance (workbench.desktop.main.js:1136:1101)
at L (workbench.desktop.main.js:2567:25229)
at workbench.desktop.main.js:2983:6914
at Proxy.forEach ()
at workbench.desktop.main.js:2983:6812
at Array.forEach ()
at B.composerWasLoadedHook (workbench.desktop.main.js:2983:6798)
at $.pushComposer (workbench.desktop.main.js:2572:13639)
at $.getHandle (workbench.desktop.main.js:2572:14768)
workbench.desktop.main.js:3019 [composer] ToolFormer: error in toolWrappedStream undefined
workbench.desktop.main.js:3019 ConnectError: [resource_exhausted] Error
at U.$endAiConnectTransportReportError (workbench.desktop.main.js:3856:11332)
at T.S (workbench.desktop.main.js:2447:14845)
at T.Q (workbench.desktop.main.js:2447:14611)
at T.M (workbench.desktop.main.js:2447:13644)
at T.L (workbench.desktop.main.js:2447:12479)
at y.value (workbench.desktop.main.js:2447:11174)
at d.B (workbench.desktop.main.js:438:732)
at d.fire (workbench.desktop.main.js:438:949)
at s.fire (workbench.desktop.main.js:1121:14824)
at G.onmessage (workbench.desktop.main.js:2463:8227)
workbench.desktop.main.js:3019 [composer] Error in AI response: ConnectError: [resource_exhausted] Error
at U.$endAiConnectTransportReportError (workbench.desktop.main.js:3856:11332)
at T.S (workbench.desktop.main.js:2447:14845)
at T.Q (workbench.desktop.main.js:2447:14611)
at T.M (workbench.desktop.main.js:2447:13644)
at T.L (workbench.desktop.main.js:2447:12479)
at y.value (workbench.desktop.main.js:2447:11174)
at d.B (workbench.desktop.main.js:438:732)
at d.fire (workbench.desktop.main.js:438:949)
at s.fire (workbench.desktop.main.js:1121:14824)
at G.onmessage (workbench.desktop.main.js:2463:8227)
workbench.desktop.main.js:3019 [composer] Failed to get complete AI response after 0 attempts

Does this stop you from using Cursor

Yes - Cursor is unusable

Ok just did a ctrl+n as I saw suggested in another similar topic.
that seems to activate again the composer functionality.

Hey, thanks for reporting this!

We should have a fix for this in our v0.44 release which you should auto-update to very soon.
Alternatively, you can manually update to it now by downloading the latest release from Downloads | Cursor - The AI Code Editor

As you have found, starting a new chat or composer session is a good workaround in the older versions.