I renewed my subscription, and then I found out that the cursor had an update, so I updated it last night, after the update is done till now its not working and just throwing errors when i try to do anything
An unexpected error occurred. Request ID: f9969f7f-c13a-4780-a88d-492959080580
For AI issues: add Request ID with privacy disabled
Request ID: f9969f7f-c13a-4780-a88d-492959080580
An unexpected error occurred.
No resource accessor found for composer: 447cad05-d300-4f98-a786-4407bc30e633
Error: No resource accessor found for composer: 447cad05-d300-4f98-a786-4407bc30e633
at Pjl.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:17874:6298)
at Pjl.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:17874:24983)
at _8e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9478:828)
at async jZm.submitMessage (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:9432:40379)
at async vzk.submitMessage (vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:19410:23734)
at async vscode-file://vscode-app/c:/Users/HP/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:17489:200271
Hey, thanks for the detailed report and stack trace. It helped identify the issue right away. This is a known bug: after an update, the chat or agent loses its link to the project folder, and then any request fails instantly with No resource accessor found for composer. It’s not related to your subscription or model. The error happens on the client before the request is sent, which is why it looks like no model works.
What usually fixes it:
Ctrl+Shift+P → Reload Window
If that doesn’t help, close and reopen the project folder via File > Open Folder. Make sure you open the folder, not an empty window.
If you’re using a .code-workspace file, check that the folders array in it isn’t empty.
As a temporary workaround, start a new agent chat only after the folder is opened correctly.
No need to reinstall or change anything about your subscription.
We’re tracking this bug, but there’s no exact ETA for a fix yet. If the workaround doesn’t help, reply and we’ll dig in further.
the workaround isnt working as well, ive tried everything that you listed, moreover, i will also wanna add that!
i cannot open it as a folder as well becuase its not giving me option
also to add, even if i try to run a new agent!for something else
thats is also not working!
idk how to fix this issue!
kindly resolve asap
Got it, the basic steps didn’t work, so let’s try a different angle. It looks like you’re currently using the Agent Window layout, and this bug shows up there. In the normal Editor layout, chat usually works.
Try these in order:
Fully close Cursor. On Windows, open Task Manager and make sure there are no Cursor processes left. End them if they’re still running, then start Cursor again.
Switch from Agent Window to the normal Editor layout. You can do this from the window itself. Cursor lets you keep both modes and switch between them.
In the Editor window, open your project using Ctrl+O Open Folder. Open the actual project folder, not an empty window. The option might not show in the File menu, so use the shortcut.
Once the folder is open, start a new chat.
A couple quick questions so we can dig deeper if this doesn’t help:
Are you opening the project as a normal folder or via a .code-workspace file? If it’s .code-workspace, check that the folders array inside isn’t empty.
After the steps above, is it the same error No resource accessor found for composer, or did anything change?
Glad to see new chats are working in the Editor window. From the screenshot, the issue with the old chat is clear: in stylegen2.code-workspace, the folders array is empty ("folders": []). Old chats are pinned to that workspace, and since it has no folders, it can’t resolve. Any request from that chat fails instantly with the same error.
How to fix it:
Either edit the .code-workspace file yourself: set folders to your project path, for example:
{
"folders": [
{ "path": "." }
]
}
(or use the full path to the project folder instead of "."). Save it, then run Ctrl+Shift+P → Reload Window.
Or проще: open the project folder directly using Ctrl+O Open Folder, instead of opening the .code-workspace file.
After that, the workspace should resolve and the old chat should come back. If that specific old chat still won’t send requests (sometimes the binding gets permanently stuck), the history is still readable. You can just copy it into a new chat opened in a correctly loaded folder.
