Agents errors over and over again last two days

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Internal subagents (source: internal) appear in the Agents UI with valid bc-* IDs and “Loading chat…”, but fullscreen returns “Server couldn’t find it, or it was deleted.” No events, no transcript, status stuck RUNNING with branchName: null. Example: bc-4f8fd8eb-f495-5d30-927e-382c38dd08ec, parent bc-5e5be4ce-f69f-46f0-9e7c-ac3a4eb342b9.

Steps to Reproduce

plan mode and release sub agents… keep failing on me, all my rules and agents files are all default nothing extra customized

Expected Behavior

subagents finish my building and i can view their actual progress before and after the fact

Operating System

MacOS

Version Information

Using Cursor agents window on MacOs and Windows 11

For AI issues: which model did you use?

Composer & Grok

For AI issues: add Request ID with privacy disabled

Parent agent bc-5e5be4ce-f69f-46f0-9e7c-ac3a4eb342b9 dispatches Task subagents. UI lists them with bc-* IDs (e.g. bc-4f8fd8eb-f495-5d30-927e-382c38dd08ec, “P1b merge baseline into mega”). Clicking shows “Loading chat…” then fullscreen: “Server couldn’t find it, or it was deleted.” API shows subagents as source: internal, branchName: null, 0 events, no transcript, stuck RUNNING. Parent (source: desktop) works. Please either hide internal runs from openable chat UI or provide transcript + correct status.

Additional Information

Parent agent bc-5e5be4ce-f69f-46f0-9e7c-ac3a4eb342b9 dispatches Task subagents. UI lists them with bc-* IDs (e.g. bc-4f8fd8eb-f495-5d30-927e-382c38dd08ec, “P1b merge baseline into mega”). Clicking shows “Loading chat…” then fullscreen: “Server couldn’t find it, or it was deleted.” API shows subagents as source: internal, branchName: null, 0 events, no transcript, stuck RUNNING. Parent (source: desktop) works. Please either hide internal runs from openable chat UI or provide transcript + correct status.

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hey @maxnaid,
Two things going on:

  1. The repeated errors the last couple of days were a service-side issue on our end (not your setup or rules), and we’ve addressed it - give it another go, should be smoother now.
  2. The internal entries that won’t open are a display issue, not lost work: those subagents actually run fine and feed their results back into the parent agent’s chat. Hiding them from the openable list (what you suggested) is the direction we’re heading.

For now:

  • Watch subagent progress from the Task cards inside the parent agent’s chat (the entry that opens fine).
  • Developer: Reload Window (Cmd/Ctrl+Shift+P) clears the stray entries that won’t open.

I’ll post when there’s an update. If the errors come back after retrying, drop a fresh request ID (privacy off) and I’ll dig in.