Agentic Composer breaking for Jest tests

Thanks for reporting a bug you have found in Cursor!
Please add the following info to help us diagnose your issue:

:white_check_mark: Check the forum to ensure the issue hasn’t been reported already
Checked

:lady_beetle: Provide a clear description of the bug
When I ask composer to create a jest test for me while also providing other jest tests as context I see the “forever loader” issue, where the product is stuck in a never ending thinking loop. The exact same prompt works in the “Chat” window.

:arrows_counterclockwise: Explain how to reproduce the bug (if known)

:camera: Attach screenshots or recordings (e.g., .jpg, .png, .mp4).

:computer: Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Version: 0.44.11

VSCode Version: 1.93.1

Commit: fe574d0820377383143b2ea26aa6ae28b3425220

Date: 2025-01-03T07:59:06.361Z (2 wks ago)

Electron: 30.5.1

Chromium: 124.0.6367.243

Node.js: 20.16.0

V8: 12.4.254.20-electron.0

OS: Darwin arm64 23.6.0
:no_entry_sign: Tell us if the issue stops you from using Cursor.
It does completely break my ability to use Cursor for Jest code.

LOGS
2workbench.desktop.main.js:3542 [Extension Host] jest-editor-support parser returned error TypeError: Cannot read properties of undefined (reading ‘flatMap’)
at t.JestRunnerCodeLensProvider. (/Users/nzozaya@sitetracker.com/.cursor/extensions/firsttris.vscode-jest-runner-0.4.74/src/JestRunnerCodeLensProvider.ts:69:15)
at Generator.next ()
at /Users/nzozaya@sitetracker.com/.cursor/extensions/firsttris.vscode-jest-runner-0.4.74/dist/extension.js:1:61375
at new Promise ()
at fileName (/Users/nzozaya@sitetracker.com/.cursor/extensions/firsttris.vscode-jest-runner-0.4.74/dist/extension.js:1:61120)
at t.JestRunnerCodeLensProvider.provideCodeLenses (/Users/nzozaya@sitetracker.com/.cursor/extensions/firsttris.vscode-jest-runner-0.4.74/src/JestRunnerCodeLensProvider.ts:63:43)
at m.provideCodeLenses (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:192:104478)
at /Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:192:137928
at Ze.s (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:192:136674)
at Ze.$provideCodeLenses (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:192:137916)
at R.S (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:189:5984)
at R.Q (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:189:5750)
at R.M (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:189:4732)
at R.L (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:189:3603)
at a.value (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:189:2298)
at o.B (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:113:734)
at o.fire (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:113:951)
at u.fire (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:135:14600)
at a.value (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:215:8666)
at o.B (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:113:734)
at o.fire (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:113:951)
at u.fire (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:135:14600)
at MessagePortMain. (/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:215:6792)
at MessagePortMain.emit (node:events:519:28)
at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:2619)
at Object.callbackTrampoline (node:internal/async_hooks:130:17)
console.error @ workbench.desktop.main.js:3542
d @ workbench.desktop.main.js:530
$logExtensionHostMessage @ workbench.desktop.main.js:2950
S @ workbench.desktop.main.js:2950
Q @ workbench.desktop.main.js:2950
M @ workbench.desktop.main.js:2950
L @ workbench.desktop.main.js:2950
(anonymous) @ workbench.desktop.main.js:2950
B @ workbench.desktop.main.js:470
fire @ workbench.desktop.main.js:470
fire @ workbench.desktop.main.js:1153
G.onmessage @ workbench.desktop.main.js:3000
workbench.desktop.main.js:530

Hey, from the logs, it looks like the vscode-jest-runner extension may not have full compatibility with Cursor yet!

However, that shouldn’t stop the composer from executing properly.
Can you try to start a new composer, and try the same prompt again to see if that works?

Yes, trying now.

1 Like

Alternatively, try to disable that extension, restart Cursor, and see if that helps, as there is a small change the extension is actually breaking Cursor enough to stop it from submitting prompts correctly.

Same result in new Composer chat - loom recording https://www.loom.com/share/d144120fbc7a4a35b3fbe78c1fd92bea?sid=72de82a9-74c2-4a7d-a76b-f9f907e2c0f8

Trying to disable the extension now.

Separate but now related issue is that I can’t see my extensions in Cursor.

They are showing in VSCode:

l

Strange. I’ll try to dig into why that’s occurring but it’s been that way for a while now.

Trying the CLI

Uninstalled via cli, trying the prompt again.

That looks like it worked!

Glad you’ve seemed to resolve it!