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

# Agent Interface and Terminal

> Use a Cloud Agent's browser interface and shell within their readiness, persistence, and permission boundaries.

Open **Agents** in the [Clawdi dashboard](https://cloud.clawdi.ai), select the
Cloud Agent, then choose **Agent Interface** or **Terminal**. These two tools
belong to the remote runtime and are available only for Cloud Agents.

## Agent Interface

**Agent Interface** embeds the browser interface provided by the selected Agent
software. Its layout, capabilities, and authentication can differ by software.

* The Cloud Agent must be **Running**.
* The interface endpoint can become ready after the runtime starts. If the page
  says it is not ready, choose **Check again** or use Terminal while it starts.
* **Access** shows the current software-specific sign-in material when one is
  required. Treat a displayed password or token as a secret.
* **Open in new window** can require your browser to allow pop-ups for Clawdi.
* **Reset access** rotates the current access material and restarts the whole
  Agent through its normal lifecycle. Existing Agent Interface windows can no
  longer use the old material.

## Terminal

**Terminal** opens a secure shell session for the Cloud Agent. It is available
only while the Agent is **Running**.

The status above the Terminal reports **Connecting**, **Connected**, or
**Disconnected**. If a connection closes, choose **Reconnect** to request a new
session. Starting, stopping, restarting, updating, or deleting the Cloud Agent
can close an active session.

The shell runs as the ordinary runtime user, not with unrestricted system
administrator access. Some protected system paths, operating-system package
operations, and service-level changes can therefore be unavailable. The
Terminal does not bypass Clawdi access controls, an Agent software permission
model, or an external service's authorization.

## Know what persists

The durable boundary is narrower than an entire operating system image.

| Designed to persist                            | Do not treat as durable                                                      |
| ---------------------------------------------- | ---------------------------------------------------------------------------- |
| Supported workspace files                      | The Terminal connection itself                                               |
| Supported Agent plugins and user configuration | A running foreground shell process, temporary files, or runtime scratch data |
| Supported user-level tools                     | Arbitrary changes to protected operating-system files, packages, or services |

Supported workspace files, plugins, user configuration, and user-level tools
are preserved across normal restarts and Clawdi platform updates. This does not
guarantee persistence for every filesystem path or operating-system change,
and it does not provide automatic version control or backup.

<Warning>
  Deleting the Cloud Agent permanently removes its remote resources. Do not
  keep the only copy of important work in the remote runtime.
</Warning>

Use source control or another appropriate external system for important
project files. Use [Vault](/concepts/core-concepts#vault) for supported secret
workflows instead of pasting secrets into shell history, logs, or source files.

If a live tool is unavailable, see [Cloud Agent
troubleshooting](/cloud-agents/troubleshooting#agent-interface-and-terminal).