Cloud Agent stopped running and could not be restored

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Cloud Agent stopped running and could not be restored.

https://cursor.com/agents/bc-019f834e-8297-7ecb-927e-e44e708e9be1

Steps to Reproduce

Open this cloud agent and continue

Operating System

MacOS

Version Information

Cloud Agent Web

Does this stop you from using Cursor

Yes - Cursor is unusable

Hi @harrisonhou Sorry about this! I reviewed the run and found that the Cloud Agent environment ran out of memory while many compiler processes were running concurrently, causing it to stop responding.

A fresh environment later began provisioning, but a Stop or Pause action canceled that recovery.

To restart safely:

  1. Reopen the same agent and send a new follow-up message.
  2. Allow several minutes for provisioning without pressing Stop.
  3. Rerun the build with bounded parallelism. When retrying, reduce the build’s parallelism or worker count. If you share the build command, we can help identify the appropriate setting.

Your conversation history should remain available. However, files stored only in the failed environment and not committed or saved elsewhere may not be recoverable.

Let us know if you keep hitting these issues consistently and we can explore additional troubleshooting measures.

I followed the instructions(restart safely), but it didn’t work

Hi @harrisonhou I checked the same agent again after your message. The first retry still reached the failed environment, but a replacement environment then came online successfully, and I can see the agent completing later turns.

This recovery completed after you posted. Can you confirm whether the agent is working for you now? If not, please let us know and we can take another look!

It’s running normally now, but creating a new chat results in an error.

Request ID: 6f3a174f-5da8-430a-910f-fa659cfb4622{"error":"ERROR_EXTENSION_HOST_TIMEOUT","details":{"title":"Agent Execution Timed Out","detail":"The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.","isRetryable":false,"shouldShowImmediateError":true,"additionalInfo":{},"buttons":[{"label":"Reload Window","reloadWindow":{}}],"planChoices":}}The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.Agent Execution Timed Out [deadline_exceeded]ConnectError: [deadline_exceeded] Agent Execution Timed Outat QKm (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9409:35096)at Nli.waitForProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9409:40316)at async Pjl._waitForPushRequestContextProviderRegistration (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:17874:4327)at async qmt (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8289:11983)at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:17874:8999at async qmt (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:8289:11983)at async Pjl.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:17874:8896)at async Pjl.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:17874:24972)at async _8e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:9478:2511)