Request ID: 841107d5-3a82-4df6-924e-b640ee46f4c5
The agent stopped because of an internal error. Try again.
RetriableError: The agent stopped because of an internal error. Try again.
at __b (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9085:128032)
at fGo._executeTurn (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9085:150068)
at async fGo.executeTurn (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9085:138335)
at async Sme.runAgentLoop (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9080:17083)
at async PRa.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:19013:24590)
at async PRa.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:19013:49924)
at async $Ie._submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9063:5198)
at async $Ie.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9058:90558)
Steps to Reproduce
After every prompt I get “The agent stopped because of an internal error. Try again.”
This doesn’t look like it’s caused by the update. Your requests reach our servers and get answered normally, but Cursor then fails to save the chat to its local database on your machine, which reports it as damaged (“database disk image is malformed”), and the agent stops with that generic error. Cursor doesn’t repair that database on its own yet, so restarting usually won’t clear it.
First try a brand-new chat. If that fails the same way, resetting the local database should help:
Quit Cursor completely (check Task Manager that no Cursor processes are left).
Open %APPDATA%\Cursor\User\globalStorage in File Explorer.
Copy state.vscdb (and state.vscdb-wal / state.vscdb-shm if present) to another folder as a backup.
Rename the originals, for example to state.vscdb.old.
Start Cursor, sign in again if asked, and send a prompt in a new chat.
Your local chat history won’t show after this, but it stays in the backup copy. Let me know whether prompts go through after the reset.
Fair, status.x.ai is just where status.cursor.com redirects now, so it covers Cursor too. Sounds like this one was the local chat database, not an outage, so glad Colin’s reset fixed it.