I’ve been using Cursor for a few months, and then in the last few days it stopped working. When I do a new chat, it goes from Summarizing chat → Chat summarized → planning next steps → Internal error occurred. Here’s the output from the error:
Request ID: d329da52-720c-4581-bcb3-1bfe7761d53c
[internal] Failed to run step, exceeded max retries
LTe: [internal] Failed to run step, exceeded max retries
at kmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
at $mf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at ova.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34193:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34242:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34242:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async $i (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32991:3808)
I’ve logged out and back in. Checked network connectivity in the Corsor settings (everything worked), and even ran “sudo rm -rf ~/Library/Application\ Support/Cursor and rm -f ~/.cursor.json”. I’ve also checked for updates and still see this on the latest version (as of this email). I also opted into the new pricing, thinking that might help, but it didn’t. Can you move me back to the old pricing?
Hey, thanks for the report. I can see you’ve already tried the main workarounds.
This “Failed to run step, exceeded max retries” error is something the team is investigating. It’s different from the common SSL/HTTP2 errors they’re currently fixing.
It should prompt you to downgrade to the stable version
The Early Access track (your version 2.4.26) can sometimes include regressions that aren’t in the Default track. Since this started about a week ago, it might be related to a recent EA update.
I also tried changing the network settings from HTTP/2 to HTTP/1.1. I was able to successfully run the network diagnostics on that page, but the agent chat still doesn’t work. Here’s my latest erroneous request:
Request ID: 444a405e-d9fe-458b-93de-5933cd9cece7
[internal] Failed to run step, exceeded max retries
LTe: [internal] Failed to run step, exceeded max retries
at Gmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38348)
at Hmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37251)
at rpf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at fva.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async Hyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34196:57047)
at async Zpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:7695)
at async Zpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Ei (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32994:3808)
I’ve tried tethering to my phone, which didn’t help, so it’s not an ISP issue. My work laptop with Cursor does work, so it’s not a local network issue. I do not have a VPN set up on the laptop this is happening on. I also tried completely removing the Cursor installation (via Homebrew) and reinstalling it, to no avail.
I can see you’ve already tried all the standard workarounds, so this clearly isn’t a network or proxy issue.
I sent both Request IDs to the team for a deeper investigation. Since it works on your work laptop, it’s most likely something specific to the account or a particular machine on the backend.
A couple quick questions while the team is looking:
Are you using the same Cursor account on the work laptop?
If yes, try signing out on the work laptop and then test on the affected one.
I’ll update you as soon as I hear back from the team.
@Tristan_Burch We can’t sort through individual billing issues here in the forum. If you have questions about this, please reach out to [email protected]!