Calm down man, it’ll be alright. These things happen and the team is working on it. In the meantime you can download version 2.4 from here Cursor · Download
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
agent/chat not responding at all
Steps to Reproduce
even if used early release/latest, the issue still not gone, same. just writing anything, opening new chats doesn’t help too
Screenshots / Screen Recordings
Operating System
Linux
Version Information
Version: 2.5.15
VSCode Version: 1.105.1
Commit: 578fd4ade188ac623bd692156274a32fd68eaa80
Date: 2026-02-16T05:45:39.627Z
Build Type: Stable
Release Track: Early Access
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.14.0-37-generic
For AI issues: add Request ID with privacy disabled
Request ID: 2252b906-f241-44f6-9616-3cf4461cc3b5
Failed to get request context: error
Error: Failed to get request context: error
at uOl.buildComposerRequestContext (vscode-file://vscode-app/tmp/.mount_cursor2okX2R/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44404:3889)
at async uOl.streamFromAgentBackend (vscode-file://vscode-app/tmp/.mount_cursor2okX2R/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44404:5384)
at async uOl.getAgentStreamResponse (vscode-file://vscode-app/tmp/.mount_cursor2okX2R/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44404:9837)
at async bLe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/tmp/.mount_cursor2okX2R/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32178:15752)
at async zs (vscode-file://vscode-app/tmp/.mount_cursor2okX2R/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43411:4782)
Additional Information
all models, same. not working, all networks passing
Does this stop you from using Cursor
Yes - Cursor is unusable
This error looks identical to mine. I’m on Mac, apart from that my setup is pretty similar.
sh1t, how can u calm down when ur whole work depends on this app u payed for but it is not working
Are you able to downgrade versions? That should allow you to continue working. I’ve downgraded to 2.4 and have been able to progress. You can give that a try here Cursor · Download
It’s the same problem for me. Exactly the same.
Same issue here …. but i can wait if its going to fix in a hour…
Same issue. Interestingly, no error as long as no workspace folder is loaded. Also cli still works.
Getting the same issue
Failed to get request context: error
Error: Failed to get request context: error
at uOl.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44404:3889)
at async uOl.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44404:5384)
at async uOl.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44404:9837)
at async bLe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32178:15752)
Same:
Failed to get request context: error
Error: Failed to get request context: error
at uOl.buildComposerRequestContext (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44404:3889)
at async uOl.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44404:5384)
at async uOl.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44404:9837)
at async bLe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/micha/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32178:15752)
2.5.16 is rolling out to affected users (those on 2.5.15) and should fix the issue. Sorry again for the disruption!
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
