Deployment

Deploy NemoClaw to a Remote GPU Instance

View as Markdown

Run NemoClaw on a remote GPU instance through Brev. The preferred path is to provision the VM, run the standard NemoClaw installer on that host, and then run nemoclaw onboard.

Prerequisites

  • The Brev CLI installed and authenticated.
  • A provider credential for the inference backend you want to use during onboarding.
  • HF_TOKEN or HUGGING_FACE_HUB_TOKEN exported when your remote vLLM or Hugging Face workflow needs access to gated models.
  • NemoClaw installed locally if you plan to use the deprecated nemoclaw deploy wrapper. Otherwise, install NemoClaw directly on the remote host after provisioning it.

Deploy the Instance

The nemoclaw deploy command is deprecated. Prefer provisioning the remote host separately, then running the standard NemoClaw installer and nemoclaw onboard on that host.

Create a Brev instance and run the legacy compatibility flow:

$nemoclaw deploy <instance-name>

Replace <instance-name> with a name for your remote instance, for example my-gpu-box. The sandbox created on the remote VM uses NEMOCLAW_SANDBOX_NAME, or my-assistant when the variable is unset. Sandbox names must be lowercase, start with a letter, contain only letters, numbers, and internal hyphens, and end with a letter or number. The deploy wrapper validates the sandbox name before it provisions the Brev instance, opens SSH, or starts the remote installer.

The legacy compatibility flow performs the following steps on the VM:

  1. Installs Docker and the NVIDIA Container Toolkit if a GPU is present.
  2. Installs the OpenShell CLI.
  3. Runs nemoclaw onboard (the setup wizard) to create the gateway, register providers, and launch the sandbox.
  4. Starts optional host auxiliary services, such as the cloudflared tunnel, when cloudflared is available. Onboarding configures channel messaging, and the channels run through OpenShell-managed processes, not through nemoclaw tunnel start.

By default, the compatibility wrapper asks Brev to provision on gcp. Override this with NEMOCLAW_BREV_PROVIDER if you need a different Brev cloud provider. If you export HF_TOKEN or HUGGING_FACE_HUB_TOKEN, the wrapper forwards those values to the VM so remote setup can pull gated Hugging Face model repositories.

Connect to the Remote Sandbox

After deployment finishes, the deploy command opens an interactive shell inside the remote sandbox. To reconnect after closing the session, run the command again:

$nemoclaw deploy <instance-name>

Monitor the Remote Sandbox

SSH to the instance and run the OpenShell TUI to monitor activity and approve network requests:

$ssh <instance-name> 'cd ~/nemoclaw && set -a && . .env && set +a && openshell term'

Verify Inference

Run a test agent prompt inside the remote sandbox:

$openclaw agent --agent main -m "Hello from the remote sandbox" --session-id test

Remote Dashboard Access

The NemoClaw dashboard validates the browser origin against an allowlist baked into the sandbox image at build time. By default, the allowlist only contains http://127.0.0.1:18789. When you access the dashboard from a remote browser, for example through a Brev public URL or an SSH port-forward, set CHAT_UI_URL to the origin the browser uses before running setup:

$export CHAT_UI_URL="https://openclaw0-<id>.brevlab.com"
$nemoclaw deploy <instance-name>

For SSH port-forwarding, the origin is typically the default http://127.0.0.1:18789, so you do not need extra configuration.

On Brev, set CHAT_UI_URL in the launchable environment configuration so the installer can read it when it builds the sandbox image. If you do not set CHAT_UI_URL on a headless host, the compatibility wrapper prints a warning.

NEMOCLAW_DISABLE_DEVICE_AUTH is also evaluated at image build time. When CHAT_UI_URL points at a non-loopback origin, NemoClaw disables OpenClaw device pairing in the generated sandbox configuration because browser-only remote users cannot complete terminal-based pairing. Any device that can reach the configured dashboard origin can connect without pairing, so avoid exposing that origin on internet-reachable or shared-network deployments.

First-Run Readiness Budget

On a remote GPU host, the first nemoclaw onboard typically does the slowest work of the lifecycle: the host builds the sandbox image locally and uploads it into the OpenShell gateway, which can stream hundreds of MiB over the VM’s link before the readiness wait even starts. The post-create readiness wait defaults to 180 seconds (NEMOCLAW_SANDBOX_READY_TIMEOUT), which fits warm-cache, workstation-class onboarding but can be too short for:

  • DGX Station first runs with large quantized models (70B+ parameter footprints, NVFP4 weights).
  • Cloud VMs where the local image-build cache is cold and the upload runs over the public network.
  • Hosts onboarding the Brave Web Search preset on the first run (the egress policy stack adds boot work).

Raise the budget before re-running onboard:

$export NEMOCLAW_SANDBOX_READY_TIMEOUT=600
$nemoclaw onboard

If onboard ends with Sandbox '<name>' was created but did not become ready within 180s, onboard first deletes the partially created sandbox, so the next attempt with the raised budget starts from a clean state. For the inference-probe budget that runs earlier in onboarding, refer to NEMOCLAW_LOCAL_INFERENCE_TIMEOUT.

Proxy Configuration

NemoClaw routes sandbox traffic through a gateway proxy that defaults to 10.200.0.1:3128. If your network requires a different proxy, set NEMOCLAW_PROXY_HOST and NEMOCLAW_PROXY_PORT before onboarding:

$export NEMOCLAW_PROXY_HOST=proxy.example.com
$export NEMOCLAW_PROXY_PORT=8080
$nemoclaw onboard

NemoClaw bakes these values into the sandbox image at build time. NemoClaw also forwards them into the runtime container during sandbox creation, so /tmp/nemoclaw-proxy-env.sh uses the same host and port that the image build used. NemoClaw accepts only alphanumeric characters, dots, hyphens, and colons for the host. The port must be numeric (0-65535). Changing the proxy after onboarding requires re-running nemoclaw onboard.

GPU Configuration

The deploy script uses the NEMOCLAW_GPU environment variable to select the GPU type. The default value is a2-highgpu-1g:nvidia-tesla-a100:1. Set this variable before running nemoclaw deploy to use a different GPU configuration:

$export NEMOCLAW_GPU="a2-highgpu-1g:nvidia-tesla-a100:2"
$nemoclaw deploy <instance-name>