Skip to main content
Use the status on the Cloud Agent’s Overview as the source of truth for its remote runtime. A successful button click means Clawdi accepted an action; it does not mean every transition or tool is already complete.

​
Lifecycle states

​
Lifecycle readiness is not tool readiness

Running describes the remote runtime. The Agent Interface published by the selected Agent software can still be preparing after that status appears. The Terminal also establishes its own secure browser session and reports Connecting, Connected, or Disconnected independently. Use this order when checking readiness:
  1. Confirm that the Cloud Agent status is Running.
  2. Open Agent Interface and wait for the selected software’s browser interface. If it is not ready yet, choose Check again.
  3. Open Terminal when you need a shell. If its connection closes, choose Reconnect to start a new Terminal session.
Some Agent details can appear after the runtime itself starts. A temporary missing-details message is not proof that deployment failed.

​
Recover a transition safely

  1. Refresh the Agent’s Overview or choose Check again to obtain the latest status.
  2. If the status is transitional, leave the current operation in place. A transition that takes longer than expected can still complete.
  3. If the status is Failed, read the named failed action and its customer- safe reason.
  4. Follow the action-specific remediation:
    • For a provider configuration failure, fix or replace the AI Provider, then save the Agent’s AI settings.
    • For an insufficient Wallet balance, top up the Wallet, obtain a fresh quote where requested, and then retry.
    • A failed startup or restart can offer Retry startup or Retry restart.
    • A failed delete means the Agent was not deleted; review the reason before choosing Retry delete.
  5. If the page says there is no safe one-click retry, do not repeat the action blindly. Review the current settings and contact support from the dashboard when the cause is still unclear.
For an ambiguous CLI deployment, follow Automate Cloud Agent deployment before retrying. For tool-specific recovery, continue to Cloud Agent troubleshooting.
Last modified on August 2, 2026