Composer stops editing prematurely

[qubit000]

Composer starts editing then stops during ‘Generating…’ process before completing the edits. Numerous requests to finish updates repeat cycle of starting then stopping edits prematurely

Is this a known issue and any workarounds?

[deanrie]

Hey, which model are you using? Does this also happen in a new Composer session?

[qubit000]

Claude, Deepseek R1, 4.0, o3-mini and still happens even after opening new Composer

[deanrie]

Can you open the DevTools panel and check if there are any errors?

[webdo]

Also having this issue, either it just hangs on generating, or I get the same thing as OP.

I restarted cursor and created a new composer session, same issue, here are the complete logs:

[MCPService] Starting server initialization
workbench.desktop.main.js:1015 [MCPService] Getting servers: []
workbench.desktop.main.js:1015 [MCPService] Found servers on startup: []
workbench.desktop.main.js:1015 [MCPService] Getting servers: []
workbench.desktop.main.js:1015 [MCPService] Getting servers: []
workbench.desktop.main.js:1378 [Extension Host] (node:1504) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `Cursor --trace-deprecation ...` to show where the warning was created)
Jur @ workbench.desktop.main.js:1378
$logExtensionHostMessage @ workbench.desktop.main.js:1378
S @ workbench.desktop.main.js:4870
Q @ workbench.desktop.main.js:4870
M @ workbench.desktop.main.js:4870
L @ workbench.desktop.main.js:4870
(anonymous) @ workbench.desktop.main.js:4870
B @ workbench.desktop.main.js:59
fire @ workbench.desktop.main.js:59
fire @ workbench.desktop.main.js:1394
l.onmessage @ workbench.desktop.main.js:4915
vscode-file://vscode-app/c:/Users/Webdo/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/services/extensions/worker/webWorkerExtensionHostIframe.html?&vscodeWebWorkerExtHostId=b4fc9895-2cbf-4871-957f-a76aac38688d:1 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
workbench.desktop.main.js:980 Failed to perform semantic search: Error: Semantic search timeout
    at workbench.desktop.main.js:980:211
getContextFromSemanticSearch @ workbench.desktop.main.js:980
workbench.desktop.main.js:4851 
        
        
       GET https://www.vscode-unpkg.net/_gallery/jeanp413/open-remote-ssh/latest 404 (Not Found)
iuo @ workbench.desktop.main.js:4851
(anonymous) @ workbench.desktop.main.js:4851
c @ workbench.desktop.main.js:667
request @ workbench.desktop.main.js:4851
K @ workbench.desktop.main.js:694
await in K
(anonymous) @ workbench.desktop.main.js:694
E @ workbench.desktop.main.js:694
getExtensions @ workbench.desktop.main.js:694
checkForUpdates @ workbench.desktop.main.js:4136
await in checkForUpdates
(anonymous) @ workbench.desktop.main.js:4136
queue @ workbench.desktop.main.js:60
(anonymous) @ workbench.desktop.main.js:60
(anonymous) @ workbench.desktop.main.js:60
Promise.then
trigger @ workbench.desktop.main.js:60
trigger @ workbench.desktop.main.js:60
Ob @ workbench.desktop.main.js:4136
rb @ workbench.desktop.main.js:4136
qb @ workbench.desktop.main.js:4136
workbench.desktop.main.js:1015 [MCPService] Getting servers: []
workbench.desktop.main.js:1015 [MCPService] No connected servers found. Server statuses: 

I still have Fast request so I don’t think It’s a slow queue issue either.

Sometimes after trying for a while it will go through.

Edit added details and picture of logs for clarity

[qubit000]

no errors

[brettswift]

I find this is mostly happening when generating README / markdown documentation. I suspect it has something to do with code blocks and backticks, but I’m not entirely sure.

This has been happening for a few months now, back to whatever version that was released in about December when I started to notice this.

I’ve had success getting it to work by giving it these prompts, which support my theory:

1. Prompt → You are outputting text into the side panel. this is causing your workflow to stop. i’m not sure how you can output the text without the side panel. maybe you could just do bit by bit of the file and write the readme file … say a tiny section by section, and then ask me if i want to continue to write the rest. you may have more success that way.
2. the bot asks to continue several iterations
3. fails at the code block
4. Prompt → ok that is what broke it. don’t put the code blocks around the examples for now, just do raw code.. after you have that in we will add the code blocks.
5. I just keep typing “continue” as it gets through bit by bit.