Cannot start cloud agent

[Anthony_Chan]

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

i tried triggering my cloud agent but it doesn’t work. Tried a few times with new agent but still stuck

Agent: bc-b494fd3b-0079-4525-a984-4c1bedfca359
Symptom: [install:] completes successfully, then agent stuck in CREATING
Local logs: EXEC_DAEMON_NOT_READY (earlier runs), then
“Cannot resolve authority” + “Extension host (Remote) terminated unexpectedly”
after TCP connect succeeds (19:53 HK time)
Repo: https://github.com/tchoany/liturgy_skills
Environment: dashboard update script installs antiword + libreoffice-impress-nogui + pip

Steps to Reproduce

create new cloud agent

Expected Behavior

can start run and call through cursor SDK

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.7.27 (Universal)
VS Code Extension API: 1.105.1
Commit: e48ee6102a199492b0c9964699bf011886708ba0
Date: 2026-06-10T01:46:16.942Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the detailed report with logs and the bcId. It helped us spot the issue right away.

This isn’t on your side and it’s not related to your custom environment. We currently have a known infra issue with starting cloud agents. The pod gets created, but the exec-daemon on the VM isn’t ready in time, so you see EXEC_DAEMON_NOT_READY, then Cannot resolve authority, and then the remote extension host crashes. This is on us and we’re tracking it, but I can’t share an ETA for a fix yet.

What you can do right now:

• Try starting it again. Agents often come up after a few attempts once the scheduler lands a healthy pod. In a similar case it started working after about an hour.
• If the cluster is unstable and you need it urgently, run the task locally for now.

The same symptom is discussed here: Cloud agent stuck at "Running start script": noVNC keeps running in the foreground. Subscribe there if you want to track updates. I’ll post here once we have an update.