Cloud Agents crash after a few tool calls (possible Cursor hooks / todolist issue)

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

All Cloud Agents crash after executing a few tool calls. After some tool calls, the Cloud Agent stops and disappears from the Cursor web app.

A couple possible explanations:

  • We introduced Cursor hooks, and now the Background Agents wont run somehow due to the new Cursor hooks.
  • The background agents are all writing todolists, and perhaps updating todolists causes the agent to crash

A couple useful pieces of information:

  • The virtual machine cannot be found. We cannot “Open Virtual Machine” as we get a “Failed to connect to the remote extension host server (Error: [unknown] undefined)”
  • Sending “It looks like you’ve been interrupted. Please continue” messages do not restore the Cloud Agent, and no additional tool calls are triggered from these messages. They actually disappear after refreshing the page when sent in the Cursor web app.

Steps to Reproduce

  1. Launch a Cloud Agent (e.g., background agent on GitHub/Slack/Web/Linear).
  2. Let the agent run through several tool calls.
  3. Observe that after a few tool calls the agent crashes and disappears from the Cursor web interface.
  4. Attempt to open the associated virtual machine via “Open Virtual Machine”. The system returns an error: “Failed to connect to the remote extension host server (Error: [unknown] undefined)”.
  5. Try to respond to the “It looks like you’ve been interrupted. Please continue” prompt that appears. Notice that the message disappears upon sending and refreshing the page, and the agent does not resume or make additional tool calls.
  6. In cases where the background agent writes or updates todolists using Cursor hooks, note that the agent still crashes.

These steps occur consistently and block normal operation.

Expected Behavior

Cloud Agents should continue processing tool calls and remain active until tasks are completed.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 23.3.0

For AI issues: which model did you use?

GPT-5 Codex High

For AI issues: add Request ID with privacy disabled

bc-c3e20945-2877-4028-8d5a-4b1133f240cd
bc-d981a604-6b2a-49e3-b46a-d05dadf11e64
bc-3a03a817-a1ec-4744-b435-4098c86a2517

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This is a known issue that has already been passed to the engineering team.

The team is currently investigating cases where Cloud Agents hit resource limits during long-running sessions. Your notes about the agent crashing when using Cursor hooks and updating the todolist are very helpful, and I’ll make sure they are added to the ticket.

Your Request IDs will help the team debug this specific case more accurately.

1 Like

@deanrie, I see you guys have hidden my related bug report - Cloud Agents crash with "We encountered an internal error - please try again in a moment.". Confirming with you all that this is still a problem for us.

Your post is not hidden - the team is investigating this issue. Both of your reports are being tracked.

Thanks for the detailed information you’ve provided.

Okay, this is what I meant:

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.