> ## 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, Files, and Terminal
> Use a Cloud Agent's browser interface, Workspace files, and Terminal with clear readiness and persistence boundaries.
Open **Agents** in the [Clawdi dashboard](https://cloud.clawdi.ai), select the
Cloud Agent, then open its **Hermes Dashboard** or **OpenClaw Control UI**,
**Files**, or **Terminal**. These tools belong to the remote runtime and are
available only for Cloud Agents. **Files** appears when file access is available for that Agent.
## Agent Interface
The Agent interface embeds **Hermes Dashboard** or **OpenClaw Control UI**.
Its layout, capabilities, and authentication can differ by software. The
Agent overview also links to its messaging Channels and AI Provider settings.
1. Confirm the Cloud Agent is **Running** and open **Hermes Dashboard** or **OpenClaw Control UI**.
2. Wait for the embedded interface to load; open **Access** only when sign-in material is needed.
3. Start a new conversation and send a small, non-secret task.
4. Review the response before trusting a larger workflow.
The embedded interface accepts your task and shows a response from the
intended Cloud Agent.
*The Chat workspace shows rendered terminal startup content and available tools. Account identity, private runtime session metadata, and terminal input are masked for privacy. The loaded-model label remains visible. Use New chat for your own task.*
### Hermes models
In **Chat**, open the current model selector to review the loaded model catalog
and the model choices available to this runtime. Model availability can change
with the Agent's AI access configuration.
*The native model picker shows the loaded Clawdi catalog in the running Hermes interface.* [Light full-size image](/assets/clawdi-demo-screenshots/light/hermes-models.webp) · [Dark full-size image](/assets/clawdi-demo-screenshots/dark/hermes-models.webp)
### OpenClaw Control UI
An OpenClaw Cloud Agent opens its own **OpenClaw Control UI**. Wait for the
runtime connection and model catalog to load before beginning a conversation.
*The OpenClaw screenshot shows a connected runtime at `/new` with the model catalog loaded. This ready-to-start view illustrates interface readiness; task verification follows after you send your own request.* [Light full-size image](/assets/clawdi-demo-screenshots/light/openclaw-dashboard.webp) · [Dark full-size image](/assets/clawdi-demo-screenshots/dark/openclaw-dashboard.webp)
* 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.
## Files
**Files** opens the Cloud Agent's private Workspace in an embedded browser. The
Agent must be **Running**, and Clawdi authenticates the Files session before
the Workspace loads. Choose **Open in new window** when you need the same Files
view outside the Agent page.
*Workspace files can hold recurring reviews, decision logs, calendars, and research history.*
If **Files** is not shown, file access is not available for that Agent. Use
Terminal or the Agent Interface for the runtime workflow available to it.
## Terminal
**Terminal** opens a secure shell session for the Cloud Agent. It is available
only while the Agent is **Running**. Choose **Open in new window** for a
standalone Terminal. Supported reconnects preserve scrollback, but do not
assume a disconnected foreground command is still 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.
## What persists
The durable boundary is narrower than an entire operating system image.
| Designed to persist | Not 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.
Deleting the Cloud Agent permanently removes its remote resources. Do not
keep the only copy of important work in the remote runtime.
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-files-and-terminal).
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.