When the parent Bot looks idle while Cloud Agents are still running

After a parent Bot hands work to a Cloud Agent, the parent chat goes quiet on purpose until that agent finishes. The parent is woken automatically at completion. A long job can look idle in chat even while the Cloud Agent is still running. Staff (Colin, Sep 17, 2026) on forum 172009.

Delegated Cloud Agents are ordinary Cursor cloud agents. Cursor is improving in-flight visibility in the parent conversation; until that lands, use the steps below.

Watch the Cloud Agent without polling chat

1. Open cursor.com/agents (or the Cloud Agents view in the Cursor desktop app).
2. Find the agent the Bot launched (status shows running, finished, or errored).
3. Leave that page open if you want live progress while the parent Bot stays quiet.

Keep Running / Done visible in the parent chat

1. When the parent Bot mentions a delegated agent, ask it to attach the agent card.
2. The card shows Running / Done inline in the parent conversation so you do not have to ask “is it still working?” every few minutes.
3. When the agent finishes, the parent wakes on its own and continues — you do not need to poke it just to resume the handoff.

Pitfalls

• Do not treat a quiet parent chat as a stalled workflow while cursor.com/agents still shows the child Running.
• Do not invent a parent tool that pulls binary artifacts (screenshots, large files) out of the child Cloud Agent VM into the parent chat — that path is not documented; status callbacks and agent cards are.
• ResourceExhausted / vttablet transaction pool launch failures are a different issue (infra / capacity); they are not fixed by watching agents or attaching cards.