Cloud agent transcript empty + migrate fails: no conversation state (bc-757e523c…)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cloud agent for repo Tmanfluff/CreativeSync-Prod (“CreativeSync-Prod architecture brief”) shows an empty transcript on cursor.com/agents after ~24h. Sidebar/title load; main pane is blank. Reload, single-window-only, desktop vs web — no change.

Steps to Reproduce

  1. Open https://cursor.com/agents/bc-757e523c-6143-5bd3-b323-08a609447b62 (or select chat from sidebar)
  2. Observe blank transcript
  3. Attempt Move to local → error above

Expected Behavior

Transcript visible; cloud→local migration (or clear error if state truly missing)

Operating System

MacOS

Version Information

Version: 3.21.16
VS Code Extension API: 1.128.0
Commit: 8ae78e8eee1e63479c7e0504b664bc0a80c68000
Date: 2026-09-19T06:43:22.276Z
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: Darwin arm64 25.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Tyler_Miller, thanks for the detailed report.

I looked into that agent. It was created when your Grok Bot handed the “CreativeSync-Prod architecture brief” task off to a cloud agent, but the cloud agent never actually started running on our side. Because it never ran, there is no conversation to display and nothing for Move to local to transfer, which is why you see a blank pane and the “no conversation state” message. I’ve flagged this to the team so a run that fails to start shows a clear error instead of an empty transcript.

To clean it up, open cursor.com/agents, hover over the “CreativeSync-Prod architecture brief” entry in the sidebar and choose Archive. Then re-run the task, either by asking your Grok Bot again or by starting the cloud agent directly from cursor.com/agents or the Agents window in Cursor.

If it happens again, please send me the agent link (the bc-… URL) and roughly when you launched it, and I’ll take another look.

Legend! Thank you Colin, that resolved it.