Cloud Agent chats disappeared and requests are stuck

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

My Cursor cloud chat history suddenly stopped appearing. I normally see the same chats in both Cursor desktop and Cursor web.

At the same time, Cloud Agent requests began failing with “[internal] internal error.” I reproduced the failures using multiple models.

Later, the chat history reappeared, but new Cloud Agent requests became stuck indefinitely on “Planning next moves” with no visible option to stop the run.

Cursor’s status page is currently reporting an active service degradation / major outage affecting Cloud Agents and Automations.

Steps to Reproduce

  1. Open Cursor desktop or Cursor web while signed into my account.
  2. Open an existing Cloud Agent conversation.
  3. Send a normal Agent request.
  4. The request either:
    • returns “[internal] internal error”, or
    • becomes stuck on “Planning next moves” for several minutes with no Stop option.
  5. During the same incident, my entire cloud chat list also temporarily disappeared from Cursor web and later reappeared.

I tested in the normal browser session, after a hard refresh, and in an incognito/private browser session. The missing-chat behavior was the same.

I also reproduced Agent failures using more than one model.

Expected Behavior

My existing Cloud Agent conversations should remain visible and synchronized between Cursor desktop and Cursor web.

When I submit an Agent request, the Agent should either begin processing normally or return a clear recoverable error. It should not remain indefinitely stuck on “Planning next moves,” and an active request should provide a way to stop/cancel it.

Operating System

Windows 10/11

Version Information

Version: 3.20.21 (user setup)
VS Code Extension API: 1.128.0
Commit: f09fca384ceca23f7bf21f9c23655b162641d740
Date: 2026-09-13T19:02:51.781Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Cursor Grok 4.6 Medium

I also reproduced the failure after switching models, including Claude Opus 5 Medium, so this does not appear to be specific to one model.

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hi @David_Haasch Thanks for the post and sorry for the inconvenience. What you’re seeing lines up with the Cloud Agents and Automations service degradation currently posted on status.cursor.com, including the chat list dropping out and then returning, so nothing on your end needs fixing.

Local agents in the editor aren’t affected if you need to keep working, and runs stuck on “Planning next moves” are worth resending once things recover rather than waiting on them. You can subscribe to email updates here: https://status.cursor.com/ to be notified when the issue is resolved.