> This page is for NeMo Fabric, version Latest (v0.7.0) (default).
> For other versions, use one of these documentation indexes:
> - Latest (v0.7.0) (default): https://docs.nvidia.com/nemo/fabric/latest/llms.txt
> - dev: https://docs.nvidia.com/nemo/fabric/dev/llms.txt
> - v0.7.0: https://docs.nvidia.com/nemo/fabric/v0.7.0/llms.txt
> - v0.6.1: https://docs.nvidia.com/nemo/fabric/v0.6.1/llms.txt
> - v0.6.0: https://docs.nvidia.com/nemo/fabric/v0.6.0/llms.txt
> - v0.5.0: https://docs.nvidia.com/nemo/fabric/v0.5.0/llms.txt
> - v0.4.0: https://docs.nvidia.com/nemo/fabric/v0.4.0/llms.txt
> - v0.3.0: https://docs.nvidia.com/nemo/fabric/v0.3.0/llms.txt
> - v0.2.0: https://docs.nvidia.com/nemo/fabric/v0.2.0/llms.txt
> - v0.1.1: https://docs.nvidia.com/nemo/fabric/v0.1.1/llms.txt
> - v0.1.0: https://docs.nvidia.com/nemo/fabric/v0.1.0/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemo/fabric/llms.txt.

# OpenClaw Terminal TUI

> Attach the native terminal renderer to the managed Gateway.

Start with the [OpenClaw overview](/nemo/fabric/integrations/harness-integrations/open-claw) for shared installation, configuration, and ownership.

## Enable Terminal Access

Complete the [shared installation](/nemo/fabric/integrations/harness-integrations/open-claw#install-openclaw-and-the-adapter) first. Terminal access requires a POSIX host, an interactive terminal, and the supported OpenClaw and Node versions. The OpenClaw package includes the terminal UI; no separate frontend build is needed.

Use this harness configuration when starting your managed runtime:

```python
from nemo_fabric import HarnessConfig

harness = HarnessConfig(
    adapter_id="nvidia.fabric.openclaw",
    settings={"interfaces": {"terminal": {}}},
)
```

The adapter starts the Gateway and, once it is ready, creates an executable launcher at `<artifact root>/.fabric/openclaw/runtimes/<runtime-id>/interfaces/terminal`. The terminal connects to that Gateway, so there is no terminal port to configure. Browser assets are unnecessary when dashboard access is disabled.

## Connect From a Terminal

Run the generated `terminal` launcher from an interactive terminal. The [manual example](https://github.com/NVIDIA/NeMo-Fabric/blob/v0.7.0/examples/interfaces/openclaw/README.md#4-terminal-tui) prints its full path as `terminal_launcher`.

The launcher checks that the runtime's private connection files are valid and that the Gateway accepts its credential. It then starts `openclaw tui` with the correct Gateway address and token. Authentication is automatic; you do not need to paste a token. The credential is supplied through the environment and a private client configuration, rather than command-line arguments. Existing OpenClaw connection settings in your shell are cleared for this client so it connects to the selected runtime.

For a runtime inside an OpenShell sandbox, run the launcher through a TTY-enabled sandbox command:

```bash
openshell sandbox exec -n SANDBOX --tty -- /path/to/interfaces/terminal
```

Replace `SANDBOX` and the launcher path with your runtime's values. Local attachment has been tested; the OpenShell terminal transport remains unqualified in this prototype.

## Choose a Conversation

* Run the launcher without `--session` to start a new conversation on the configured agent.
* Add `--session manual-review` to open or continue that named conversation. Reuse the name when reconnecting to the same runtime. Session names cannot contain spaces or colons.
* Browser and terminal clients can join the same conversation when they explicitly select the same native session. Separate clients do not provide user isolation.

Session names apply only to the configured agent and current runtime.

## Disconnect and Check Runtime Health

After a turn completes, enter `/quit` to close the terminal client. The Gateway keeps running, and SDK, HTTP, browser, and other terminal clients can continue using it. The pinned terminal client can return exit code 130 through its native shutdown fallback; that exit code alone does not mean the Gateway stopped.

Stop the owning runtime to shut down the Gateway. The adapter removes `terminal.running` first, then the remaining connection files and credentials.

`Fabric.check()` uses native Gateway endpoints to check health. With browser or terminal access enabled, activity is reported as `unknown` because the adapter cannot observe all interactive work. A passing health check does not establish that the runtime is idle.

## Try It and Review Limitations

Follow the [terminal manual test](https://github.com/NVIDIA/NeMo-Fabric/blob/v0.7.0/examples/interfaces/openclaw/README.md#4-terminal-tui) to send input, continue a conversation, inspect output, and stop the runtime.

Active-turn detach, interactive approvals, remote attachment, and complete native activity discovery still need qualification. NeMo Relay integration is deferred.