Edit failed because of a diff timeout

Describe the Bug

The parameter
“diffEditor.maxComputationTime”: 60000
does not prevent the diff execution timeout from occurring.
I am attaching a screenshot.
I have tried setting other parameters as well, but it still doesn’t work.
And in the latest version 1.3.8, the popup window that used to allow removing the timeout restrictions, which was present in version 1.2.7, no longer appears.

Steps to Reproduce

Do anything with big existing file

Expected Behavior

diffEditor.maxComputationTime

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.8 (user setup)
VSCode Version: 1.99.3
Commit: a1fa6fc7d2c2f520293aad84aaa38d091dee6fe0
Date: 2025-07-31T21:46:17.109Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

Additional Information

Nothing helps.

Does this stop you from using Cursor

No - Cursor works, but with this issue

hi @nikitayev and thank you for the bug report.

Which model are you using there?

Could you post a Request ID with privacy disabled so we can look into the details? Cursor – Getting a Request ID

hi @condor !
As sample request ID: 32c58b2a-0fe7-4afd-8aa5-0b41db9d92fe

Answer for this request ID also have diff timeout.

Also I have many many many answers from server:

Request ID: f76e2dac-cc51-48f5-8205-eb6b737668b2
{“error”:“ERROR_UNAUTHORIZED”,“details”:{“title”:“Unauthorized request.”,“detail”:“The provider refused to serve this request based on the content”,“isRetryable”:false,“additionalInfo”:{},“buttons”:},“isExpected”:true}
ConnectError: [unauthenticated] Error
at BWa.$endAiConnectTransportReportError (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4846:224431)
at wsr.S (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:495:17762)
at wsr.Q (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:495:17540)
at wsr.M (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:495:16628)
at wsr.L (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:495:15729)
at Wyt.value (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:495:14521)
at we.B (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:2398)
at we.fire (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:2617)
at Ynt.fire (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4833:10379)
at u.onmessage (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7043:13881)

I updated to:

Version: 1.3.9 (user setup)
VSCode Version: 1.99.3
Commit: 54c27320fab08c9f5dd5873f07fca101f7a3e070
Date: 2025-08-01T20:19:30.453Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

Same thing happeneding for big code edit

1 Like