Commands#
The nemoclaw CLI is the primary interface for managing NemoClaw sandboxes. It is installed when you run npm install -g nemoclaw.
/nemoclaw Slash Command#
The /nemoclaw slash command is available inside the OpenClaw chat interface for quick actions:
Subcommand |
Description |
|---|---|
|
Show sandbox and inference state |
Standalone Host Commands#
The nemoclaw binary handles host-side operations that run outside the OpenClaw plugin context.
nemoclaw onboard#
Run the interactive setup wizard. The wizard creates an OpenShell gateway, registers inference providers, builds the sandbox image, and creates the sandbox. Use this command for new installs and for recreating a sandbox after changes to policy or configuration.
$ nemoclaw onboard
The first run prompts for your NVIDIA API key and saves it to ~/.nemoclaw/credentials.json.
The wizard prompts for a sandbox name. Names must follow RFC 1123 subdomain rules: lowercase alphanumeric characters and hyphens only, and must start and end with an alphanumeric character. Uppercase letters are automatically lowercased.
Before creating the gateway, the wizard runs preflight checks.
On systems with cgroup v2 (Ubuntu 24.04, DGX Spark, WSL2), it verifies that Docker is configured with "default-cgroupns-mode": "host" and provides fix instructions if the setting is missing.
nemoclaw list#
List all registered sandboxes with their model, provider, and policy presets.
$ nemoclaw list
nemoclaw deploy#
Warning
The nemoclaw deploy command is experimental and may not work as expected.
Deploy NemoClaw to a remote GPU instance through Brev. The deploy script installs Docker, NVIDIA Container Toolkit if a GPU is present, and OpenShell on the VM, then runs the nemoclaw setup and connects to the sandbox.
$ nemoclaw deploy <instance-name>
nemoclaw <name> connect#
Connect to a sandbox by name.
$ nemoclaw my-assistant connect
nemoclaw <name> status#
Show sandbox status, health, and inference configuration.
$ nemoclaw my-assistant status
nemoclaw <name> logs#
View sandbox logs.
Use --follow to stream output in real time.
$ nemoclaw my-assistant logs [--follow]
nemoclaw <name> destroy#
Stop the NIM container and delete the sandbox. This removes the sandbox from the registry.
Warning
Destroying a sandbox permanently deletes all files inside it, including workspace files (SOUL.md, USER.md, IDENTITY.md, AGENTS.md, MEMORY.md, and daily memory notes). Back up your workspace first by following the instructions at Back Up and Restore.
$ nemoclaw my-assistant destroy
nemoclaw <name> policy-add#
Add a policy preset to a sandbox. Presets extend the baseline network policy with additional endpoints.
$ nemoclaw my-assistant policy-add
nemoclaw <name> policy-list#
List available policy presets and show which ones are applied to the sandbox.
$ nemoclaw my-assistant policy-list
openshell term#
Open the OpenShell TUI to monitor sandbox activity and approve network egress requests. Run this on the host where the sandbox is running.
$ openshell term
For a remote Brev instance, SSH to the instance and run openshell term there, or use a port-forward to the gateway.
nemoclaw start#
Start auxiliary services, such as the Telegram bridge and cloudflared tunnel.
$ nemoclaw start
Requires TELEGRAM_BOT_TOKEN for the Telegram bridge.
nemoclaw stop#
Stop all auxiliary services.
$ nemoclaw stop
nemoclaw status#
Show the sandbox list and the status of auxiliary services.
$ nemoclaw status
nemoclaw setup-spark#
Set up NemoClaw on DGX Spark.
This command applies cgroup v2 and Docker fixes required for Ubuntu 24.04.
Run with sudo on the Spark host.
After the fixes complete, the script prompts you to run nemoclaw onboard to continue setup.
$ sudo nemoclaw setup-spark