> ## 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.

# Troubleshoot Cloud Agents

> Resolve Cloud Agent deployment, readiness, live tool, settings, AI access, and billing problems.

Start on the Cloud Agent's **Overview**. Record its current status and the name
of the failed or in-progress action before retrying anything.

## Deployment

### Deploy on Clawdi is not shown

The dashboard shows the Cloud Agent deployment path only when it can verify
that the signed-in account currently has access. Refresh the page and sign in
again. If the availability check still fails, use its retry action; do not use
the Connected Agent flow as a substitute for a remote deployment.

### The CLI asks for authorization

Use the browser authorization and version-specific help in [Automate Cloud
Agent deployment](/cloud-agents/deployment-automation). A legacy manually
entered API key does not authorize deployment.

### A CLI request timed out or lost its connection

The request may already have been accepted. Keep the original request ID and
choices, then follow [Recover an unclear
outcome](/cloud-agents/deployment-automation#recover-an-unclear-outcome).

### Checkout or Agent details did not reopen

Return to **Agents** and look for the accepted Cloud Agent. Use the payment
ambiguity guidance in [Automate Cloud Agent
deployment](/cloud-agents/deployment-automation#make-non-interactive-retries-idempotent).

## States and readiness

### Starting, Restarting, or Updating continues longer than expected

The transition can still finish. Choose **Check again** and keep only the
existing operation in progress. Do not stack lifecycle or settings actions.

### Status unavailable

Clawdi cannot currently determine the state. Choose **Check again**. Do not
infer that the Agent is stopped, safe to delete, or ready for another action.

### The Agent is Running but some details are missing

The remote runtime and its projected Agent details can become available at
different times. Retry the affected section. Available lifecycle actions and
live tools can still work while the remaining details load.

## Agent Interface and Terminal

### Agent Interface is not ready

Confirm the Agent is **Running**, then choose **Check again**. The selected
Agent software can publish its browser interface after runtime readiness. Use
Terminal while the interface starts when Terminal is available.

### A new Agent Interface window does not open

Allow pop-ups for the Clawdi dashboard and try again. If access material cannot
be loaded, open **Access** and retry there. Use **Reset access** only when you
intend to rotate the current credentials or token and restart the Agent.

### Terminal is disconnected

Terminal requires a **Running** Agent. Start a stopped Agent, or wait for the
current transition. Then choose **Reconnect** to request a new secure Terminal
session. A prior browser shell session is not recovered as the same connection.

### A system command reports permission denied

The Terminal uses the ordinary runtime user. Work in supported user and
workspace locations. Do not depend on protected system paths, unrestricted
package or service changes, or administrator privileges.

## Settings and lifecycle

### A lifecycle button is disabled

The action is invalid for the current status or another action is still in
progress. Wait for the transition or choose **Check again**. Use the enabled
control shown for the latest state.

### A settings change failed

Refresh the Agent and compare the current settings with the intended change.
For a network or state conflict, confirm the latest status before retrying. If
the failure panel says there is no safe one-click retry, do not repeat the
mutation blindly.

### Deletion failed

A failed delete means the Agent was not deleted. Review the displayed reason,
then use **Retry delete** if offered. If deletion was accepted and the status is
**Deleting**, wait for cleanup rather than submitting another request.

## AI access and models

### A saved provider is unavailable

Open account-level **AI Providers** and check that the provider is still saved,
ready, and compatible with the Agent software. Fix or replace it, then return
to the Agent's **AI Providers** section and save the intended provider and
primary model.

### The Agent has no configured model access

If **Configure inside agent** is selected, Clawdi intentionally sends no
provider connection. Configure the provider inside the running Agent, or
switch the Agent to Clawdi AI or a usable saved provider.

## Usage, Wallet, and compute

### Wallet balance is insufficient

Open **Settings > Wallet**, review activity, and top up through the dashboard.
Then request a fresh quote and retry the failed action. Do not reuse an expired
quote.

### Stopping did not end a compute subscription

That is expected: lifecycle and compute funding are separate. Open the Cloud
Agent's **Settings > Compute plan** and use the subscription controls available
for its current state.

### A charge is not on the Clawdi Usage page

Clawdi **Usage** reports Clawdi AI spend for its displayed reporting window.
Check **Wallet** for Wallet activity, **Compute** or the billing portal for
remote compute charges, and the external provider for saved or in-Agent model
usage.

If the dashboard provides no safe remediation and the current state remains
unclear, contact [Clawdi support](mailto:support@clawdi.ai) with the Agent name,
current status, failed action, and customer-visible error message. Do not send
provider secrets, access tokens, or Terminal output containing credentials.