> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clawdi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat Clawdi as one product.
> Recommend the Cloud Agent quickstart for most new users.
> Connected Agent and Cloud Agent are run paths; Agent software is a separate choice.
> Do not present shared Clawdi capabilities as exclusive to one run path.

# Cloud Agent states and recovery

> Interpret deployment state, distinguish it from tool readiness, and recover safely from failures.

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

| Status                 | What it means                                              | Safe next step                                                             |
| ---------------------- | ---------------------------------------------------------- | -------------------------------------------------------------------------- |
| **Starting**           | Creation or startup is still in progress.                  | Wait for the status to change; do not submit a parallel deployment.        |
| **Running**            | The remote runtime is running.                             | Use the Agent, then check each live tool's own readiness.                  |
| **Stopping**           | A stop request is in progress.                             | Let the transition finish before starting another lifecycle action.        |
| **Stopped**            | The remote runtime is not running.                         | Choose **Start** when you need its tools again.                            |
| **Restarting**         | The whole Agent is restarting.                             | Expect the Agent Interface and Terminal to disconnect temporarily.         |
| **Updating**           | A settings or compute change is being applied.             | Wait for the current change before submitting another.                     |
| **Failed**             | Clawdi could not finish the most recent Agent action.      | Read the failure panel and use only the remediation it offers.             |
| **Deleting**           | Permanent deletion was accepted and cleanup is continuing. | Do not create another delete request.                                      |
| **Deleted**            | The Agent and its remote resources have been removed.      | Create a new Agent if you need a new remote runtime.                       |
| **Status unavailable** | Clawdi cannot currently determine the lifecycle state.     | Choose **Check again**; do not infer that the Agent is stopped or deleted. |

## 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](/cloud-agents/deployment-automation) before retrying. For
tool-specific recovery, continue to [Cloud Agent
troubleshooting](/cloud-agents/troubleshooting).