Skip to navigation

Start with the OpenClaw overview for installation and shared configuration.

Additional Setup

Install the pinned npm package with its packaged Control UI assets before runtime startup. Startup does not build browser assets or install dependencies. No second backend is needed when terminal or SDK access is also enabled.

Serve the Control UI

OpenClaw’s Control UI is its browser dashboard and chat. A managed runtime serves it when harness.settings.interfaces.dashboard is present:

from nemo_fabric import HarnessConfig
harness = HarnessConfig(
adapter_id="nvidia.fabric.openclaw",
settings={"interfaces": {"dashboard": {"port": 18789}}},
)
  • The Gateway listens on 127.0.0.1 at the dashboard port, which serves the Control UI. start fails with openclaw_interface_port_unavailable if port or port + 2 is in use. OpenClaw also uses port + 10 for its browser relay and allocates browser CDP ports from port + 11 through port + 110, so reserve the whole range from port through port + 110. port can’t be combined with port_range; set enabled to false to keep a configured dashboard off.
  • After the Gateway starts, the adapter writes the sign-in token, generated at each start, to <artifact root>/.fabric/openclaw/runtimes/<runtime-id>/interfaces/dashboard.token. With runtime.keep_state=true, the path is <state_dir>/interfaces/dashboard.token inside the retained home. The file uses mode 0600 on POSIX hosts. On Windows, the file inherits the artifact root’s permissions. stop removes it; if the adapter host is killed, the file can remain.
  • Open http://127.0.0.1:<port>/#token=<token> through a forward to that port to sign in. The Control UI removes the token from the address bar. OpenClaw 2026.9.34 accepts any loopback origin, such as a forward to a different local port; the token is still required.
  • Processes that run as the runtime’s user, including the agent’s own tools, can read the token and reach the port.
  • The adapter regenerates OpenClaw’s configuration at each start and marks it read-only, so changes made through the Control UI don’t survive a restart.
  • Prepared and attached services reject interfaces with openclaw_interfaces_require_managed_runtime.

Origins and Conversations

interfaces.dashboard.public_origins adds explicit HTTP(S) origins to the native allowlist. Supply origins without paths, credentials, queries, or fragments. OpenClaw’s loopback-origin exception still applies; the list does not restrict loopback access to only the configured ports. Authentication remains required. This setting does not change the loopback bind; remote access still needs forwarding or a proxy and native pairing where required.

Select the configured agent and create or select a distinct chat for browser work. Browser tabs can select the same native session; opening another tab does not guarantee a fresh conversation. SDK and HTTP examples use their own stable selectors.

Health and Testing

Native /healthz, /startupz, /v1/models, and /readyz observations feed Fabric’s normalized checks. With browser or terminal access enabled, runtime activity remains unknown because SDK invocation state does not account for native work. Checks do not submit a model turn.

Follow the browser manual test. NeMo Relay export is not supported.